Keelage MCP server

• keelage_holdersFree

  Top wallets for one token with pools, contracts and burn addresses labeled, top-10 share excluding pools and contracts, burn share, and the share held by EIP-7702 smart accounts (how the Robinhood app wallet reads).

• keelage_paywrite actionFree

  Prepaid credit for priced calls on the hosted server. With tx: the hash of a USDG transfer on Robinhood Chain (chain 4663) to 0xaE313a57B2CE1cbd31bB82C90ced3CFaC0862bA1; the sending wallet is credited once with the amount. Without tx: the credit of the wallet named by the wallet argument or your X-Wallet header. Free, never counted. The local server has no payments.

• keelage_recordFree

  The track record behind the verdicts, cut every day from Keelage's own ledger: every Robinhood Chain pass with its 24-hour, 7-day and 30-day outcome, and every token-day since each token's first pool, re-cut daily on the hosted server into tables by horizon, band, tier, mcap, pool, age, dayOne, claim, jev, xPosts, xTone, kind, repeat, path, derived, lines, ledger, universe, tokenDays, launcher, projectType, regime, sized, holderGrowth, worst, best, signals, one table at a time (table) or all at once, with the day-by-day series (history). table "signals" is the register of research triggers (conditions that held up in later data, ranked, each with its n, dates and the field it is measured against), with its own history. No dated studies: the rules ship with their origin and are tested on the live tables. Research, not advice.

• keelage_scanFree

  One Robinhood Chain token at the three moments, read from the chain now. The code pass (clean code, not clean, unread): verified source, launcher template, owner privileges, transfer-tax code, honeypot flags. The activity pass (passes, fails, not judged): the code again plus sells clearing, the pool not drained, the deployer share, the holder concentration tier. The size (sized $X, not sized): a share of the pool by tier when the entry test clears, with the one reason when not. verdict.moments carries the three with their reasons; verdict.key keeps the 0.3 word (ELIGIBLE, NOT_ELIGIBLE, FAIL, UNVERIFIED), mapped in verdict.keys. Computed under a named, dated ruleset (the optional ruleset argument) and marked beta; the facts are measured and timestamped. Jev probabilities as context when TYPESAFE_API_KEY is set. signals: the research triggers this scan crosses right now (hosted server; conditions that held up in later data, each with its n and dates), evaluated on the scan's own facts and never written; the verdict and the size do not change for a trigger. Research only, not financial advice.

• keelage_templateFree

  Which launcher template a contract came from (Pons, LaunchToken, Doppler, UERC20, tokenized stock, or unregistered), with the template verdict, the ABI privileges and the transfer-tax identifier count read from verified source.

• keelage_todayFree

  What Keelage read today on Robinhood Chain, as the Today page shows it: this hour's and today's code passes (clean code / not clean / unread, with the reasons), today's activity passes (passes, with the tier and whether each was sized), today's sized passes, and the watch lines that fired on passed tokens (volume, momentum, price, the 10 largest wallets, original holders), plus signals: the research triggers crossed in the last 24 hours, on the rows they belong to. One moment (moment) or all four. Free, never counted. Hosted server only: the local server has no store and says so.

• keelage_tokenFree

  Everything Keelage holds on one Robinhood Chain token, as the token page shows it: the launch (creator, factory, template, block and time), today's price, cap, pool, volume and holders, the structural verdict the scan last recorded, every alert raised on it with its 24-hour, 7-day and 30-day outcome, the hourly price series, what X showed by day, a dated log of what changed, and signals: the research triggers the token crossed, dated. Free, never counted. Hosted server only: the local server has no store and says so.

• keelage_xFree

  What X is saying about one Robinhood Chain token in the last 24 hours: posts and accounts, how much is a repeated template, which large profiles posted and whether they meant this chain's token, views, and a one-line read of the narrative. Context only, never part of the verdict; a scan does not read X. Cached 6 hours per token.

• Code scan20 source files scanned25/25
• Live reliabilityremote reachable in 628ms20/20
• Tool poisoning8 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
• Maintenanceno repository listed3/15
• Maintainer identityno repository or website to verify2/10

Safety score

68/100

higher than 30% of 48,255 servers

Tools

8

the typical server has 7

Tools that change things

13%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

147 ms

faster than 74% of 30,031 servers

Downloads a week

513

more than 88% of 12,191 servers with a package

Keelage: common questions

Is Keelage MCP server safe?

With care: it is graded C, so read the findings first (68/100). Read the Keelage safety report

How do I install Keelage?

It runs remotely at mcp.keelage.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Keelage need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Keelage maintained?

The latest release is v0.4.0.

Is Keelage up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does Keelage compare with other MCP servers?

safety score 68/100 (higher than 30% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.