Agent Exchange router
REMOTE · AGENTEXCHANGE.WORK
Say what your agent needs; get the paid x402 API that works now, with exact request and terms.
Available components
Last scanned (15 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 21 Nov 2026.
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 check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (memory). See how to fix → View diagnostics → Fail
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1314 tokens (~164/item across 8 items; 8 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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 84% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Nov 26 0
- Tool “route” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 19 Nov 26 56
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 21 Nov 2026 · Probed https://agentexchange.work/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentexchange.work | CN=WE1,O=Google Trust Services,C=US | 20 Nov 2026 | 18 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | b0177ec81ef17df50e122cb393490f3b |
| SANs: agentexchange.work, planets.agentexchange.work, *.planets.agentexchange.work | ||||||
| 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 agentexchange.work. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| work. | DS published | 33659 | 13 | Verified |
| agentexchange.work. | No DS | 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 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self' https: data: 'unsafe-inline'; object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentexchange.work/mcp | Verified | 200 | |
| http (plaintext) | http://agentexchange.work/mcp | Served over HTTP | 200 |
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 →
ask The best live paid endpoint for any need ~134
The Agent Exchange router: one question, the best live x402 endpoints for that need, ranked by on-chain payers then price, re-probed hourly. Each answer carries url, method, price_usd, network, payers, settled_usd and the seller page. Free, no signup. To use an answer: GET its url unpaid, read the 402 payment ask, pay the payTo in USDC on Base (x402), retry: delivery at once.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| max_price_usd | number | – | – |
| need | string | yes | what you need done: words |
No output schema declared.
No examples provided.
census_stats What the x402 census holds right now ~52
No arguments. The size and date of the Agent Exchange x402 census (every paid API endpoint in the Coinbase CDP and PayAI catalogs), where to search it, and how a seller gets listed or featured here.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_seller Check an x402 seller (host) ~119
Everything the census knows about one host: resources listed, how many answer a valid 402, dead listings, verdict (live | partial | dead | unverified), price range, catalogs, discovery files present (/.well-known/x402, agent card, llms.txt, openapi.json) and the on-chain settlement facts for its payTo addresses (distinct payers, payments, USDC volume, first/last payment, sampler share) or 'unresolved'.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | host name, e.g. api.example.com |
No output schema declared.
No examples provided.
find_resources Find x402 resources ~203
Search the Agent Exchange x402 census (every resource listed in the CDP Bazaar and PayAI catalogs, probed unpaid). Returns ranked resources with URL, method, price in USD, network, our probe verdict (live = answered a valid 402 today), on-chain payers and settled USD for the seller's payTo, catalogs it appears in, and links to https://bazaar.agentexchange.work/r/<id>. Filter by network (base, solana, base-sepolia, polygon...), max_price_usd, status (live|dead|any).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | default 20 |
| max_price_usd | number | – | only resources priced at or below this many USD |
| network | string | – | base | base-sepolia | solana | polygon | arbitrum | xlayer | other |
| query | string | yes | words, a host name, or a URL fragment |
| status | string | – | default any |
No output schema declared.
No examples provided.
memory Remember and recall (30 days) ~90
Persistent memory for agents: pass value to store (up to 4 KB, kept 30 days), omit value to recall. Keyed by your agent name, so an agent can remember facts, results and state between runs.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | your agent or bot name |
| key | string | yes | what to remember |
| value | string | – | the fact to store; omit to recall |
No output schema declared.
No examples provided.
resource One resource by id ~79
The full census record for one resource id (12 hex chars from find_resources): catalog rows, last unpaid probe with the 402 shape (accepts[0], version, channel, bazaar extension, price match), on-chain facts for its payTo, verdict, and the latest hourly re-probe when one exists.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
route Route me to the right paid API ~201
Say what you need in plain words (e.g. "bitcoin price", "web search", "screenshot a URL"). Returns the one paid API that buyers actually pay for (distinct buyers in 30 days) and that answered a valid x402 402 to our check seconds ago, the exact request to send, and that seller's payment terms so you can pay on your first request; up to four alternatives. Free, no key. Same as GET https://bazaar.agentexchange.work/route.json?need= . Also covers x402scan and AgentCash listings (beyond the CDP and PayAI catalogs), each probed live: https://store.agentexchange.work/find/preview?need=<words>.
| Name | Type | Req | Description |
|---|---|---|---|
| max_price_usd | number | – | optional: only routes at or below this price |
| need | string | yes | what you need, in plain words |
| network | string | – | optional: base | solana | polygon | ... |
No output schema declared.
No examples provided.
search_all_catalogs Search every agent catalog ~222
One search over every open agent catalog indexed at https://bazaar.agentexchange.work/universe: the Official MCP Registry, Smithery, npm packages tagged mcp-server and x402, the Apify Store, ClawHub skills, Agentverse agents, the A2A Registry, Hugging Face Spaces tagged mcp-server, the Docker MCP Catalog and x402-list. Returns name, the link to the entry on its own catalog, description, the catalog popularity number and whether it is paid. Without catalog it searches the top entries of each catalog; with catalog=<key> it searches that catalog in full. For priced x402 routes use find_resources.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | string | – | optional: mcp-registry | smithery | npm-mcp | npm-x402 | apify | docker-mcp | x402-list | clawhub | agentverse | a2a-registry | hf-mcp |
| limit | integer | – | default 30 |
| query | string | yes | what you need: words, a product name, a protocol |
No output schema declared.
No examples provided.
How do I install the Agent Exchange router MCP server?
Agent Exchange router is a hosted endpoint at https://agentexchange.work/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 · agentexchange.work
claude mcp add --transport http work-agentexchange-router 'https://agentexchange.work/mcp'
What is the Agent Exchange router MCP server?
Agent Exchange router is an MCP server listed in the public MCP registry as work.agentexchange/router. Say what your agent needs; get the paid x402 API that works now, with exact request and terms. This page covers its hosted endpoint (https://agentexchange.work/mcp).
Is the Agent Exchange router MCP server safe to use?
Agent Exchange router scores 57 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 Exchange router MCP server expose?
Agent Exchange router exposes 8 tools: route, find_resources, check_seller, resource, census_stats, and 3 more. Their descriptions and schemas cost roughly 1,100 tokens of context every time the server is loaded.
Does the Agent Exchange router MCP server require authentication?
No. We connected to Agent Exchange router without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Exchange router MCP server still maintained?
Agent Exchange router is still listed as active in the MCP registry. We last reached this channel on 21 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 Exchange router MCP server?
VerifyMCP ran 13 checks on Agent Exchange router, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.