delora-mcp
Registry code: 4c9e9d09b9404cdd
Delora MCP server for cross-chain quotes, supported chains, tokens, and tools.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.delora.build/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is delora-mcp live?
- Partly — its last checks failed now and then (checked 2h ago). It answered 99% of checks over the last 30 days.
- Is delora-mcp free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does delora-mcp have?
- 6 tools: get_quote, get_tokens, get_tools, get_chains, get_instructions, get_token.
- Is delora-mcp safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.7%· all time 99.7%
last good check
of 6 tools
- live → degraded· timeout after 20000ms
- down → live
- unknown → live
- used for
- get a cross-chain swap quote
- list supported chains and tokens
- list bridges and dexes
- takes → gives
- text → data
- tools
- 6 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_tokens reads open 20h ago
List supported tokens. Optionally filter by chains and/or chainTypes.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "chains": { "type": "string", "description": "Comma-separated chain IDs or identifiers" }, "chainTypes": { "type": "string", "description": "Chain types, e.g. EVM,SVM" } } }arguments 14 linesget_tools reads open 28h ago
List available tools (e.g. bridges, DEXes). Optionally filter by chains (comma-separated).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "chains": { "type": "string", "description": "Comma-separated chain IDs or identifiers" } } }arguments 10 linesget_chains reads open 20h ago
List supported chains. Optionally filter by chainTypes (e.g. EVM,SVM).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "chainTypes": { "type": "string", "description": "Comma-separated chain types, e.g. EVM,SVM" } } }arguments 10 linesget_instructions reads open 20h ago
CALL THIS FIRST. Returns the guide for Delora MCP: how to get quotes, chains, tokens, tools…
{ "type": "object", "properties": {} }arguments 4 linesget_token reads auth-required 28h ago
Get a single token by chain and token address/symbol.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "chain", "token" ], "properties": { "chain": { "type": "string", "description": "Chain ID or chain identifier" }, "token": { "type": "string", "description": "Token address or symbol" } } }arguments 18 linesget_quote reads unknown 28h ago
Get a cross-chain quote: best route, output amount, calldata, gas. Use get_chains and get_tokens first to resolve chain IDs and token addresses.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "originChainId", "destinationChainId", "amount", "originCurrency", "destinationCurrency" ], "properties": { "fee": { "type": "number", "maximum": 0.1, "minimum": 0, "description": "Fee 0–0.1 (only with integrator)" }, "amount": { "type": "string", "description": "Amount in smallest units (wei/smallest decimals)" }, "slippage": { "type": "number", "maximum": 1, "minimum": 0, "description": "Slippage tolerance 0–1 (e.g. 0.005 for 0.5%)" }, "integrator": { "type": "string", "description": "Integrator identifier" }, "originChainId": { "type": "number", "description": "Origin chain ID (e.g. 1 for Ethereum, 42161 for Arbitrum)" }, "senderAddress": { "type": "string", "description": "Sender wallet address" }, "originCurrency": { "type": "string", "description": "Token address on origin chain; use 0x0... for native currency" }, "receiverAddress": { "type": "string", "description": "Receiver wallet address" }, "destinationChainId": { "type": "number", "description": "Destination chain ID" }, "destinationCurrency": { "type": "string", "description": "Token address on destination chain; use 0x0... for native" } } }arguments 57 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id4c9e9d09b9404cdd.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/4c9e9d09b9404cdd/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/4c9e9d09b9404cdd?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.