BTCDecoded Intelligence
REMOTE · MCP.BTCDECODED.ORG · SCANNED SEP 20
Cited Bitcoin coordination record search (~783k). Lightning. MCP. Not prices/chain analytics.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1542 tokens (~128/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the BTCDecoded Intelligence MCP server?
BTCDecoded Intelligence is a hosted endpoint at https://mcp.btcdecoded.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.btcdecoded.org
claude mcp add --transport http org-btcdecoded-intelligence 'https://mcp.btcdecoded.org/mcp'
{
"mcpServers": {
"org-btcdecoded-intelligence": {
"url": "https://mcp.btcdecoded.org/mcp"
}
}
} {
"servers": {
"org-btcdecoded-intelligence": {
"type": "http",
"url": "https://mcp.btcdecoded.org/mcp"
}
}
} [mcp_servers.org-btcdecoded-intelligence] url = "https://mcp.btcdecoded.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-btcdecoded-intelligence": {
"type": "remote",
"url": "https://mcp.btcdecoded.org/mcp",
"enabled": true
}
}
} openclaw mcp add org-btcdecoded-intelligence --url 'https://mcp.btcdecoded.org/mcp' --transport streamable-http
mcp_servers:
org-btcdecoded-intelligence:
url: "https://mcp.btcdecoded.org/mcp" {
"McpServers": {
"org-btcdecoded-intelligence": {
"Transport": "http",
"Url": "https://mcp.btcdecoded.org/mcp"
}
}
} assistant mcp add org-btcdecoded-intelligence -t streamable-http -u 'https://mcp.btcdecoded.org/mcp'
{
"mcpServers": {
"org-btcdecoded-intelligence": {
"type": "http",
"url": "https://mcp.btcdecoded.org/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 0
- Tool “get_contributor_profile” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “analyze_submission” functional
- “get_contributor_profile” reworded the description of “login” cosmetic
- 19 Sept 26 +39
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 17 Sept 26 31
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.btcdecoded.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=btcdecoded.org | CN=WE1,O=Google Trust Services,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 818563d9d11e235013a4027dc175c595 |
| SANs: btcdecoded.org, mcp.btcdecoded.org, *.mcp.btcdecoded.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.btcdecoded.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| btcdecoded.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp", resource_metadata="https://mcp.btcdecoded.org/.well-known/oauth-protected-resource"
Bearer realm="mcp", resource_metadata="https://mcp.btcdecoded.org/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://mcp.btcdecoded.org/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.btcdecoded.org/mcp |
| Authorisation server | https://mcp.btcdecoded.org |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.btcdecoded.org/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.btcdecoded.org/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_issue ~86
Issue review scaffold for a public GitHub issue. Live-fetches title, body, and a capped comment thread. Private repos fail. Precedent from the index. Does not post comments.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | – | Alternate to url: owner/repo/issues/n. |
| url | string | – | Public GitHub issue URL (https://github.com/owner/repo/issues/n). |
No output schema declared.
No examples provided.
analyze_pr ~93
PR review scaffold for a public GitHub PR. Fetches filenames and a 4000-char patch pack, plus a capped live thread. Private repos fail. Precedent from the index. Does not post comments.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | – | Alternate to url: owner/repo#n. |
| url | string | – | Public GitHub pull request URL (https://github.com/owner/repo/pull/n). |
No output schema declared.
No examples provided.
analyze_submission ~263
Advisory spec-versus-submission check. Retrieves cited index passages, then a closed judge label: met, not_met, or ambiguous. Empty index pack is ambiguous. Optional public GitHub PR (github_pr) is packed; private repos fail. Not a merge, payout, or money check. Does not post comments.
| Name | Type | Req | Description |
|---|---|---|---|
| caller_ref | string | – | Optional opaque correlation id. Echoed, not interpreted. |
| github_pr | string | – | Optional public GitHub PR URL (https://github.com/owner/repo/pull/n) or ref (owner/repo#n). Packed into the submission. Private repos fail. Not an arbitrary URL fetch. |
| requirements | array | – | Optional named criteria strings. When present, the judge may score each 0-1 from the cite pack. |
| source | string | – | Optional pin to one corpus source (e.g. github, irc, mail, spec). Omit to search both layers. |
| spec | string | yes | Natural-language spec or acceptance criteria to check against. |
| submission | string | yes | Natural-language submission text (description and/or public PR pack). |
| when | string | – | Optional date pin YYYY, YYYY-MM, or YYYY-MM-DD. Keeps cites whose passage date starts with that prefix. |
No output schema declared.
No examples provided.
assess_argument ~81
Match the claim to a discourse game, then the documented counter-move, from Bitcoin_Discourse_Games or Bitcoin_Governance_Complete_Argument_Map. Return pattern + cites. No new synthesis. These files are product policy (internal), not contemporaneous evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Claim or thread excerpt to match against the documented discourse games. |
No output schema declared.
No examples provided.
find_discourse ~93
Retrieve GitHub, mail, IRC, and Delving cites for a path or symbol. Mail/IRC rarely include paths.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Source path to search (e.g. src/validation.cpp). |
| query | string | – | Optional extra search text. |
| repo | string | – | Optional owner/repo token to include in the query. |
| symbol | string | – | Optional function or type name. |
No output schema declared.
No examples provided.
find_incident ~59
Retrieve index cites for a named incident or CVE (e.g. CVE-2018-17144). Same search page as search. Empty if the index has no passage.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | CVE id or incident name. |
No output schema declared.
No examples provided.
find_precedent ~64
Retrieve BIP, GitHub, and mail cites for a proposal. Disposition is only what a cite heading or URL already says. Does not invent merged/rejected/stalled labels.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Proposal title, BIP number, or change description. |
No output schema declared.
No examples provided.
find_spec_impl ~57
Retrieve spec, Core source, and GitHub cites for a spec section or behavior. Cites only. Does not emit aligned/gap/divergence verdicts.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Spec section, rule, or implementation question. |
No output schema declared.
No examples provided.
get_contributor_profile ~82
Public-record facts for a GitHub login, or that login's unique public GitHub name, from research findings. Known set is small (canonical maintainers). Most logins return found=false. Do not invent employment or affiliation.
| Name | Type | Req | Description |
|---|---|---|---|
| login | string | yes | GitHub login or unique public GitHub name, case-insensitive. Unknown values return found=false. |
No output schema declared.
No examples provided.
get_passage ~93
Return the stored index passage for a search cite. Pass id from the cite, or source plus doc. Not a live web fetch. If ok is false, the index has no passage.
| Name | Type | Req | Description |
|---|---|---|---|
| doc | string | – | Document id when id is omitted (with source). |
| id | string | – | Vectorize id from a search cite. |
| source | string | – | Corpus source when id is omitted (with doc). |
No output schema declared.
No examples provided.
search ~437
Cited Bitcoin coordination index. Not a live quote, ETF, derivatives, or chain analytics. Pin a layer with source. If ok is false, the index has no passage. Every plan searches both layers. Footnotes label domain (protocol, lightning, mining, tooling, security, nostr, governance). Record: IRC review logs, bitcoin-dev and cryptography mailing lists, GitHub PRs/issues/commits, Delving Bitcoin, Bitcointalk, Satoshi communications, BIP text and BIP PRs/issues, release tags/signers, and Bitcoin Core source (consensus, policy, script, validation, net, mempool, miner). Price: CoinMetrics community PriceUSD (source=price), every daily close from 2010-07-18 through the last dated row, packed by ISO week. Curated: named precursor papers (source=articles); academic protocol/security papers (source=papers); open textbooks (source=textbooks: Learning Bitcoin from the Command Line, Karasavvas, minium, Elementary Bitcoin, Dorier C#, Book of Bitcoin commentary, Mastering Bitcoin 2e, Mastering Bitcoin 3e, Mastering LN, Lightning BOLTs, Mastering Taproot, bitcoin.org developer docs and RPC reference, Optech topics/newsletters); Nostr NIPs (source=nips); Stratum V2 spec (source=sv2); BLIPs, LNURL LUDs, and LSP spec (source=ln-spec); BDK, HWI, LDK, LND/CLN, miniscript, Sparrow Wallet docs (source=tooling); specs, maps, research, and topic syntheses (source=synthesis).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Natural-language question or topic to retrieve cited passages for. |
| source | string | – | Optional pin to one corpus source (e.g. github, irc, mail, price, textbooks). Omit to search both layers. |
| when | string | – | Optional date pin YYYY, YYYY-MM, or YYYY-MM-DD. Keeps cites whose passage date starts with that prefix. Undated cites drop. |
No output schema declared.
No examples provided.
verify_claim ~134
Score whether a stored index passage supports a claim. Pass id from a search cite, or source plus doc. Loads the stored excerpt then returns noul 0-1, skipped if the judge is unavailable, or no_passage if the index has no excerpt. Not a live web fetch. The judge is not a source.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | Claim to score against the stored excerpt. |
| doc | string | – | Document id when id is omitted (with source). |
| id | string | – | Vectorize id from a search cite. |
| source | string | – | Corpus source when id is omitted (with doc). |
No output schema declared.
No examples provided.
What is the BTCDecoded Intelligence MCP server?
BTCDecoded Intelligence is an MCP server listed in the public MCP registry as org.btcdecoded/intelligence. Cited Bitcoin coordination record search (~783k). Lightning. MCP. Not prices/chain analytics. This page covers its hosted endpoint (https://mcp.btcdecoded.org/mcp).
Is the BTCDecoded Intelligence MCP server safe to use?
BTCDecoded Intelligence scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BTCDecoded Intelligence MCP server expose?
BTCDecoded Intelligence exposes 12 tools: search, assess_argument, get_contributor_profile, get_passage, verify_claim, and 7 more. Their descriptions and schemas cost roughly 1,542 tokens of context every time the server is loaded.
Does the BTCDecoded Intelligence MCP server require authentication?
Yes. BTCDecoded Intelligence asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the BTCDecoded Intelligence MCP server still maintained?
BTCDecoded Intelligence is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.