Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
BTC Intel is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
13
tools declared
remote
at its publisher
—
calls last 7d
What it does
Bitcoin market-state Score (0-100): free delayed reads; live Score $0.25 per call via Lightning
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http btc-intel-mcp https://btcintel.org/mcp
# 2 — ask your agent for something these tools do
# get_delayed_score, get_market_read, get_brief and 10 more
BTC Intel costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BTAll 1 server
btcintel1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http btc-intel-mcp https://btcintel.org/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | A day as YYYY-MM-DD. Optional: the latest delayed day when left out. |
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.
No parameter schema on file.
The latest public Brief (the daily read) and the latest public Weekly Brief: their headlines, dates and links.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan | string | no | Optional: one plan. All three when left out. |
The live BTC Intel Score (0–100), its market classification and historical positioning. Shows where today's Score ranks against the complete historical record (daily since July 2011; live since October 6, 2026, earlier days back-calculated with the current method), including its historical position and the proportion of recorded days above and below today's reading, with the publication date. Cont
| Parameter | Type | Required | Notes |
|---|---|---|---|
| payment | string | no | Optional: "<macaroon>:<preimage>" after paying the invoice from the first call. |
Where Bitcoin stood on a day compared with its own history: the BTC Intel Score (0–100) and its classification, marked live or back-calculated (daily since July 18, 2011; live publication since October 6, 2026; earlier days back-calculated with the current method). Free up to the Delayed date (three months back); live = true or a later day: through the latest published day, $0.25 a call in bitcoin
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | Optional day, YYYY-MM-DD. The Delayed date when left out (the latest published day with live = true). |
| live | boolean | no | Optional: true for data through the latest published day (paid, $0.25 a call). Free answers stop at the Delayed date. |
| payment | string | no | Optional: "<macaroon>:<preimage>" after paying the invoice a paid call returned. Send the same arguments again with it. |
How the Score has moved over 1, 7, 30 and 90 days and how long it has held its classification, counted on its own daily record. Free up to the Delayed date (three months back); live = true or a later day: through the latest published day, $0.25 a call in bitcoin over Lightning, never recurring. Changes describe the past, not what comes next.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| live | boolean | no | Optional: true for data through the latest published day (paid, $0.25 a call). Free answers stop at the Delayed date. |
| payment | string | no | Optional: "<macaroon>:<preimage>" after paying the invoice a paid call returned. Send the same arguments again with it. |
Where the Score sits in its own record: its historical position (the share of recorded days above and below today's reading), mean, median and range, days in each 10-point band, and the stretches and moves between classifications. Free up to the Delayed date (three months back); live = true or a later day: through the latest published day, $0.25 a call in bitcoin over Lightning, never recurring. T
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | no | Optional: the statistics on days from here (YYYY-MM-DD); the historical position and classification are always on the whole record. |
| to | string | no | Optional: the statistics on days up to here (YYYY-MM-DD); after the Delayed date is paid. |
| live | boolean | no | Optional: true for data through the latest published day (paid, $0.25 a call). Free answers stop at the Delayed date. |
| payment | string | no | Optional: "<macaroon>:<preimage>" after paying the invoice a paid call returned. Send the same arguments again with it. |
The daily record (daily since July 18, 2011; live publication since October 6, 2026; earlier days back-calculated with the current method), each row marked live or back-calculated, as JSON or CSV, 100 rows a page. Free up to the Delayed date (three months back); later days $0.25 a query, one payment opening every page for 24 hours, or $1.00 for the full live export (export = true, 1000 rows a page
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | no | Optional first day, YYYY-MM-DD. The start of the record when left out. |
| to | string | no | Optional last day, YYYY-MM-DD. The Delayed date when left out (the latest published day with live = true); a day after the Delayed date is paid. |
| page | integer | no | Optional page, from 1. A page is 100 rows; next_page in the answer gives the next one (null on the last). |
| format | string | no | Optional: json (default) or csv. |
| export | boolean | no | Optional: true for the full live export, $1.00, 1000 rows a page. |
| live | boolean | no | Optional: true for data through the latest published day (paid, $0.25 a call). Free answers stop at the Delayed date. |
| payment | string | no | Optional: "<macaroon>:<preimage>" after paying the invoice a paid call returned. Send the same arguments again with it. |
The stretches the Score spent in each classification (Low, Moderate-low, Neutral, Elevated, High), newest first, 100 a page, each marked live or back-calculated. Free up to the Delayed date (three months back); later days $0.25 a query in bitcoin over Lightning, one payment opening every page for 24 hours, never recurring.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | no | Optional first day, YYYY-MM-DD. The start of the record when left out. |
| to | string | no | Optional last day, YYYY-MM-DD. The Delayed date when left out (the latest published day with live = true); a day after the Delayed date is paid. |
| page | integer | no | Optional page, from 1. A page is 100 rows; next_page in the answer gives the next one (null on the last). |
| live | boolean | no | Optional: true for data through the latest published day (paid, $0.25 a call). Free answers stop at the Delayed date. |
| payment | string | no | Optional: "<macaroon>:<preimage>" after paying the invoice a paid call returned. Send the same arguments again with it. |
The daily intelligence brief. Free: the five market areas' state words on the Delayed date (three months back); live = true, $0.25 a call in bitcoin over Lightning, never recurring: the latest Brief with its headline, the five state words and the top stories.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| live | boolean | no | Optional: true for data through the latest published day (paid, $0.25 a call). Free answers stop at the Delayed date. |
| payment | string | no | Optional: "<macaroon>:<preimage>" after paying the invoice a paid call returned. Send the same arguments again with it. |
What the BTC Intel Score is, its classifications, how it is published and checked, and the definitions used in every answer, in plain words; the method itself is private. Free.
No parameter schema on file.
The published market read in detail: each of the five market areas (Technical, On-chain, Market structure, Sentiment, Macro) with its state, its position on the five-step scale (Adverse, Cautionary, Neutral, Constructive, Supportive), its explanation and last change, and the components its Analysis page shows (26 in all), each with its state and position, with each area's edition time. Optional ar
| Parameter | Type | Required | Notes |
|---|---|---|---|
| area | string | no | Optional: one area (technical, on-chain, market-structure, sentiment, macro). All five when left out. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install BTC Intel or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 7 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest6df06241159c7e8ea3ad1f8f293facd76ad7c7934184066a1f6a441c64081a0c
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_delayed_score | no tags | |
| get_market_read | no tags | |
| get_brief | no tags | |
| get_plan_rules | no tags | |
| get_live_score | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_btc_intel_score | no tags | |
| get_score_momentum | no tags | |
| get_score_statistics | no tags | |
| get_score_history | no tags | |
| get_classification_history | no tags | |
| get_daily_intelligence_brief | no tags | |
| get_methodology | no tags | |
| get_market_detail | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest6df06241159c7e8e
Scanned2026-11-07
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish BTC Intel can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.