_ registry / mcp http-sse · checked 49m ago

@flowexecutor/flow-mcp

https://flow-kg4x.vercel.app

Registry code: 221e5aeadda933c3

api record
endpoint
https://flow-kg4x.vercel.app/api/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 it live, free and safe measured by this hub
Is @flowexecutor/flow-mcp live?
Yes — it answered the hub's last check (checked 49m ago). It answered 100% of checks over the last 30 days.
Is @flowexecutor/flow-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does @flowexecutor/flow-mcp have?
2 tools: flow_quote, flow_health.
Is @flowexecutor/flow-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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
648ms

last good check

priced tools
0

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, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
1

distinct

settlements
6

last 2026-10-11

received on chain
0.06 USDC

counted from three payers (thin, concentrated)

_ what it can do 2 tools
1 open 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.

  • flow_health open 49m ago

    Check the Flow quote API health: status, chain, and latest synced block number.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • flow_quote unknown never probed

    Get a best-execution swap quote on Base. Compares Uniswap V3 and Aerodrome, returns the winning venue, expected output, edge in bps vs the baseline, a liquidity flag (deep/watch/thin), the exact block number and timestamp, and build latency. Read-only: no funds move.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "tokenIn",
    "tokenOut",
    "amountIn"
  ],
  "properties": {
    "chainId": {
      "type": "number",
      "description": "Chain id, defaults to 8453 (Base)"
    },
    "tokenIn": {
      "type": "string",
      "description": "Input token contract address on Base (e.g. USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA4E46E)"
    },
    "amountIn": {
      "type": "string",
      "description": "Human-readable input amount, e.g. \"10\" for 10 USDC"
    },
    "tokenOut": {
      "type": "string",
      "description": "Output token contract address on Base (e.g. WETH 0x4200000000000000000000000000000000000006)"
    }
  },
  "additionalProperties": false
}
    arguments 28 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 221e5aeadda933c3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/221e5aeadda933c3/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/221e5aeadda933c3/badge.svg)](https://brick.blue/agent/221e5aeadda933c3?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.