Scienter
Crypto forensics with sources: deployer records, OFAC matches, exchange and bridge attribution.
Connect it
Settings → Connectors → Add custom connector
URL: https://scienter.xyz/mcpSettings → Apps & Connectors → Advanced → Developer mode
Create connector with URL: https://scienter.xyz/mcp{
"mcpServers": {
"scienter": {
"url": "https://scienter.xyz/mcp",
"headers": {
"Authorization": "<YOUR_AUTHORIZATION>"
}
}
}
}claude mcp add --transport http scienter https://scienter.xyz/mcp --header "Authorization: <value>"{
"servers": {
"scienter": {
"type": "http",
"url": "https://scienter.xyz/mcp",
"headers": {
"Authorization": "<YOUR_AUTHORIZATION>"
}
}
}
}8 tools, verified live
solana_tokenread-onlyWho created a Solana token, and what that wallet's OTHER launches did. Takes a mint — the identifier a user actually has — and resolves the wallet that created it, which requires a census that watched Solana launches prospectively since 2026-09-08. EVERY NUMBER IT RETURNS COUNTS LAUNCHES BY THAT WALLET, NOT EVENTS IN THIS TOKEN. Never write that the token had launches or has a death rate; the tru
solana_deployerread-onlyWhat the wallet that deployed a Solana token has done before: how many of its launches settled, how many died, and whether every one of them did. Built from a census that has watched Solana launches prospectively since 2026-09-08, which is why it can answer a question about the deployer rather than about the token. Three outcomes, and they must not be collapsed: - flagged: every settled launch
wallet_scoreread-onlyScienter's forensic read on one blockchain address: public block-explorer facts (age, activity, balance, bounded-window flows), the published exchange-wallet label when the address is one, the clustering engine's entity when it answers, and itemised findings with citations. This does NOT return a risk score. Scienter publishes no calibrated wallet-risk model and this tool will never emit a number
ofac_checkread-onlyScreen one blockchain address against the U.S. Treasury OFAC SDN (Specially Designated Nationals) list: a direct match on the address itself, plus the engine's two-hop proximity walk over the address's real transfer history. Two separate claims, reported separately. Three direct-match outcomes, and they must not be collapsed: - a match: the address is published on the SDN list. The designated e
cex_attributionread-onlyLook up whether an address is a labelled centralised-exchange wallet in Scienter's published exchange-wallet table, whether any address clustered with it is, and what the address's own exchange activity looks like: its deposits to labelled exchange wallets and any per-user deposit addresses inferred from its behaviour, read from real transfer history (activity.checked says whether that read ran).
bridge_traceread-onlyTrace an address's cross-chain bridge transfers: which transfers touched which bridge contracts, toward which chains, for how much, with the transaction hash of each. Scienter matches the address's transfer history (its own warehouse first, a live provider inside a budget after that) against a registry of bridge contracts across seven protocols. The registry is partial by construction, so an empt
leaderboard_queryread-onlyList the addresses Scienter's risk model has flagged most recently, highest score first, with each row's chain, score, model version, top evidence and timestamps. Every row is a model output about a token contract's on-chain behaviour -- not a legal finding, not an audit, and not an allegation against any person. Widely held tokens are excluded by an allowlist and the suppressed count is reported
receipts_lookupread-onlySearch Scienter's published forensic receipts -- written reconstructions of specific on-chain incidents -- by address or free text, and get back titles, dates, subjects and public URLs a human can open. There are only tens of receipts in total, each written for one investigation, so most addresses have none. No match is the normal case and is NOT evidence that nothing happened to or around the ad
Alternatives in Crypto & Web3
Compare →
IBM Granite x402 RemoteB
Pay-per-use IBM Granite AI via x402: chat, code, embeddings, forecasting. USDC on Base or Solana.
GNGate News MCPB
Gate news MCP for crypto news, structured events, announcements, and social sentiment.
APApibaseB
MCP endpoint to APIbase catalog (https://apibase.pro/llms.txt). USDC: x402 Base, MPP Tempo.
AiFinPayB
Pay for any HTTP API in stablecoins on Polygon and Solana with one MCP call.
NWNsgoods Workbench MCPB
Read only x402 catalogue: payability verdicts, prices, drift, host status, signatures. No wallet.
SQSQDB
Query 130+ SQD Portal datasets across blockchains, including native Tron transactions and events.