Log inSubmit server

Bitcoin Signals vs PubFi MCP

A side-by-side look at the Bitcoin Signals and PubFi MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

B
Bitcoin SignalsFinance & Fintech · Remote HTTP/SSESignal-first Bitcoin intelligence: sovereign, hiring & hashrate signals over MCP.39FairAuth: no auth requiredPubFi MCP logoPubFi MCPFinance & Fintech · Local subprocess (stdio)Route crypto data needs through PubFi capability and gateway tools.44FairAuth: not declared

Verdict: choose Bitcoin Signals for finance & fintech work over a hosted endpoint; choose PubFi MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

B
Choose Bitcoin Signals when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
Explore Bitcoin Signals

PubFi MCP logoChoose PubFi MCP when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
Explore PubFi MCP

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
B
Bitcoin Signals		PubFi MCP logoPubFi MCP
CategoryFinance & FintechFinance & Fintech
Quality signal39/100 · Fair44/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNo auth requiredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—0
Directory activity 0 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView Bitcoin Signals View PubFi MCP

Tools & capabilities

Bitcoin Signals tools

No tool names declared yet. Check the project README from the listing page.

PubFi MCP tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Bitcoin Signals

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "bitcoin-signals": {
      "command": "npx",
      "args": [
        "-y",
        "bitcoin-signals"
      ]
    }
  }
}

PubFi MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "pubfi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mint@latest"
      ]
    }
  }
}

Frequently asked questions

Bitcoin Signals is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. PubFi MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick Bitcoin Signals for finance & fintech work and PubFi MCP for finance & fintech.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Bitcoin Signals has no declared pricing — check the project's own site. Auth: no auth required. PubFi MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add bitcoin-signals and pubfi-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Bitcoin Signals has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. PubFi MCP has 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.

Popular comparisons with Bitcoin Signals

Popular comparisons with PubFi MCP