MCP server: One MCP server.

Entropy0dev MCP

@entropy0devRun by its publisher: served from their own domain, namespace checked by the registry.MCP server · External

Entropy0 MCP server — source trust and URL safety tools for AI agents

Fraud & scam detectionv0.1.3TypeScript
Freeno charge per call

Runs on your machine from its package; the steps are below.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: only reads or looks up information.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npm@entropy0/mcpv0.1.3

Run

npx -y @entropy0/mcp

MCP client config

{
  "mcpServers": {
    "entropy0dev-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@entropy0/mcp"
      ]
    }
  }
}
README3 min read

Entropy0 SDK

AI agents fetch URLs, follow links, and act on domains they've never seen before. Most of the time that's fine. Sometimes it isn't — phishing infrastructure, newly registered lookalike domains, brand impersonation sites, or plain malware hosting.

Entropy0 adds a trust gate between your agent and the external web. One API call returns a machine-readable recommended action your agent can reason about before it fetches, navigates, or transacts.

Try it without signing up →

POST /v1/decide
{ "domain": "secure-login-verify-account.xyz" }

→ recommended_action: "deny"
  confidence: 91%
  signals: [NEWLY_REGISTERED_DOMAIN, BRAND_MISMATCH, CERTIFICATE_ANOMALY]

Packages

PackageRegistryDescription
entropy0-langchainPyPILangChain tool — trust-gate URLs before agents fetch from them
@entropy0/expressnpmExpress middleware — evaluate request targets through /v1/decide
@entropy0/mcpnpmMCP server — source trust and URL safety tools for Claude Desktop, Cursor, Cline

Quick start

LangChain (Python)

bash
pip install entropy0-langchain
python
from entropy0_langchain import Entropy0Tool

tools = [Entropy0Tool(api_key="sk_ent0_xxxx")]
# Agent will call entropy0_trust_check before fetching any external URL

Express (Node.js)

bash
npm install @entropy0/express
typescript
import { entropy0Guard } from "@entropy0/express";

app.use(entropy0Guard({ apiKey: process.env.ENTROPY0_API_KEY! }));
// Requests to flagged domains are blocked before your handlers run

Direct API

bash
curl -X POST https://entropy0.ai/v1/decide \
  -H "X-API-Key: sk_ent0_xxxx" \
  -H "Content-Type: application/json" \
  -d '{"domain": "example.com"}'

How it works

Each decision runs a deterministic pipeline — same inputs always produce the same output:

  1. Classifies the domain (Clear Threat → Safe Known) using WHOIS, DNS, SSL, and threat intel feeds
  2. Maps classification to a base action under your chosen policy
  3. Shifts strictness based on interaction risk (fetch vs transactional vs privileged)
  4. Applies confidence clamps — low-confidence negatives never hard-deny
  5. Returns recommended_action + reason codes + uncertainty + bounded validity window

No probabilistic black boxes. Auditable, explainable, overridable.


Examples

ExampleDescription
examples/rag-agentLangChain agent that trust-gates every URL before fetching content
examples/langgraph-trust-gateLangGraph pipeline with Entropy0 trust gate + evidence usability scoring

LangGraph trust gate demo

This example shows a four-layer retrieval pipeline:

  1. Search returns candidate sources
  2. Entropy0 evaluates whether each source should enter the workflow
  3. The extraction layer retrieves page content
  4. The evidence usability layer determines whether the agent can safely cite the content

Example run:

[entropy0] 5 approved / 1 sandboxed / 0 denied / 0 unverified
  SANDBOX    outpost24.com
             trust signals: ['LONG_OPERATIONAL_HISTORY', 'STRONG_BRAND_ALIGNMENT']
             sandbox reason: ['ELEVATED_DEVIATION']

[evidence layer]
  ! microsoft.com/security/blog/...   boilerplate_dominant — usability=low
  ! genai.owasp.org/llmrisk/...       boilerplate_dominant — usability=low
  ✓ pmc.ncbi.nlm.nih.gov/...          body_text_captured   — usability=high
  ✓ securecodewarrior.com/...         body_text_captured   — usability=high

The agent answered only from high-usability evidence and refused to attribute claims to sources where article body text was not captured.

This prevents a common failure mode in AI search agents:

Treating a reputable URL as equivalent to usable evidence.


Similar modules

Browse Fraud & scam detection