Alimenter votre agent
La commande propre à l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code n'a pas de lien d'installation pour une commande locale. Copiez la commande ci-dessous et exécutez-la dans un terminal.
claude mcp add chain-insights -- npx -y chain-insights@0.80.1À exécuter dans un terminal.
{ "mcpServers": { "chain-insights": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LancerFollow the funds. Find the obvious.
Website | npm | Quickstart
Chain Insights is open-source AML and forensics infrastructure for AI agents and analysts: a hosted Chain Insights Graph you reach over MCP, screened through one CLI. It screens blockchain addresses for risk, explores fund flows through read-only graph queries, and returns structured investigation facts. The hosted graph has a free tier — 5,000 units a day per address, no key and no payment setup — so you can run a first screen in minutes.
All shell snippets in this documentation are for Linux (bash). They work as-is on macOS; on Windows use WSL.
npx chain-insights@latest --help # run without installing
npm install -g chain-insights # or install the cia CLI globally
cia networks # network status + dataset overview
cia network robinhood # how far one network is indexed
cia network robinhood --schema # live graph schema, cached for 24 hours
cia mcp tools # list remote graph tools
Sixty seconds gets you the CLI, a network overview, and the available remote
graph tools for Robinhood.
To call the same tools from an agent, register the MCP proxy:
cia setup claude-code (or claude-desktop / codex / chatgpt / hermes).
The chatgpt target is for Codex chats inside the ChatGPT app: ask there,
not in a plain ChatGPT chat.
CLI results are human-readable by default. Add --json when another tool or
script needs indented JSON:
cia mcp call --json graph_query \
network=robinhood \
"query=USE topology MATCH (a:Address) RETURN a.address AS address LIMIT 10"
The plugin/ folder is the Chain Insights plugin for Claude. It starts the
local Chain Insights MCP proxy on your computer over stdio
(chain-insights-mcp-proxy from the npm package, through npx), and brings the
chain-insights-cypher skill. The proxy serves the views itself (a graph, a
chart or a table, picked from the column names of a graph_query answer, and
the balance), and reaches the Chain Insights Graph for the data.
In Claude Code the plugin also ships a Stop hook that checks every answer against the Chain Insights answer rules (full addresses, tokens are not dollars) and sends the model back once when one is broken.
The plugin needs Node.js 22 or newer. Add this repository as a plugin
marketplace, then install the chain-insights plugin from it. Setup for
Claude Desktop without the plugin, and the plugin's own layout, are in
plugin/README.md.
One public npm package (chain-insights) providing the cia CLI and a
stdio MCP proxy over a Chain Insights Graph endpoint.
Owns:
cia / chain-insights CLI and the chain-insights-mcp-proxy MCP
server (source under src/).graph_* / meta_* /
wallet_* tools.skills/ (chain-insights-*), packaged
into the npm tarball.Never touches:
graph_query; the CLI never writes labels.Upstream:
graphMcpEndpoint; defaults to the public
production endpoint https://mcp.chain-insights.ai/.BASE_RPC_URL override). Not a graph-support claim.Downstream:
Chain Insights is the investigation layer above the Chain Insights Graph. The CLI and MCP proxy call graph tools over one MCP endpoint and never write to the graph.
Agent or CLI user
-> Chain Insights CLI / MCP proxy
-> local config and wallet
-> Chain Insights Graph
-> graph intelligence for AML workflows
Source modules (hand-maintained):
Entry points:
bin/cli.js → src/cli.ts (CLI bins: cia, chain-insights).bin/mcp-proxy.cjs → src/mcp/proxy.ts (bin:
chain-insights-mcp-proxy).src/index.ts — library exports.Full architecture docs: docs/architecture/, the contracts the code keeps in Development, and the repository rules in Contributing.
Graph queries choose the read graph explicitly:
One rule is worth reading before writing a query by hand: the network
argument selects the graph. network is also a property of every node and
relationship on every layer, and its value is the query's network. It is never
stored, except on a :Chain node, so a filter on it narrows nothing: anchor on
an address instead. A thing has one name on every layer: address, tx_id,
block_height and block_hash, with time in epoch milliseconds. See
Graph query compatibility.
Agent installs include chain-insights-cypher for graph-query dialect rules,
one query for each kind of graph search, and how to find the fields of the
EVM / Robinhood graph. Protocol skills sit beside it and load only when a
question names their protocol:
chain-insights-virtuals: Virtuals Protocol agents on robinhood: who
created an agent, who is behind a creator wallet, whether an agent was
dumped, and whether its buyers form a cartel.Chain Insights Graph bills by billable units.
billable_units on every graph response.Check your own count. src/lib/recount-units.ts mirrors the server's
counting logic. Use it client-side to recount units in a response and
confirm the billed amount matches what you received.
Watch for truncated: true. A response can hit the row limit and get
cut off. When you see truncated: true:
LIMIT to ask for fewer rows.SKIP to fetch the next batch.WHERE filter before raising the limit.package.json engines) and npm..env.example documents the two supported overrides:
npm install
npm run build
npm install -g .
cia --version
Or install the released package:
npm install -g chain-insights
cia --version
cia update --check
Run a first query from any directory:
cia mcp call graph_query \
network=robinhood \
"query=USE topology MATCH (a:Address) RETURN a.address AS address LIMIT 10"
Create a local payment wallet when paid access is needed:
cia wallet create
The command shows the private key once in a clearly marked warning panel.
Save it in a secure password manager or offline backup, then type BACKED UP
to finish. The encrypted local copy is stored at
~/.chain-insights/wallet.json. Continue with cia wallet ready when you are
ready to enable paid access.
Example queries. Direct topology:
cia mcp call graph_query \
network=robinhood \
"query=USE topology MATCH (a:Address) RETURN a.address AS address, a.network AS network, a.labels AS labels LIMIT 10"
Batch across graph views:
cia mcp call graph_query_batch \
network=robinhood \
'queries=[{"id":"count","query":"USE topology MATCH (a:Address) RETURN count(a) AS count LIMIT 1"},{"id":"flows","query":"USE topology MATCH (src:Address)-[f:FLOWS_TO]->(dst:Address) RETURN src.address AS source, dst.address AS target, f.amount_usd_sum AS amount_usd_sum, f.tx_count AS tx_count LIMIT 3"},{"id":"linked","query":"USE topology MATCH (a:Address)-[l:LINKED]-(b:Address) RETURN a.address AS address, b.address AS linked_address, l.basis AS basis, l.confidence AS confidence LIMIT 3"},{"id":"node_metrics","query":"USE topology MATCH (a:Address {address:\"FULL_ADDRESS\"}) RETURN a.address AS address, a.tx_out_count AS tx_out_count, a.tx_in_count AS tx_in_count LIMIT 1"}]'
More query examples (manual fund-flow reads, pagination): Graph tools.
cia uses graphMcpEndpoint for all Chain Insights Graph calls. The npm
package uses the public production endpoint by default, so a fresh install can
run cia networks immediately.
For local development, override the default explicitly:
cia config set graphMcpEndpoint http://127.0.0.1:8012/mcp
The public production Graph is already the default. Use the host root. Do not
add /mcp.
cia config set graphMcpEndpoint https://mcp.chain-insights.ai/
To undo every local override at once, after an upgrade or a test setup:
cia config reset # production endpoint, paid mode, no test key; wallet kept; old file in config.json.bak
Optional one-shot override from the environment:
export CHAIN_INSIGHTS_GRAPH_MCP_ENDPOINT=https://mcp.chain-insights.ai/
Configuration precedence:
CHAIN_INSIGHTS_GRAPH_MCP_ENDPOINT env var (GRAPH_MCP_ENDPOINT
legacy alias also supported).cia config set graphMcpEndpoint ... saved value.https://mcp.chain-insights.ai/.Validation rules:
http:// is accepted only for localhost / loopback addresses.https://.Hosted access also needs an access mode, such as an approved access key or
a prepared wallet. For paid access, run cia wallet ready — it checks
funding and finishes one-time payment setup. Setup commands live in
MCP proxy.
The hosted graph includes a free tier for graph_query and
graph_query_batch: 5,000 units a day per address (an IP address block),
no key, 30 requests a minute, reset at midnight UTC. Schema reads
(meta_schema) cost nothing on every door. Use meta_usage_status to see
the current caller allowance. Prepared wallet users receive the free tier
first, then paid access continues automatically.
The local gate, the CI install step and the workflows are in docs/development.md.
~/.chain-insights/runtime/logs/mcp-proxy.jsonl.Health checks (each is runnable):
# Configured endpoint
cia config get graphMcpEndpoint
# User-facing network overview
cia networks
# Detailed Chain Insights capability matrix
cia mcp networks
# Caller allowance / metering status
cia mcp call meta_usage_status
# Fresh remote tool discovery
cia mcp tools --refresh
# Installed CLI sanity
cia --version && cia update --check
# Endpoint, wallet and access mode in one view
cia status
cia network robinhood shows how far that network is indexed:
$ cia network robinhood
Network Robinhood Chain
Identifier robinhood
Status live (default)
Blockchain head 87,642,448 (1 s old)
Indexing height behind head
receipts 87,642,307 141
traces 87,641,751 697
dex 11,959,694 75,682,754
bridge 87,641,751 697
smart accounts 87,641,751 697
Graph height behind head
flows 87,641,751 697
operated_by 87,642,307 141
dex_swaps 87,312,173 330,275
dex_liquidity 87,312,173 330,275
bridged 87,641,751 697
approvals 87,642,307 141
sponsored 87,641,703 745
bundled 87,641,751 697
signers 87,641,703 745
owners 87,641,751 697
contracts 87,641,751 697
Evidence height behind head
evidence not reported
Blockchain head is the newest block the chain node holds, and how old that
reading is. Every other number reads against it.Indexing is the raw chain data: receipts, traces, dex, bridge and smart
accounts. Graph is each link kind of the topology graph. Evidence is the
evidence index.height is the block each one has reached. behind head is the head minus
that height.not started means that data has not begun. not reported means the
network does not report it yet.--json prints the network's reply unchanged.If network or tool discovery fails, check the endpoint and access mode
first. Confirm the endpoint with cia config get graphMcpEndpoint and retry
the command.
Contributor rules, the version bump and the changelog entry every pull request carries: Release Discipline.
Product docs:
Architecture depth:
AML investigation CLI and MCP proxy for blockchain risk screening and Chain Insights Graph access
{ "mcpServers": { "chain-insights": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
Chain Insights s'exécute en local via stdio.
Dernière vérification : 2026-11-14. AML investigation CLI and MCP proxy for blockchain risk screening and Chain Insights Graph access