Bitcoincreditstack MCP

Name: Bitcoincreditstack MCP
Author: JamieFrame

by JamieFrameversion 0.1.0i★ –iRuns in the cloud

Registry namecom.bitcoincreditstack/mcp

Install

Overview

Description from the maker (original English)

The Bitcoin credit markets, measured. Cross-venue rates, venue criteria, chain indicators.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi0 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 0 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.bitcoincreditstack.com/mcp

Run this in your terminal

claude mcp add --transport http bitcoincreditstack https://mcp.bitcoincreditstack.com/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "bitcoincreditstack": {
      "url": "https://mcp.bitcoincreditstack.com/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "bitcoincreditstack": {
      "type": "http",
      "url": "https://mcp.bitcoincreditstack.com/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.bitcoincreditstack.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

! Caution
Maker matches the repo
The publisher (bitcoincreditstack.com) is not the repo owner (JamieFrame); someone else may have listed it
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32466 servers in this category
Published to the registry more recently than 31% of the other 32466 servers in this category
Basic checks equal to or better than 33% of the other 32466 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Bitcoincreditstack MCP safe?

It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

HotCodePush

by hotcodepush-team

Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

gavel-mcp-server

Aletheia Analytics MCP server — agent-native interface over the Gavel data product.

Thin TypeScript wrapper around api.thegavel.io. Exposes Gavel credit data and Bitcoin on-chain indicators as MCP tools so LLM-driven agents (Claude Desktop, IDE clients, custom agents) can read the data product without hand-rolling REST glue.

Status

All three layers of the AI concierge spec (aletheia-docs data/specs/mcp/ai_concierge.md) are live, plus the indicator surface and real key→tier resolution. Delivered by Runbook R18 and governed by the decisions note data/specs/mcp/tier_and_scope_decisions_v1.md (MD1–MD12).

Layer A — read state

Tool	Upstream
`check_wallet_status`	direct RPC (balances, allowances, readiness blockers)
`find_auctions_matching_criteria`	`/v1/auctions`
`get_user_positions`	`/v1/user/:address/positions`
`get_loan_status`	`/v1/loans/:id/status`

Layer B — factory model (unsigned blueprints; the user signs)

Tool	Encodes
`prepare_bid_calldata`	`placeBid` + approval when allowance is short
`prepare_create_auction_calldata`	`createAuction` + collateral approval
`prepare_repay_loan_calldata`	`repayLoan` + repayment approval
`prepare_claim_collateral_calldata`	`claimCollateral`
`prepare_claim_refund_calldata`	`claimRefund`

Layer C — catalogues

Tool	Notes
`list_wallet_options`	static catalogue, no ranking
`recommend_fiat_onramp`	static catalogue; carries the two-purchase gas requirement

Data surface

Tool	Upstream
`list_gavel_indicators`	static catalogue of 32 indicators
`get_gavel_indicator`	`/v1/credit/`, `/v1/onchain/`, `/v1/market/*`
`get_yield_curve`	`/v1/yield-curve`
`get_mvrv`	`/v1/onchain/mvrv`
`get_protocol_reference`	static — addresses, signatures, conventions
`list_onchain_indicators`	static catalogue

The invariant

Aletheia builds; the user signs. There is no signing surface in this codebase — no wallet client, no account, no key material. viem is imported for encodeFunctionData only. That is what makes "Aletheia never signs" an architectural fact rather than a policy promise, and it must stay that way.

Equally load-bearing: no tool ranks, scores, or selects on the user's behalf. Filtering by user-supplied criteria is an information service; ranking by an internal model is investment advice. find_auctions_matching_criteria is named as it is deliberately, and the naming is not cosmetic.

Architecture

LLM Client → mcp.thegavel.io (this server) → api.thegavel.io (REST) → PostgreSQL

[tool catalog, descriptions, [authoritative endpoints] response shaping, auth, limits]

Single source of truth: the REST API. The MCP server never queries Postgres directly. Tools shape responses for LLM consumption (JSON-stringified text content) but never re-implement business logic. When the REST API upgrades, MCP inherits the upgrade automatically.

Local development

# Install deps (Node 20+)

npm install

Copy and edit env file

cp .env.example .env nano .env # set GAVEL_API_BASE_URL etc.

Dev mode (tsx watch)

npm run dev

Type check

npm run typecheck

Build to dist/

npm run build

Point a development MCP client (MCP Inspector, Claude Desktop with an HTTP connector) at http://localhost:3002/mcp to exercise tools.

Deployment

Target: gavel-btc Hetzner host, alongside gavel-api.

# Local — build and stage

npm install npm run build

Copy to server

scp -r dist/ package.json package-lock.json deployment/ \ root@gavel-btc:/root/gavel-mcp/

On server — install runtime deps (not the full dev set)

ssh root@gavel-btc cd /root/gavel-mcp npm install --omit=dev

Configure

cp .env.example .env nano .env

Set:

GAVEL_API_BASE_URL=https://api.thegavel.io (public API, for tool reads)

GAVEL_API_INTERNAL_URL=http://127.0.0.1:4012 (loopback, for tier lookup)

INTERNAL_API_SECRET=

PORT=3002

NODE_ENV=production

Install systemd unit

cp deployment/gavel-mcp.service /etc/systemd/system/ systemctl daemon-reload systemctl enable gavel-mcp.service systemctl start gavel-mcp.service

Verify

journalctl -u gavel-mcp -n 50 --no-pager curl http://localhost:3002/health

Reverse proxy

cp deployment/nginx-mcp.conf /etc/nginx/sites-available/mcp.thegavel.io ln -s /etc/nginx/sites-available/mcp.thegavel.io \ /etc/nginx/sites-enabled/mcp.thegavel.io nginx -t && systemctl reload nginx

TLS (Let's Encrypt)

certbot --nginx -d mcp.thegavel.io

End-to-end check

curl https://mcp.thegavel.io/health

Configuration

All knobs live in .env:

Var	Default	Purpose
`PORT`	`3002`	HTTP listen port
`NODE_ENV`	—	`production` for JSON logs
`LOG_LEVEL`	`info`	pino level (`trace`/`debug`/`info`/`warn`/`error`)
`GAVEL_API_BASE_URL`	`http://localhost:3001`	Upstream REST base URL
`RATE_LIMIT_ANONYMOUS_PER_MINUTE`	`60`	Anonymous bucket size
`RATE_LIMIT_PAID_PER_MINUTE`	`300`	Paid bucket size
`CORS_ALLOWED_ORIGINS`	empty	Comma-separated; empty = no CORS
`HEALTH_CHECK_SECRET`	empty	If set, `/health` requires `?secret=...`
`GAVEL_API_INTERNAL_URL`	`http://127.0.0.1:4012`	Key→tier lookup. Must be the loopback address — `/internal/resolve-tier` refuses any request carrying an `X-Forwarded-For`, so the public `api.thegavel.io` host will not work
`INTERNAL_API_SECRET`	empty	Shared secret for the tier lookup. Must match `gavel-indexer/.env.mainnet`. Unset ⇒ every caller resolves to `free`
`MCP_TIER_ENFORCEMENT`	`false`	Enforce per-tool tiers. Leave `false` until Gate B — see Tier model
`ARBITRUM_RPC_URL`	public RPC	Chain reads for Layer A/B. Point at a paid endpoint in production
`ARBITRUM_SEPOLIA_RPC_URL`	public RPC	Testnet equivalent

Tier model

The ladder is free / pro / enterprise — identical to the product's (gavel-indexer/lib/tiers.js) and to what Stripe sells. The scaffold's original anonymous / developer / professional / enterprise was a second vocabulary for one entitlement and is retired (MD1).

gavel-indexer/lib/api-keys.js is the authority on what tier a key is. The MCP does not open its own database pool; it asks GET /internal/resolve-tier over loopback, caches the answer for 60 s, and fails open to `free` on any error. A data MCP that 500s because the key database hiccuped is worse than one that briefly serves anonymous.

Enforcement is authored but OFF

MCP_TIER_ENFORCEMENT defaults to false, and that is the correct state today. Monetisation is gated until Gate B (D16–D18): *do not build a paywall until someone has asked to pay*. Runbook A2 withdrew the commercial surface, and www.thegavel.io/pricing currently states that data access is free and open — so refusing a tool and pointing the user at a page which denies tiers exist would be a self-refuting journey.

With the flag off, requireTier still resolves the caller's real tier and logs what it would have refused. That log is the evidence for M6, the "has anyone actually asked to pay?" gate condition.

Before flipping it on, read MD2. There are two incompatible readings of what a paid MCP means — whole-surface-paid (lib/tiers.js carries mcp: false on free) versus depth-paid (MD3, the endorsed one). They are very different products.

What is free, and why

Per MD3, inheriting the D5 route/depth map: raw on-chain state, auction discovery, wallet status, commodity on-chain indicators, the current value of any Gavel-derived assessment, and history are all free. History is free because D9 retired the 30-day REST cap, and the MCP must not reintroduce a fence the surface it mirrors has abandoned. The paid boundary is bulk delivery, which this server does not offer.

Participation is never gated (D3). Every Layer A/B/C tool is free: a would-be bidder must never meet a paywall between deciding to bid and being able to.

Rate limits are infrastructure protection, not a billing meter (D2), and apply irrespective of the enforcement flag.

Redeploying a change

npm run build            # tsc -> dist/ ; must be clean

systemctl restart gavel-mcp systemctl is-active gavel-mcp journalctl -u gavel-mcp -n 30 --no-pager

This service is systemd, not pm2. pm2 on this host carries quorum-mcp-testnet, a different service — pm2 restart gavel-mcp is a no-op that looks like a successful deploy. R18 v1 had this wrong; it is recorded in that runbook's §8.

The service runs dist/, not src/, so a change that is not built is a change that is not deployed.

Adding a tool

Create src/tools/ / .ts. Copy credit/yield-curve.ts as the template — it's the cleanest worked example.
Define a Zod schema for inputs with .describe() on every field; that description is what the LLM sees during tool discovery.
Write the tool description as a multi-line string. Lead with what the indicator is, give interpretive context (without recommending anything), and document the response shape. The MCP SDK uses this verbatim in the catalog.
Body: requireTier(...) → upstreamGet(...) → return { content: [{ type: 'text', text: JSON.stringify(...) }] }.
Register the tool in src/tools/index.ts.
Add an entry to src/tools/discovery/list-onchain.ts (or the equivalent discovery catalog for that domain).

Testing manually

# 1. Health

Bitcoincreditstack MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

HotCodePush

README from the maker

gavel-mcp-server

Status

The invariant

Architecture

Local development

Copy and edit env file

Dev mode (tsx watch)

Type check

Build to dist/

Deployment

Copy to server

On server — install runtime deps (not the full dev set)

Configure

Set:

GAVEL_API_BASE_URL=https://api.thegavel.io (public API, for tool reads)

GAVEL_API_INTERNAL_URL=http://127.0.0.1:4012 (loopback, for tier lookup)

INTERNAL_API_SECRET=

PORT=3002

NODE_ENV=production

Install systemd unit

Verify

Reverse proxy

TLS (Let's Encrypt)

End-to-end check

Configuration

Tier model

Enforcement is authored but OFF

What is free, and why

Redeploying a change

Adding a tool

Testing manually

2. MCP Inspector

Connect to http://localhost:3002/mcp

Verify: tools/list returns 3 tools, get_yield_curve returns live data,

get_mvrv returns a structured McpError "not found".

License