btc-intel
Registry code: 4619ff7042d8d3bc
BTC Intel publishes a daily Bitcoin market read and the BTC Intel Score. This server gives what the public site shows: the Score three months late, the market read, the Brief headlines and the Intel DCA plan rules. Research, not investment advice.
- endpoint
- https://btcintel.org/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is btc-intel live?
- Yes — it answered the hub's last check (checked 43m ago). It answered 100% of checks over the last 30 days.
- Is btc-intel free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does btc-intel have?
- 5 tools: get_market_read, get_plan_rules, get_live_score, get_delayed_score, get_brief.
- Is btc-intel safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_delayed_score open 42m ago
The BTC Intel Score (0 to 100) for a day up to the Delayed date, three months behind the live record, as the public site shows it. Without a date: the latest delayed day. A date after the Delayed date is refused.
{ "type": "object", "properties": { "date": { "type": "string", "description": "A day as YYYY-MM-DD. Optional: the latest delayed day when left out." } }, "additionalProperties": false }arguments 10 linesget_brief open 42m ago
The latest public Brief (the daily read) and the latest public Weekly Brief: their headlines, dates and links.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_market_read unknown never probed
The public market read: for the Full Read and each Analysis page (technical, on-chain, market structure, sentiment, macro, cross-market, liquidity, cycle), its state word and its summary line, as printed on the site.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_plan_rules unknown never probed
The public Intel DCA ladder, word for word from btcintel.org/intel-dca/: what each plan (Defensive, Balanced, Growth) does on payday at each Score level, and the notes under the ladder.
{ "type": "object", "properties": { "plan": { "enum": [ "Defensive", "Balanced", "Growth" ], "type": "string", "description": "Optional: one plan. All three when left out." } }, "additionalProperties": false }arguments 15 linesget_live_score unknown 42m ago
The live BTC Intel Score (0 to 100), its level and its date. $0.25 a call in bitcoin over Lightning, one call per payment. Call it without "payment" to get a Lightning invoice and a macaroon; pay the invoice with a Lightning wallet; call it again with payment = "<macaroon>:<preimage>".
{ "type": "object", "properties": { "payment": { "type": "string", "description": "Optional: \"<macaroon>:<preimage>\" after paying the invoice from the first call." } }, "additionalProperties": false }arguments 10 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id4619ff7042d8d3bc.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/4619ff7042d8d3bc/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/4619ff7042d8d3bc?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.