Agent Margin Router
REMOTE · AGENT-MARGIN-ROUTER-PRODUCTION.UP.RAILWAY.APP
38 x402 pay-per-call tools for AI agents (USDC/USDT on Base): web, crypto, on-chain, geo, packages
Available components
Last scanned (12 hours ago)
Scores higher than 89% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Crypto and Web3
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (3)
- HTTPS
- DNSSEC
- Transport
Checks we could not complete (8)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 12 Oct 26 +1
- Stability: 0.97 → pass security
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 97. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 87. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 18 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 7722 → 9985 ▼ functional
- New tool “feed_discover” functional
- New tool “hash” functional
- New tool “holidays” functional
- New tool “media_convert” functional
- New tool “metadata” functional
- New tool “qr_generate” functional
- New tool “robots_check” functional
- New tool “sitemap_urls” functional
- New tool “text_stats” functional
- New tool “timezone” functional
- New tool “uuid” functional
- New tool “weather” functional
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 5 Nov 2026 · Probed https://agent-margin-router-production.up.railway.app/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agent-margin-router-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| railway.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-margin-router-production.up.railway.app/mcp | Unreachable | ||
| http (plaintext) | http://agent-margin-router-production.up.railway.app/mcp | HTTPS enforced |
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 →
youtube_transcript YouTube Transcript ~192
Fetch the transcript of a YouTube video (manual or auto-generated captions) as timestamped segments plus full text, with language preference and English fallback. Accepts a video id or any YouTube URL. No API key, no download. Pay per call with USDC or USDT on Base via x402. 3 free calls per wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional AMR enterprise API key. |
| include_segments | boolean | – | Return timestamped segments (default true). |
| language | string | – | Preferred caption language (default en). |
| video_id | string | yes | 11-char video id or YouTube URL. |
| wallet | string | – | Your EVM wallet address (0x...). Unlocks the free tier (3 free calls per wallet). |
| x_payment | string | – | Optional signed x402 payment payload (base64 JSON) for USDC/USDT on Base. |
| Name | Type | Req | Description |
|---|---|---|---|
| cost_usdc | number | yes | Price charged in stablecoin units (USDC/USDT 1:1); 0 on the free tier. |
| duration_seconds | integer | yes | – |
| fetched_at | string | – | UTC timestamp when the data was fetched. |
| freshness_seconds | integer | yes | Age of the underlying data in seconds (0 = fetched live). |
| full_text | string | yes | – |
| is_generated | boolean | – | – |
| language | string | yes | – |
| routing | object | yes | How the request was routed (provider, fallback, cache, latency). |
| segment_count | integer | yes | – |
| segments | array | – | – |
| title | – | – | – |
| token | string | – | Token actually used for payment (USDC, USDT or FREE). |
| video_id | string | yes | – |
| word_count | integer | yes | – |
| x_payment_response | string | – | Base64-encoded x402 settlement receipt (mirrors the X-PAYMENT-RESPONSE header). Only present when the call was paid with `x_payment`. |
No examples provided.
How do I install the Agent Margin Router MCP server?
Agent Margin Router is a hosted endpoint at https://agent-margin-router-production.up.railway.app/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 · agent-margin-router-production.up.railway.app
claude mcp add --transport http agentmarginrouter-agent-margin-router 'https://agent-margin-router-production.up.railway.app/mcp'
What is the Agent Margin Router MCP server?
Agent Margin Router is an MCP server listed in the public MCP registry as io.github.AgentMarginRouter/agent-margin-router. 38 x402 pay-per-call tools for AI agents (USDC/USDT on Base): web, crypto, on-chain, geo, packages. This page covers its hosted endpoint (https://agent-margin-router-production.up.railway.app/mcp).
Is the Agent Margin Router MCP server safe to use?
Agent Margin Router scores 84 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 Agent Margin Router MCP server expose?
Agent Margin Router exposes 53 tools: extract_clean, market_spread, gas_fees, best_price, token_price, and 48 more. Their descriptions and schemas cost roughly 9,909 tokens of context every time the server is loaded.
Does the Agent Margin Router MCP server require authentication?
Its publisher declares no required credentials for Agent Margin Router. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Agent Margin Router MCP server still maintained?
Agent Margin Router is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Agent Margin Router MCP server?
VerifyMCP ran 3 checks on Agent Margin Router, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about Agent Margin Router: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.