Scienter

What the Scienter MCP server does

The Scienter MCP server exposes blockchain investigation tools over MCP. It accepts exact-case Solana mint and wallet addresses, EVM addresses, optional search text, and bounded result limits. The returned data is intended to describe observed evidence and the scope of each check, rather than provide a single verdict about an address or token.

Solana token and deployer tools examine a creator wallet's recorded launches. solana_token resolves the creator from a mint, while solana_deployer starts with a known wallet. Both classify the creator history as flagged, not flagged, or no record. These states refer to settled launches by the wallet and must not be interpreted as a token-level success rate, a clean result, or a buying signal.

How it works

The Scienter MCP server combines published tables, a prospective Solana launch census, transfer-history data, a bridge-contract registry, and an address-clustering engine. Some checks use Scienter's warehouse first and may use a live provider within a stated budget. Tool responses identify whether the relevant read or analysis ran and include limits such as partial registry coverage, hop bounds, node budgets, or row caps.

wallet_score returns public explorer facts such as age, activity, balance, bounded-window flows, exchange labels, clustering results, and itemized findings with citations. It is explicitly not a calibrated wallet-risk score. ofac_check separates a direct address match against the U.S. Treasury OFAC SDN list from a two-hop transfer-history proximity walk. Proximity to a listed address is not itself a designation.

Tools and capabilities

The Scienter MCP server includes these capabilities:

• solana_token: Resolve a Solana mint's creator and inspect that wallet's other recorded launches.
• solana_deployer: Check a known Solana deployer's settled launch history.
• wallet_score: Return cited address facts and forensic findings for EVM or Solana addresses.
• ofac_check: Check direct OFAC SDN matches and bounded transfer-graph proximity.
• cex_attribution: Inspect published exchange-wallet labels, clustering metadata, and observed exchange activity.
• bridge_trace: Find transfers touching tracked bridge contracts across seven protocols for EVM addresses.
• leaderboard_query: List recent token-contract model flags with scores, evidence, versions, and timestamps.
• receipts_lookup: Search published forensic incident reconstructions by address or text.

Limitations and notes

The Scienter MCP server does not establish that an asset is safe, worth buying, or free from risk. Solana addresses and mints are case-sensitive, so changing capitalization can produce no record. A no-record result generally describes coverage, not clean conduct. Likewise, an empty receipt or bridge result does not prove that no incident or bridge transfer occurred.

OFAC screening covers only the published SDN list on the stated date. It does not cover EU, UN, UK/OFSI, or OFAC non-SDN lists. A missed match is not sanctions clearance, and an unperformed check must not be reported as clear.

Exchange attribution is limited by a small published label table. Funding the same exchange wallet only shows that addresses used the same exchange; it does not connect their owners. Each result's clusterable status matters. Bridge tracing covers a partial registry, and truncated results are lower bounds. Leaderboard rows are model outputs about token-contract behavior, not legal findings, audits, or allegations. Its empty results distinguish a quiet day, missing flag-table coverage, an unconfirmed read, and a producer that did not answer.