Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MAD Synapse · Bundle Forensics

REMOTE · AGENT.MADDEGEN.ART

Who is behind a launch: bundles, insiders, airdrops, serial devs. Solana pump.fun + 18 EVM chains.

66 Trust /100

Last scanned (23 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 16 Oct 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability32
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1953 tokens (~390/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 10 Oct 26 63

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 16 Oct 2026 · Probed https://agent.maddegen.art/hub/mcp/forensics

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=maddegen.art CN=YE1,O=Let's Encrypt,C=US 20 Sept 2026 19 Dec 2026 ECDSA 256 ECDSA-SHA384 50f8015ebb899b338e1526cb5bccdb13fc0
SANs: agent.maddegen.art, maddegen.art, www.maddegen.art
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agent.maddegen.art. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
art. present 29485, 32002 8, 8 Verified
maddegen.art. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agent.maddegen.art/hub/mcp/forensics Verified 200
http (plaintext) http://agent.maddegen.art/hub/mcp/forensics HTTPS enforced 301 https://agent.maddegen.art/hub/mcp/forensics
MCP tools · 4 exposed · ~1,452 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
bundle_forensics ~344

Who bundled a Solana pump.fun launch: every block-0 wallet labelled sniper bot / bundle / dev-linked, supply bought and still held, holders who got tokens by transfer, serial-dev check, top-10 concentration, RugCheck — plus a back-tested skip/pass verdict. The rug guard MAD snipers use before every buy. Skip rules were tested on 2,221 real caller calls (held-out: stop-outs 10%→5%, rugs 16%→11%): creator launched another coin in the prior 24 h; top-10 wallets >35%; block-0 wallets that also bundled this creator's earlier launches; block-0 buys >20% of supply. Extra flags: RugCheck danger risks, insider wallets >15%, and >10% held by wallets that never bought on the curve (tokens moved in by transfer, the layered-bundle pattern of launch tools like Proxima). "ok:true" means no red flags were found, not that the coin is safe. When to use: To see WHO bundled a launch and get the skip/pass rug guard MAD snipers use; for a scored launch verdict use launch_scan (on the MAD Synapse · Wallets & Risk server, https://agent.maddegen.art/hub/mcp/risk). Price: $0.003 per call (10 free/day; after that a payment-required result lists x402 options). Errors: returns isError with a message for invalid input or an upstream failure (not charged).

NameTypeReqDescription
mintstringyesSolana token mint (pump.fun launches get the full bundle view) Base58 Solana address, 32-44 chars.
NameTypeReqDescription
bundleobject|null––
devobject|null––
holdersobject|null––
mintstring|null––
msnumber|null––
okboolean|null––
reasonsarray––
rugcheckobject|null––
swap_url–––
verdictstring|null––
warnarray––

No examples provided.

bundler_profile ~296

Is this Solana wallet a bundler? Every pump.fun launch it bought in the first 2 slots over the last 10 days, which creators it keeps bundling for, and whether it is a mass sniper bot or a dev's private bundle wallet. From our block-0 registry of every pump.fun launch (non-creator buys in slots 0–1 after creation). kind: "sniper bot" (≥50 launches in 7 days, buys everything), "dev wallet" (most of its block-0 buys are on one or two creators' coins — a private bundle wallet), "bundler", or "not seen". Use it on wallets bundle_forensics lists, or on any wallet you are about to copy. When to use: To check one wallet from bundle_forensics (sniper bot vs a dev's private bundle wallet); for trading performance use pump_wallet (on the MAD Synapse · Pump & LP server, https://agent.maddegen.art/hub/mcp/pump). 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 input or an upstream failure (not charged).

NameTypeReqDescription
limitinteger–Range 1-100. Default 25.
walletstringyesSolana wallet. Base58 Solana address, 32-44 chars.
NameTypeReqDescription
block0_launches_10dnumber|null––
block0_launches_7dnumber|null––
distinct_creatorsnumber|null––
kindstring|null––
own_launches_10dnumber|null––
recentarray––
sol_spent_10dnumber|null––
top_creatorsarray––
walletstring|null––
windowstring|null––

No examples provided.

creator_launches ~237

Every pump.fun coin a Solana wallet created in the last 10 days, how many graduated, and the wallets that bundle its launches again and again (its private bundle crew). Serial launchers (more than one coin a day) are the strongest rug signal in our tests: calls on coins whose creator launched another coin in the prior 24 h averaged −11% vs −5% after costs. Repeat block-0 wallets across a creator's launches are its own bundle wallets. When to use: For a dev's launch count and its repeat bundle crew; for graduation stats use pump_dev (on the MAD Synapse · Pump & LP server, https://agent.maddegen.art/hub/mcp/pump). 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 input or an upstream failure (not charged).

NameTypeReqDescription
creatorstringyescreator (dev) wallet. Base58 Solana address, 32-44 chars.
limitinteger–Range 1-100. Default 25.
NameTypeReqDescription
bundle_crewarray––
creatorstring|null––
graduatednumber|null––
launchesarray––
launches_10dnumber|null––
launches_24hnumber|null––
serialboolean|null––
verdictstring|null––

No examples provided.

evm_bundle_forensics ~575

Who bundled an EVM token launch (Base, BSC, Ethereum, Arbitrum, Robinhood and 13 more): creation-tx airdrops to fake holders, first-seconds buys, scripted fixed-cadence buying, fresh-wallet and transfer-only holders, dev holdings, exchange-labelled holders, GoPlus contract flags — plus a skip/pass verdict. Replays every ERC-20 Transfer of the token from its first mint on the public RPC, so for young tokens (Base ~4 days, BSC ~6 h of history in budget) holder balances, buys and wallet-to-wallet hand-offs are exact. Launchpads (Four.meme, Uniswap v4 PoolManager, v2/v3 pairs from Dexscreener) are detected; vault/locker contracts that never bought are kept out of the wallet rules, while contracts that DID buy (smart wallets, bundler contracts) count as wallets. Older tokens fall back to GoPlus holders with 527 exchange wallets named. Skip rules: GoPlus honeypot/tax>10%/owner powers; top-10 wallets >35%; first ~2 s of buys >20%; >10% held by wallets that never bought; creation tx airdropping ≥10 wallets or >10%; scripted buying (≥5 buys ≥1% at a regular cadence taking ≥15%); fresh wallets / buyer contracts >15%. Heuristic on EVM (mirrors the back-tested Solana guard); "pass" is not a safety promise. When to use: Bundles and who holds an EVM token launch (Base/BSC first-class); for contract-only flags use evm_token_security (on the MAD Synapse · Wallets & Risk server, https://agent.maddegen.art/hub/mcp/risk). Price: $0.005 per call (10 free/day; after that a payment-required result lists x402 options). Errors: returns isError with a message for invalid input or an upstream failure (not charged).

NameTypeReqDescription
chainstringyesEVM chain: ethereum, base, arbitrum, optimism, polygon, bsc, avalanche, linea, blast, scroll, gnosis, sonic, unichain, mantle, berachain, hyperevm, monad, robinhood. One of "ethereum", "base", "arbit…
tokenstringyesERC-20 token contract address. 0x + 40 hex chars.
NameTypeReqDescription
bundleobject|null––
chainstring|null––
contractobject|null––
holdersobject|null––
launchobject|null––
msnumber|null––
notestring|null––
okboolean|null––
poolsarray––
reasonsarray––
supplyobject|null––
symbolstring|null––
tokenstring|null––
transfers_replayednumber|null––
verdictstring|null––
warnarray––

No examples provided.

Install

How do I install the MAD Synapse · Bundle Forensics MCP server?

MAD Synapse · Bundle Forensics is a hosted endpoint at https://agent.maddegen.art/hub/mcp/forensics, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · agent.maddegen.art

# add to Claude Code
claude mcp add --transport http art-maddegen-agent-synapse-forensics 'https://agent.maddegen.art/hub/mcp/forensics'
Common questions

What is the MAD Synapse · Bundle Forensics MCP server?

MAD Synapse · Bundle Forensics is an MCP server listed in the public MCP registry as art.maddegen.agent/synapse-forensics. Who is behind a launch: bundles, insiders, airdrops, serial devs. Solana pump.fun + 18 EVM chains. This page covers its hosted endpoint (https://agent.maddegen.art/hub/mcp/forensics).

Is the MAD Synapse · Bundle Forensics MCP server safe to use?

MAD Synapse · Bundle Forensics scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the MAD Synapse · Bundle Forensics MCP server expose?

MAD Synapse · Bundle Forensics exposes 4 tools: bundle_forensics, bundler_profile, creator_launches, evm_bundle_forensics. Their descriptions and schemas cost roughly 1,452 tokens of context every time the server is loaded.

Does the MAD Synapse · Bundle Forensics MCP server require authentication?

No. We connected to MAD Synapse · Bundle Forensics without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MAD Synapse · Bundle Forensics MCP server still maintained?

MAD Synapse · Bundle Forensics is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.