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

unbundle

https://unbundle.fun

Registry code: c7410b4f4c130205

api record

unbundle checks Solana and Robinhood Chain coins for bundled launches (one party buying the launch through many wallets), creator-held supply and supply hidden in paired pools, and checks wallets for linked side wallets. Answers are saved results with links to the evidence. Present them as a reason to look closer, not as a verdict or financial advice.

endpoint
https://unbundle.fun/api/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 unbundle live?
Yes — it answered the hub's last check (checked 12h ago). It answered 100% of checks over the last 30 days.
Is unbundle free to use?
Yes — the hub reached it with no key and no payment.
What tools does unbundle have?
3 tools: check_coin, check_wallet, list_research.
Is unbundle 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
570ms

last good check

priced tools
0

of 3 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 3 tools
1 open 2 never probed 1 of 3 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.

  • list_research open 12h ago

    Latest on-chain investigations by unbundle (bundling methods, KOL wallet cases), optionally filtered by a keyword. Each has every transaction linked.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Optional keyword, e.g. \"pool\" or \"Cupsey\""
    }
  }
}
    arguments 9 lines
  • check_coin unknown 12h ago

    Was this coin bundled at launch? Returns the saved unbundle launch check for a Solana token address or a Robinhood Chain (0x…) token address: verdict (bundled, likely, creator-held, some signs, clean), the key number, plain-English reasons and a link to the full report. If the coin has not been checked yet, returns a link to run a free check.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Token (mint) address: Solana base58 or Robinhood Chain 0x…"
    }
  }
}
    arguments 12 lines
  • check_wallet unknown 12h ago

    Does this Solana wallet (for example a KOL or trader you copy) have hidden side wallets? Returns the saved unbundle report: likely and strong linked wallets, why they look linked, where the wallet first got its money, and a link to the evidence.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Solana wallet address"
    }
  }
}
    arguments 12 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 c7410b4f4c130205.

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

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.