MAD Synapse · Pump & LP
art.maddegen.agent/synapse-pump · 2.1.0
Every pump.fun curve trade since 09-11: tape, launches, forensics, devs, odds + Meteora DLMM pools.
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/pumpstreamable-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 12 tools.
- Protocol
- 2025-06-18
- Calls itself
- mad-synapse-pump 2.1.0
- Handshake time
- 55 ms
- HTTP status
- 200
The tools it lists (12, 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.
pump_pulseLive pump.fun heartbeat: trades/min, launches, graduations, graduation rate, hottest tokens in the last 15 min. Computed from our own live recording of every pump.fun bonding-curve trade. Use it to decide whether the launch market is hot or dead before scanning individual tokens. When to use: For the market right now; for trends over days use pump_history. Price: free. Errors: returns isError with a message for invalid input or an upstream failure (not charged).
pump_historypump.fun over time: launches, graduations, graduation rate, trades, SOL volume and unique wallets per day or hour since 2026-09-11 — with a compare window. The same tape as pump_pulse, sliced into UTC days or hours so an agent can compare the market over time instead of reading one snapshot. Pass compare_from/compare_to to get a second window and the per-period change (e.g. this week vs last week). Closed periods are precomputed from our own live recording of every bonding-curve trade; the open period is marked partial. Also reports the share of trades made by pump.fun's own mayhem agent, so i
pump_launchesThe newest pump.fun tokens with dev buy, early buyers/volume, curve progress, market cap and creator launch count. Returns up to 50 of the most recent launches (seconds old) with the first-N-seconds flow already aggregated, so an agent can shortlist without replaying the chain. When to use: To discover new mints; then use launch_scan (on the MAD Synapse · Wallets & Risk server, https://agent.maddegen.art/hub/mcp/risk) for a verdict on one of them. Price: $0.002 per call (10 free/day; after that a payment-required result lists x402 options). Errors: returns isError with a message for invalid in
pump_tokenFull bonding-curve forensics for one pump.fun mint: flow, dev buys/sells, launch snipers, top curve holders, peak, graduation, red flags. Aggregates every recorded curve trade of the token: unique wallets, buy/sell SOL, first-60-second flow, whether the dev sold out, non-dev wallets that bought in the launch slots (bundles), top net holders on the curve, peak market cap and post-graduation liquidity. When to use: For raw curve forensics on one mint. For a single scored verdict use launch_scan (on the MAD Synapse · Wallets & Risk server, https://agent.maddegen.art/hub/mcp/risk); for a contract/
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-pump, 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