MAD Synapse · Wallets & Risk
art.maddegen.agent/synapse-risk · 2.1.0
Pre-trade safety + wallets: Solana/EVM token risk, honeypots, counterparties, balances, txs, CVEs.
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://agent.maddegen.art/hub/mcp/riskstreamable-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 15 tools.
- Protocol
- 2025-06-18
- Calls itself
- mad-synapse-risk 2.1.0
- Handshake time
- 46 ms
- HTTP status
- 200
The tools it lists (15, 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.
token_risk0-100 rug-risk score for any Solana token: mint/freeze authority, Token-2022 traps, holder concentration, liquidity depth — plus pump.fun curve flags. Contract state is read live from Solana (authorities, Token-2022 extensions such as transfer fees, hooks, permanent delegate, pausable), holders from the largest accounts, market from DexScreener. For pump.fun mints the curve forensics flags are merged in. When to use: For any Solana token, pump.fun or not. For pump.fun curve-stage detail use pump_token (on the MAD Synapse · Pump & LP server, https://agent.maddegen.art/hub/mcp/pump); for EVM tok
launch_scanOne call, one verdict on a pump.fun launch: 0-100 score with positives and risks, graduation odds, dev record, snipers, holders, flow. Runs pump_token + pump_dev + pump_odds together (cheaper than calling them separately) and folds them into a single score and verdict an agent can act on: strong / neutral / weak / avoid. When to use: The one-call verdict on a pump.fun launch; it combines pump_token (on the MAD Synapse · Pump & LP server, https://agent.maddegen.art/hub/mcp/pump), pump_dev (on the MAD Synapse · Pump & LP server, https://agent.maddegen.art/hub/mcp/pump), pump_odds (on the MAD Syn
counterparty_checkOne-call verdict on a Solana wallet before you deal with it: serial token launcher, fast dumper, trading bot, or clean. Combines the wallet's pump.fun launch history (graduation rate, how fast it sells its own launches) with its trading profile into a risk level and reasons. When to use: Before sending to or trading with a Solana wallet; for full trade stats use pump_wallet (on the MAD Synapse · Pump & LP server, https://agent.maddegen.art/hub/mcp/pump). Price: $0.005 per call (10 free/day; after that a payment-required result lists x402 options). Errors: returns isError with a message for inv
priceUSD price, 24h change and liquidity for up to 100 Solana mints; flags illiquid (dead) tokens. Jupiter price data with a liquidity floor: anything under $1,000 of liquidity is flagged dead, because round-trip quotes on dead curves look fine and are not. When to use: For Solana mints by address; for majors or other chains by symbol use crypto_price (on the MAD Synapse · Chain server, https://agent.maddegen.art/hub/mcp/chain). Price: free. Errors: returns isError with a message for invalid input or an upstream failure (not charged).
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,
art.maddegen.agent/synapse-risk, 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 9 days ago. The registry entry · agent.maddegen.art