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

memepump

https://memepump.org

Registry code: d7d8489a03778825

api record

Read-only Solana token safety lookups. Safety data comes from RugCheck analysis of on-chain data and holder data from Solana RPC. Results are automated and informational; they are not financial, investment or legal advice, and a low risk score is not a guarantee that a token is safe.

endpoint
https://memepump.org/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 memepump live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is memepump free to use?
Yes — the hub reached it with no key and no payment.
What tools does memepump have?
3 tools: explain_risk_signals, check_token_safety, get_token_holders.
Is memepump 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
508ms

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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 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.

  • explain_risk_signals unknown never probed

    Returns plain-language definitions of the signals found in a token safety report: risk score bands, honeypot signal, liquidity lock, mint authority, freeze authority, holder concentration and wallet clusters, with what each one can and cannot show. Static reference text; makes no network lookup.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • check_token_safety unknown 1h ago

    Looks up a Solana token by mint address and returns a safety report built from third-party on-chain analysis: a 0 to 100 risk score (0 is lowest risk) with a risk level, whether the token shows honeypot or rug signals, whether liquidity is locked, whether the mint and freeze authorities are still active, top-holder concentration, total liquidity in USD and a list of warnings. Read-only and informational; not financial advice.

    mcp-tool

    {
  "type": "object",
  "required": [
    "mint"
  ],
  "properties": {
    "mint": {
      "type": "string",
      "maxLength": 44,
      "minLength": 32,
      "description": "Solana token mint address in base58, 32 to 44 characters."
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • get_token_holders unknown 1h ago

    Lists the largest holders of a Solana token by mint address with each holder's share of supply, a holder type label and a risk score, and reports whether wallets look linked through a common funder or frequent transfers (cluster flags), plus supply-concentration summary figures. Read-only and informational; not financial advice.

    mcp-tool

    {
  "type": "object",
  "required": [
    "mint"
  ],
  "properties": {
    "mint": {
      "type": "string",
      "maxLength": 44,
      "minLength": 32,
      "description": "Solana token mint address in base58, 32 to 44 characters."
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 25,
      "minimum": 1,
      "description": "How many top holders to return, 1 to 25."
    }
  },
  "additionalProperties": false
}
    arguments 22 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 d7d8489a03778825.

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