DeepBlue Crypto Signals

io.github.ERROR403agentPublished by GitHub account ERROR403agentv1.0.2Updated Oct 24, 2026

10 crypto tools for AI agents: BTC/ETH/SOL/XRP momentum signals, Polymarket odds, sentiment, x402.

The publisher's own server: SIGNALS Loyalty Agent Platform

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

A remote MCP endpoint offering AI assistants ten crypto tools, including BTC/ETH/SOL/XRP momentum signals, Polymarket odds, sentiment and x402.

What you can do
Retrieve momentum signals for BTC, ETH, SOL and XRP from the assistant's conversation context, without needing a local install or API key setup.
When to use it
Useful when you want an assistant to pull crypto market signals, prediction-market odds or sentiment into a conversation, for example while researching or discussing digital-asset markets.
Requirements
Connects to a hosted remote endpoint over streamable HTTP; no local runtime, package, environment variables or headers are declared. Network access to the provider's endpoint is required.
Before you install
The provider declares no authentication, so treat any data returned as unverified third-party information. Signals and odds are informational and may be inaccurate; do not rely on them for trading or financial decisions without independent checks.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. 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/io.github.ERROR403agent%2Fdeepblue-trading/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": {
    "deepblue-crypto-signals": {
      "type": "http",
      "url": "https://mcp.deepbluebase.xyz/mcp"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

25% 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
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Signals integrations