mcp-registry/com.exchangerebel/exchangerebel · v1.1.0
As of 2026-10-21 00:23 UTC, the Exchangerebel MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
76 pay-per-call APIs for AI agents: market, company, weather and dev tools, paid via x402 on Solana.
Claude Code
claude mcp add --transport http exchangerebel-mcp-server https://exchangerebel.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"exchangerebel-mcp-server": {
"type": "http",
"url": "https://exchangerebel.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
173 of 173 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
173 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
115 parameter(s) across 41 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
11 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Loading this server's tool list costs an agent ~30,187 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 41 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.exchangerebel%2Fexchangerebel/fixes
{
"name": "a2a_send",
"description": "Send one 1:1 direct message through the A2A ciphertext relay: {from, to|to_handle, ciphertext (base64, <= 16384 bytes decoded), idempotency_key, client_ts, signature (Ed25519 over the a2a-msg/v1 payload)} -> delivered receipt. Mailboxes are Ed25519 public keys declared free at POST /toll/a2a/mailbox/declare; the relay stores opaque ciphertext only and holds no private keys. The payer of record must equal the sender mailbox. Undeliverable sends are refused FREE before payment. Free pre-check at P",
"inputSchema": {
"type": "object",
"required": [
"from",
"ciphertext",
"idempotency_key",
"client_ts",
"signature"
],
"properties": {
"to": {
"type": "string",
"description": "Recipient mailbox pubkey (exactly one of to / to_handle)."
},
"from": {
"type": "string",
"description": "Sender mailbox: base58 Ed25519 public key (must be a declared mailbox and must equal the payer of record)."
},
"client_ts": {
"type": "string",
"description": "ISO 8601 sender-claimed timestamp."
},
"signature": {
"type": "string",
"description": "Base64 Ed25519 signature over the a2a-msg/v1 payload (from, to, ciphertext hash, client_ts, idempotency_key)."
},
"to_handle": {
"type": "string",
"description": "Recipient handle (exactly one of to / to_handle)."
},
"ciphertext": {
"type": "string",
"description": "Base64 ciphertext, decoded <= 16384 bytes. The relay stores opaque ciphertext only and holds no private keys."
},
"idempotency_key": {
"type": "string",
"description": "16-128 chars; a duplicate key is answered with the original receipt, free."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "address_bundle",
"description": "Address-validation bundle at $0.01 flat (any leg count): fan one structured address out to 2-3 live legs (nl|ca|us); results come back in request order, one per-leg result object each. A 1-leg request refuses free — use the leg tool instead. Canada is available inside this bundle only. Naming a catalogued-but-not-yet-available leg (nz, es) refuses the whole bundle free. Free pre-check: POST /toll/address/bundle/validate/preflight. $0.01 per call — USDC on Solana via x402 (over MCP: call without ",
"inputSchema": {
"type": "object",
"required": [
"address",
"legs"
],
"properties": {
"legs": {
"type": "array",
"items": {
"enum": [
"nl",
"ca",
"us"
],
"type": "string"
},
"maxItems": 3,
"minItems": 2,
"description": "2-3 distinct live leg codes."
},
"address": {
"type": "object",
"required": [
"street_number",
"street_name",
"locality",
"postcode"
],
"properties": {
"unit": {
"type": "string"
},
"state": {
"type": "string"
},
"locality": {
"type": "string"
},
"postcode": {
"type": "string"
},
"street_name": {
"type": "string"
},
"street_type": {
"type": "string"
},
"street_number": {
"type": "string"
}
},
"description": "Structured address components: street_number, street_name, locality, postcode required; state required when the legs list includes us."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "address_leg_nl",
"description": "Netherlands address-validation leg (BAG via PDOK Locatieserver, CC BY 4.0) at $0.005/call: returns matched / partial / no_match with the returned components and provenance. No confidence field. Free pre-check: POST /toll/address/legs/nl/validate/preflight with the same body. $0.005 per call — USDC on Solana via x402 (over MCP: call without payment to get the PaymentRequired challenge, then retry with the payment at _meta[\"x402/payment\"]). HTTP equivalent: POST https://exchangerebel.com/toll/addr",
"inputSchema": {
"type": "object",
"required": [
"address"
],
"properties": {
"address": {
"type": "object",
"required": [
"street_number",
"street_name",
"locality",
"postcode"
],
"properties": {
"unit": {
"type": "string"
},
"state": {
"type": "string"
},
"locality": {
"type": "string"
},
"postcode": {
"type": "string"
},
"street_name": {
"type": "string"
},
"street_type": {
"type": "string"
},
"street_number": {
"type": "string"
}
},
"description": "Structured address components: street_number, street_name, locality, postcode required; unit, street_type, state optional."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.exchangerebel/exchangerebel"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.exchangerebel/exchangerebel"}) over MCP.
render_bundle ~446 tokensa2a_send ~423 tokenssec_alerts_register_watch ~386 tokensscreener_screen ~355 tokensaddress_bundle ~342 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.exchangerebel%2Fexchangerebel?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.exchangerebel%2Fexchangerebel?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.exchangerebel%2Fexchangerebel.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.exchangerebel%2Fexchangerebel.svg :target: https://glimind.com/server/mcp-registry%2Fcom.exchangerebel%2Fexchangerebel?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:4506dc0565219e94…, first seen 2026-10-20, included at leaf 32959 of 36,055. Version history · verify what your client received.
Compare: most reliable other servers · most reliable ml servers · most reliable data servers · most reliable knowledge servers · most reliable finance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 00:23 UTC, the Exchangerebel MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Exchangerebel MCP server advertises 173 tools, including a2a_send, access_crawl, access_crawl_preflight, access_scan, access_scan_preflight.
Point your MCP client at this streamable-http endpoint: https://exchangerebel.com/mcp
Glimind scanned all 173 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.