Entropy0 MCP server — source trust and URL safety tools for AI agents
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.
POST /v1/decide
{ "domain": "secure-login-verify-account.xyz" }
→ recommended_action: "deny"
confidence: 91%
signals: [NEWLY_REGISTERED_DOMAIN, BRAND_MISMATCH, CERTIFICATE_ANOMALY]
| Package | Registry | Description |
|---|---|---|
entropy0-langchain | PyPI | LangChain tool — trust-gate URLs before agents fetch from them |
@entropy0/express | npm | Express middleware — evaluate request targets through /v1/decide |
@entropy0/mcp | npm | MCP server — source trust and URL safety tools for Claude Desktop, Cursor, Cline |
LangChain (Python)
pip install entropy0-langchain
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)
npm install @entropy0/express
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
curl -X POST https://entropy0.ai/v1/decide \
-H "X-API-Key: sk_ent0_xxxx" \
-H "Content-Type: application/json" \
-d '{"domain": "example.com"}'
Each decision runs a deterministic pipeline — same inputs always produce the same output:
recommended_action + reason codes + uncertainty + bounded validity windowNo probabilistic black boxes. Auditable, explainable, overridable.
| Example | Description |
|---|---|
examples/rag-agent | LangChain agent that trust-gates every URL before fetching content |
examples/langgraph-trust-gate | LangGraph pipeline with Entropy0 trust gate + evidence usability scoring |
This example shows a four-layer retrieval pipeline:
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.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @entropy0/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-entropy0dev-mcp": {
"command": "npx",
"args": [
"-y",
"@entropy0/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@entropy0/mcpnpmio.github.entropy0dev/mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.