Home / MCP registry index / io.github.AgentMarginRouter/agent-margin-router

Agent Margin Router

io.github.AgentMarginRouter/agent-margin-router in the official MCP registry. Endpoint https://agent-margin-router-production.up.railway.app/mcp. Source: github.com/AgentMarginRouter/AgentMarginRouter.

The registry describes it as: 38 x402 pay-per-call tools for AI agents (USDC/USDT on Base): web, crypto, on-chain, geo, packages

We read its 53 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http agent-margin-router https://agent-margin-router-production.up.railway.app/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "agent-margin-router": {
      "url": "https://agent-margin-router-production.up.railway.app/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"agent-margin-router","type":"http","url":"https://agent-margin-router-production.up.railway.app/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

extract_clean market_spread gas_fees best_price token_price wallet_balance web_search email_validate dns_whois pdf_text seo_check defi_yields currency_convert geo_ip rss_feed crypto_ohlcv ens_resolve html_to_markdown youtube_transcript github_repo_summary dex_price tx_status erc20_balance news_search hn_search reddit_search defi_tvl fear_greed agent_wallet_snapshot url_status web_crawl metadata sitemap_urls wikipedia_summary arxiv_search npm_package pypi_package geocode domain_rdap dns_lookup contract_info weather holidays robots_check feed_discover text_stats timezone qr_generate uuid hash media_convert health payment_info

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-agentmarginrouter-agent-margin-router/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-agentmarginrouter-agent-margin-router)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers

The Stall
ai.intuitek.the-stall/the-stall
200 tools, nothing matched
2026-10-22
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
200 tools, nothing matched
2026-10-22
Citiview Agent Market
com.citiviewgroup.mcp/agent-market
200 tools, nothing matched
2026-10-26
ScorpTech x402 API
com.it.scorptech/x402
200 tools, nothing matched
2026-10-26
Apex Edge — x402-paid machine services
dev.pages.nonsynthetic/apex-edge
200 tools, nothing matched
2026-10-23
io.github.praneeth12098/x402-factory
io.github.praneeth12098/x402-factory
200 tools, nothing matched
2026-10-26