satoshidata — Bitcoin entity intelligence
ai.satoshidata/wallet-intelligence · 1.0.6
Bitcoin entity and risk-exposure evidence for AI agents; keyless MCP, no risk_check score/verdict.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://satoshidata.ai/mcp/v1/streamable-httpX-WR-API-Keyoptional, secret: Optional satoshidata.ai API key for premium tools. Free tools work without it.
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 44 tools.
- Protocol
- 2025-06-18
- Calls itself
- satoshidata.ai Agent API MCP 1.26.0
- Handshake time
- 79 ms
- HTTP status
- 200
The tools it lists (44, as of 6 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
wallet_trust_safetyReturn satoshidata.ai's free Bitcoin wallet trust and safety teaser for a single address, including the examined marker when no clear category matched.
address_riskReturn factual address risk signals: entity label/category, source count, bounded behavioral flags, coarse risk_indicator, and an informational-only disclaimer. This is not AML/KYT/compliance advice.
batch_trust_safetyLook up labels and trust-safety signals for multiple Bitcoin addresses in one call. Returns the REST batch trust-safety payload and forwards X-WR-API-Key/Bearer auth when present.
batch_summaryReturn satoshidata.ai wallet/entity summaries for multiple Bitcoin addresses in one call. Forwards X-WR-API-Key/Bearer auth when present.
batch_risk_signalsReturn factual label-derived risk indicators for multiple Bitcoin addresses in one call. Forwards X-WR-API-Key/Bearer auth when present.
risk_checkReturn a free evidence + confidence BTC screening bundle for one address, not a recommendation; you decide whether to transact.
risk_check_batchReturn free evidence + confidence BTC screening bundles for up to 100 addresses, not recommendations; you decide whether to transact.
address_evidence_packReturn a free sectioned evidence report for one Bitcoin address. Packages labels, trust-safety, risk signals, optional risk_check, overview, recent transactions, and optional flow graph with component statuses. Evidence only: no score, verdict, clearance, or compliance recommendation.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
ai.satoshidata/wallet-intelligence, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 102 days ago. The registry entry · satoshidata.ai