chain-insights 0.3.6 → 0.3.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +13 -13
- package/docs/graph-tools.md +8 -8
- package/docs/mcp-proxy.md +14 -14
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -19,7 +19,7 @@ MCP endpoint for development; hosted endpoints are set explicitly with
|
|
|
19
19
|
| `trace_victim_funds` | Trace victim/source funds forward to exchange deposit candidates |
|
|
20
20
|
| `trace_deposit_sources` | Trace backward from suspected deposit/cashout addresses to upstream sources and convergence |
|
|
21
21
|
| `trace_suspect_funds` | Trace suspected scammer, mule, operator, or laundering-ring funds forward to cashout topology |
|
|
22
|
-
| `usage_status` | Check the caller's
|
|
22
|
+
| `usage_status` | Check the caller's daily free-tier graph query allowance |
|
|
23
23
|
| `graph_query` | Run one read-only GQL/Cypher query against a GraphRAG MCP graph layer |
|
|
24
24
|
| `graph_query_batch` | Run related read-only graph queries as one MCP call |
|
|
25
25
|
|
|
@@ -117,14 +117,14 @@ If network or tool discovery fails, check the endpoint and access mode first.
|
|
|
117
117
|
The CLI can still initialize workspaces and manage cases without a reachable
|
|
118
118
|
GraphRAG MCP endpoint.
|
|
119
119
|
|
|
120
|
-
Hosted GraphRAG MCP
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
120
|
+
Hosted GraphRAG MCP includes a small public free tier for `graph_query` before
|
|
121
|
+
paid access is required. The default public free tier is 10 execution seconds
|
|
122
|
+
per IP per UTC day. Use `usage_status` to see the current caller allowance.
|
|
123
|
+
Prepared wallet users receive the daily free tier first, then paid access
|
|
124
|
+
continues automatically after the allowance is exhausted.
|
|
125
125
|
If you do not have a prepared wallet yet, use bounded single `graph_query`
|
|
126
|
-
calls
|
|
127
|
-
when the
|
|
126
|
+
calls within the free tier, then prepare a wallet or use an invited tester
|
|
127
|
+
access key when the allowance is exhausted.
|
|
128
128
|
|
|
129
129
|
Open a case and run a small investigation:
|
|
130
130
|
|
|
@@ -162,12 +162,12 @@ The export writes Markdown notes, `manifest.chain-insights.json`,
|
|
|
162
162
|
for Codex, Claude Code, and ChatGPT under `published/<case-slug>/`.
|
|
163
163
|
|
|
164
164
|
Private exports may include full addresses. Use `--mode partner` for controlled
|
|
165
|
-
handoff after review. Use `--mode public` only for shareable
|
|
165
|
+
handoff after review. Use `--mode public` only for shareable examples; public mode
|
|
166
166
|
aliases addresses and removes secrets by default. Vault workflow guidance lives
|
|
167
167
|
in [Obsidian vault workflow](docs/obsidian-vault.md); export bundle details
|
|
168
168
|
live in [Knowledge exports](docs/knowledge-exports.md).
|
|
169
169
|
|
|
170
|
-
##
|
|
170
|
+
## Examples
|
|
171
171
|
|
|
172
172
|
Run a direct live topology query:
|
|
173
173
|
|
|
@@ -185,9 +185,9 @@ cia mcp call graph_query_batch \
|
|
|
185
185
|
'queries=[{"id":"count","query":"USE live_topology MATCH (n) RETURN count(n) AS count LIMIT 1"},{"id":"archive_flows","query":"USE archive_topology MATCH (src:Address)-[f:FLOWS_TO]->(dst:Address) RETURN f.period_granularity AS granularity, src.address AS source, dst.address AS target LIMIT 3"},{"id":"facts_sample","query":"USE facts MATCH (a:Address)-[:HAS_FEATURE]->(f:AddressFeature) RETURN a.address AS address, f.sent_count AS sent_count LIMIT 3"}]'
|
|
186
186
|
```
|
|
187
187
|
|
|
188
|
-
For no-wallet public
|
|
189
|
-
reserve worst-case execution time and can ask for paid access even
|
|
190
|
-
free
|
|
188
|
+
For no-wallet public free-tier usage, prefer the single-query example first.
|
|
189
|
+
Batch calls reserve worst-case execution time and can ask for paid access even
|
|
190
|
+
when a small free allowance remains.
|
|
191
191
|
|
|
192
192
|
Run suspect topology without requiring an incident timestamp:
|
|
193
193
|
|
package/docs/graph-tools.md
CHANGED
|
@@ -14,7 +14,7 @@ The GraphRAG MCP public graph surface is intentionally small:
|
|
|
14
14
|
|
|
15
15
|
| Tool | Purpose |
|
|
16
16
|
| --- | --- |
|
|
17
|
-
| `usage_status` | Return the caller's
|
|
17
|
+
| `usage_status` | Return the caller's daily free-tier graph_query allowance for the current UTC day |
|
|
18
18
|
| `graph_query` | Run one read-only GQL/Cypher query through the universal graph endpoint |
|
|
19
19
|
| `graph_query_batch` | Run related read-only graph-language queries as one MCP call |
|
|
20
20
|
|
|
@@ -31,18 +31,18 @@ GraphRAG MCP endpoint.
|
|
|
31
31
|
- Use `USE archive_topology` for historical topology.
|
|
32
32
|
- Use `USE facts` for labels, features, risk scores, assets, and enrichment.
|
|
33
33
|
- Use `usage_status` before public hosted reads when you need the caller's
|
|
34
|
-
remaining free
|
|
35
|
-
- Hosted endpoints can expose a public free graph_query
|
|
36
|
-
10 execution seconds per IP per UTC day.
|
|
37
|
-
- Prepared wallet users receive the daily
|
|
34
|
+
remaining free-tier allowance.
|
|
35
|
+
- Hosted endpoints can expose a public free tier for graph_query. The default
|
|
36
|
+
is 10 execution seconds per IP per UTC day.
|
|
37
|
+
- Prepared wallet users receive the daily free tier first; after it is used,
|
|
38
38
|
x402 payment continues automatically from the configured wallet.
|
|
39
39
|
- Use explicit LIMIT and pagination in your query when you want bounded result
|
|
40
40
|
sets.
|
|
41
41
|
- The GraphRAG MCP server does not append `LIMIT`; Chain Insights recipes own
|
|
42
42
|
their own limits and pagination.
|
|
43
|
-
- Use single bounded `graph_query` calls for public no-wallet
|
|
43
|
+
- Use single bounded `graph_query` calls for public no-wallet free-tier usage. Use
|
|
44
44
|
`graph_query_batch` for related reads that should share one paid call; public
|
|
45
|
-
free access does not include batches.
|
|
45
|
+
free-tier access does not include batches.
|
|
46
46
|
- `per_query_timeout_seconds` is optional and capped at `10` by default.
|
|
47
47
|
- Returned rows live in `structuredContent.facts`.
|
|
48
48
|
|
|
@@ -80,7 +80,7 @@ chain-insights mcp call graph_query_batch \
|
|
|
80
80
|
|
|
81
81
|
Batch calls reserve worst-case execution time from their timeout settings. On
|
|
82
82
|
public hosted endpoints, they can ask for paid x402 access even when a small
|
|
83
|
-
free
|
|
83
|
+
free-tier allowance remains.
|
|
84
84
|
|
|
85
85
|
Batch result facts include:
|
|
86
86
|
|
package/docs/mcp-proxy.md
CHANGED
|
@@ -140,7 +140,7 @@ chain-insights access-key set ci_test_REDACTED --endpoint https://staging-mcp.ch
|
|
|
140
140
|
chain-insights access-key status
|
|
141
141
|
```
|
|
142
142
|
|
|
143
|
-
|
|
143
|
+
Daily free-tier graph usage:
|
|
144
144
|
|
|
145
145
|
```bash
|
|
146
146
|
chain-insights mcp call usage_status
|
|
@@ -150,23 +150,23 @@ chain-insights mcp call graph_query \
|
|
|
150
150
|
```
|
|
151
151
|
|
|
152
152
|
Hosted GraphRAG MCP can allow anonymous `graph_query` calls before wallet
|
|
153
|
-
setup. The default public free
|
|
154
|
-
|
|
155
|
-
|
|
156
|
-
|
|
157
|
-
|
|
158
|
-
|
|
159
|
-
|
|
160
|
-
`
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
|
|
164
|
-
Staging UAT on 2026-05-31 showed the 10-second
|
|
153
|
+
setup. The default public free tier is 10 execution seconds per IP per UTC day,
|
|
154
|
+
reset on the UTC calendar day. `usage_status` returns only the current caller's
|
|
155
|
+
allowance status. Wallet users receive the same daily free tier first; after it
|
|
156
|
+
is exhausted, x402 payment continues automatically when `wallet ready` reports
|
|
157
|
+
ready.
|
|
158
|
+
|
|
159
|
+
The daily free tier is intended for bounded single `graph_query` calls. It does
|
|
160
|
+
not include `graph_query_batch`; use a tester access key or paid x402 mode for
|
|
161
|
+
regular usage and batches. Use explicit LIMIT and pagination in your query when
|
|
162
|
+
you want bounded result sets.
|
|
163
|
+
|
|
164
|
+
Staging UAT on 2026-05-31 showed the 10-second free tier was enough for exact
|
|
165
165
|
Bittensor address checks, sample address reads, sample flow reads, and the
|
|
166
166
|
free-to-paid handoff. The tested address
|
|
167
167
|
`5EkTMF1noWnWupGxQqtPczW2FFB7ktdVwjaZ22Cam54U93Xx` returned no indexed live or
|
|
168
168
|
archive rows on staging, but bounded sample reads still returned Bittensor
|
|
169
|
-
topology data inside the same daily
|
|
169
|
+
topology data inside the same daily allowance.
|
|
170
170
|
|
|
171
171
|
For custom graph reads, install the shipped `chain-insights-cypher` skill. Its
|
|
172
172
|
Memgraph examples reference distinguishes staging-tested GraphRAG MCP query
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "chain-insights",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.7",
|
|
4
4
|
"description": "AML investigation CLI and MCP proxy for blockchain risk, fund-flow tracing, case reports, and GraphRAG MCP access",
|
|
5
5
|
"homepage": "https://chain-insights.ai",
|
|
6
6
|
"repository": {
|