_ registry / mcp streamable-http · checked 16h ago

swapquote

https://swapquote-al6bxcngia-ue.a.run.app

Registry code: f815ba810fd835c6

api record
endpoint
https://swapquote-al6bxcngia-ue.a.run.app/mcp
protocol
streamable-http ·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 it live, free and safe measured by this hub
Is swapquote live?
Yes — it answered the hub's last check (checked 16h ago). It answered 100% of checks over the last 30 days.
Is swapquote free to use?
No — it charges per call, from 0.005 USDC, quoted in its own 402 answers.
What tools does swapquote have?
2 tools: swap_quote_lite, swap_quote.
Is swapquote 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
187ms

last good check

priced tools
1

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
1 paid 1 never probed 1 of 2 classified

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.

  • swap_quote 0.005 USDC paid 16h ago

    Best-route Solana swap quote: input an input mint, an output mint and an amount in base units, get the quoted output amount in raw and human units, the minimum received after slippage, price impact percent, the full route plan with venue labels and split percents, and USD values and prices for both sides. Quotes come from the Jupiter aggregator public API at request time and are indicative until a transaction is built and signed. Optional slippage_bps (default 50) sets the tolerance the minimum received is computed with. When no route exists for the pair the report says so and states no numbers (fail-closed). Cost: $0.005 USDC per call via x402 (Base settlement; Solana settlement when configured) - no API key needed.

    mcp-tool

    {
      "type": "object",
      "required": [
        "input_mint",
        "output_mint",
        "amount"
      ],
      "properties": {
        "amount": {
          "type": "string",
          "description": "Amount of the input token in base units as an integer string (for example 1000000000 for 1 SOL)."
        },
        "input_mint": {
          "type": "string",
          "description": "Mint address of the token being sold (base58, 32-44 chars)."
        },
        "output_mint": {
          "type": "string",
          "description": "Mint address of the token being bought (base58, 32-44 chars)."
        },
        "slippage_bps": {
          "type": "integer",
          "description": "Optional slippage tolerance in basis points (default 50, max 10000)."
        }
      }
    }
    arguments 26 lines
  • swap_quote_lite unknown 16h ago

    FREE lite Solana swap quote for one input mint, output mint and amount. Output amount, USD values on both sides, the exchange rate and price impact only. Use it to price a swap before committing; the paid swap_quote adds minimum received, the full route plan and per-side price detail.

    mcp-tool

    {
      "type": "object",
      "required": [
        "input_mint",
        "output_mint",
        "amount"
      ],
      "properties": {
        "amount": {
          "type": "string",
          "description": "Amount of the input token in base units as an integer string (for example 1000000000 for 1 SOL)."
        },
        "input_mint": {
          "type": "string",
          "description": "Mint address of the token being sold (base58, 32-44 chars)."
        },
        "output_mint": {
          "type": "string",
          "description": "Mint address of the token being bought (base58, 32-44 chars)."
        },
        "slippage_bps": {
          "type": "integer",
          "description": "Optional slippage tolerance in basis points (default 50, max 10000)."
        }
      }
    }
    arguments 26 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f815ba810fd835c6.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f815ba810fd835c6/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f815ba810fd835c6/badge.svg)](https://brick.blue/agent/f815ba810fd835c6?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.

_ how we know
card completeness
60%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.