EntRoute
REMOTE · MCP.ENTROUTE.COM · SCANNED SEP 28
Discover and call pay-per-request (x402) APIs, ranked by reliability, latency and price.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 860 tokens (~286/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the EntRoute MCP server?
EntRoute is a hosted endpoint at https://mcp.entroute.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.entroute.com
claude mcp add --transport http com-entroute-entroute 'https://mcp.entroute.com/mcp'
{
"mcpServers": {
"com-entroute-entroute": {
"url": "https://mcp.entroute.com/mcp"
}
}
} {
"servers": {
"com-entroute-entroute": {
"type": "http",
"url": "https://mcp.entroute.com/mcp"
}
}
} [mcp_servers.com-entroute-entroute] url = "https://mcp.entroute.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-entroute-entroute": {
"type": "remote",
"url": "https://mcp.entroute.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-entroute-entroute --url 'https://mcp.entroute.com/mcp' --transport streamable-http
mcp_servers:
com-entroute-entroute:
url: "https://mcp.entroute.com/mcp" {
"McpServers": {
"com-entroute-entroute": {
"Transport": "http",
"Url": "https://mcp.entroute.com/mcp"
}
}
} assistant mcp add com-entroute-entroute -t streamable-http -u 'https://mcp.entroute.com/mcp'
{
"mcpServers": {
"com-entroute-entroute": {
"type": "http",
"url": "https://mcp.entroute.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://mcp.entroute.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=entroute.com | CN=WE1,O=Google Trust Services,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | cd842f26e05c241b0eaeb8e80fe35a84 |
| SANs: entroute.com, mcp.entroute.com, *.mcp.entroute.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.entroute.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| entroute.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.entroute.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.entroute.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
call_paid_api ~282
Call a previously discovered API endpoint. Use this after discover_paid_api to execute the request. IMPORTANT: You must first use discover_paid_api to find an endpoint. Then use the endpoint_id from the discovery result. Use the sample_request from the discovery result as your body template — it shows the exact parameter names the endpoint expects. Replace the example values with the actual values you need. Payment: this hosted server holds no wallet, so it cannot settle x402 payments. Free endpoints return their data directly. Paid endpoints return the payment challenge (amount, recipient, network) without charging anything. To pay automatically, run the local server instead: npx @entroute/mcp-server with EVM_PRIVATE_KEY set. Trust & safety: - EntRoute verifies that endpoints return valid 402 responses every 10 minutes, but does not guarantee response quality or accuracy. Treat results like any third-party API. - Prefer endpoints with high success rates (>95%) and recent verification timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | Request body (for POST/PUT/PATCH) |
| endpoint_id | string | yes | The endpoint_id from a previous discover_paid_api result |
| headers | object | – | Additional headers to include in the request |
| method | string | – | HTTP method (defaults to endpoint method) |
| query_params | object | – | Query parameters to append to URL |
No output schema declared.
No examples provided.
discover_paid_api ~353
Discover pay-per-request API endpoints for a given capability. Returns ranked, verified endpoints with pricing and reliability metrics. Use this to find APIs before calling them. The results include: - Endpoint URL and method - Price per call and payment network - Success rate and latency metrics - Provider information - sample_request / sample_response: Example request body and response showing the exact parameter names and format the endpoint expects. ALWAYS use sample_request as your template when calling the endpoint — do not guess parameter names. After discovering, you can use call_paid_api to execute the endpoint. Trust & safety: - "Verified" means the endpoint returns a valid x402 402 response -- it does not guarantee the quality or accuracy of the data returned after payment. - Endpoints are probed every 10 minutes. Check last_verified and success_rate to gauge reliability. - Fallback endpoints (unverified) have failed recent verification checks -- use with caution. - Prefer endpoints with success_rate >95% and verification within the last 24 hours.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | – | Explicit capability ID if known (e.g., "weather.current", "translate.text"). Alternative to intent for precise matching. |
| intent | string | yes | Natural language description of what you want to do (e.g., "get current weather for London", "translate text to Spanish"). Provide this or capability_id. |
| limit | number | – | Maximum number of endpoints to return (default: 5) |
| max_price | number | – | Maximum price per request in USD (e.g., 0.01 for 1 cent) |
| network | string | – | Required blockchain network for payment |
| ranking_preset | string | – | Ranking preference preset |
No output schema declared.
No examples provided.
list_capabilities ~107
List available API capability types. Use this to explore what kinds of APIs are available in the registry. You can filter by tag (e.g., "weather", "translation") or search by keyword. Note: A capability existing does not mean verified endpoints are available for it. Use discover_paid_api to check for live endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Search capabilities by keyword |
| tag | string | – | Filter by tag (e.g., "weather", "translation", "finance") |
No output schema declared.
No examples provided.
What is the EntRoute MCP server?
EntRoute is an MCP server listed in the public MCP registry as com.entroute/entroute. Discover and call pay-per-request (x402) APIs, ranked by reliability, latency and price. This page covers its hosted endpoint (https://mcp.entroute.com/mcp).
Is the EntRoute MCP server safe to use?
EntRoute scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the EntRoute MCP server expose?
EntRoute exposes 3 tools: discover_paid_api, list_capabilities, call_paid_api. Their descriptions and schemas cost roughly 742 tokens of context every time the server is loaded.
Does the EntRoute MCP server require authentication?
No. We connected to EntRoute without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the EntRoute MCP server still maintained?
EntRoute is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.