_ registry / mcp + a2a streamable-http · checked 2h ago

4626.fun

https://4626.fun

Registry code: 7114811fa7d78cbd

api record

Read-only 4626.fun MCP server. Use get_openapi_spec, get_health, get_vault_report, and list_explore_vaults. Creator vaults are pre-launch. Do not treat demo vaults as live deposit destinations.

endpoint
https://4626.fun/api/mcp
door code
80de6c28196eae9a
protocol
streamable-http ·2025-03-26
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 4626.fun live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is 4626.fun free to use?
Yes — the hub reached it with no key and no payment.
What tools does 4626.fun have?
4 tools: get_vault_report, get_openapi_spec, list_explore_vaults, get_health.
Is 4626.fun 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
99.6%

90 days 99.5%· all time 99.6%

latency
2,173ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 842 checks · signed record
  • degraded → live
  • live → degraded· HTTP 500: vercel INTERNAL_FUNCTION_INVOCATION_FAILED
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
topic
crypto & onchain trading & defi
used for
  • get a vault report for an evm address
  • list explore vaults
  • get agent api openapi spec
takes → gives
data → data
tools
4 reads
_ 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 4 tools
3 open 1 never probed 3 of 4 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.

  • get_openapi_spec reads open 16h ago

    Return the 4626.fun Agent API OpenAPI 3.0 document.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_explore_vaults reads open 16h ago

    List 4626.fun explore vaults from the public Agent API.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "q": {
      "type": "string"
    },
    "sort": {
      "enum": [
        "volume",
        "marketCap",
        "fees24h",
        "new"
      ],
      "type": "string"
    },
    "time": {
      "enum": [
        "1d",
        "1w",
        "1y"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • get_health reads open 12h ago

    Read the public 4626.fun liveness payload.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_vault_report reads unknown 16h ago

    Fetch a 4626.fun vault report for an EVM address.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "pattern": "^0x[a-fA-F0-9]{40}$",
      "description": "Vault address"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
_ try it over mcp 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 7114811fa7d78cbd.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7114811fa7d78cbd/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/7114811fa7d78cbd/badge.svg)](https://brick.blue/agent/7114811fa7d78cbd?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 knowoff the mcp door
card completeness
80%

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.