com.cerberusindex/cerberus-index
com.cerberusindex/cerberus-index · 1.0.0
XRPL token rug-checks, issuer reputation & AMM data for AI agents. Pay-per-call USDC via x402.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://cerberusindex.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 20 tools.
- Protocol
- 2025-06-18
- Calls itself
- cerberus-index 1.28.1
- Handshake time
- 234 ms
- HTTP status
- 200
The tools it lists (20, as of 5 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
check_xrpl_tokenLive safety verdict for an XRPL token: clawback & global-freeze hard rejects, issuer blackhole status (can supply ever be re-minted?), NoFreeze, pool depth & trading fee, LP-burn fraction (is liquidity locked?), plus Cerberus's proprietary rug blocklist & detection history. Verdicts: unsafe | caution | likely_safe | unknown, with reasons. Covers BOTH XRPL fungible-token standards. `currency` may be a 3-char or 40-char hex trust-line code, OR a 48-char MPTokenIssuanceID — pass an issuance ID and the token is screened as a Multi-Purpose Token instead (issuance locked, clawback, freeze power, all
check_issuer_reputationReputation for an XRPL issuer: blocklist status + historical detection outcomes. Price: $0.002 USDC. Missing something? Call `submit_feedback` (free) to request it.
check_addressCross-chain address & counterparty risk — one call before you send to, approve, or trust an address. EVM chains (ethereum, base, bsc, polygon, arbitrum, optimism, avalanche, …): sanctions, mixer, phishing, drainer, money-laundering & cybercrime flags aggregated from GoPlus, told whether it's a contract or a wallet. XRP Ledger (r-addresses): Cerberus's own engine — the production rug blocklist, live clawback/global-freeze flags (can this address seize or freeze tokens it issues?), burn-address detection, and prior launch history — coverage no incumbent offers. Chain is auto-detected; pass `chai
check_transactionSimulate an unsigned XRPL transaction and tell you what it will ACTUALLY do — before you sign it. Pass the transaction JSON; get back (1) its intent in plain language, (2) a live-ledger dry-run (`simulate`): would it succeed, and the exact balance changes per account — computed, never submitted, never signed — and (3) drain vectors flagged: handing over your signing key (SetRegularKey / SignerListSet), disabling your master key, enabling clawback, partial-payment tricks, trustlines to blocklisted issuers, sends to flagged addresses. Verdict: danger | caution | safe | unknown. A transaction tha
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.cerberusindex/cerberus-index, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 81 days ago. The registry entry · cerberusindex.com