Signal Api

live.bitcoinintelPublished by bitcoinintel.liveOfficial publisherv1.0.0Updated Oct 27, 2026

Bitcoin 15-min prediction signals with on-chain commitment proofs. L402-gated.

VerifiedSSEWeb executableFinanceAI & ML

Overview

AI-generated overview

Remote MCP endpoint that serves Bitcoin 15-minute prediction signals with on-chain commitment proofs, gated by L402 payments.

What you can do
  • Provides Bitcoin 15-minute prediction signals.
  • Pairs each signal with an on-chain commitment proof.
  • Gates access through L402 payment challenges.
  • No tool list is published, so the exact calls an assistant can make are not documented.
When to use it
Consider it if you want an assistant to pull short-horizon Bitcoin prediction signals and check their on-chain commitment proofs, and you are prepared to pay per access via L402.
Requirements
A remote MCP client that supports the SSE transport, connecting to the provider's endpoint. Network access is required. Access is L402-gated, so a Lightning wallet or L402-capable client able to pay invoices is needed. No environment variables or headers are declared.
Before you install
Access is paid: L402 gating means requests may require paying Lightning invoices, so spending real funds is possible. The tool list and signal methodology are undocumented, so treat the signals as unverified third-party output. No authentication is declared in the manifest, so review how credentials and payments are handled before connecting.

Installation

In SourceWeft

  1. Open Signal Api in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/live.bitcoinintel%2Fsignal-api/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "signal-api": {
      "type": "sse",
      "url": "https://mcp.bitcoinintel.live/mcp/sse"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

17% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.