DeepBlue Trading Intelligence

xyz.deepbluebasePublished by deepbluebase.xyzOfficial publisherv1.0.0Updated Oct 24, 2026

Live crypto trading signals, sentiment, Polymarket analytics. Free demo + x402 micropayments.

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

A remote MCP endpoint offering live crypto trading signals, market sentiment and Polymarket analytics, with a free demo and paid micropayment access.

What you can do
Access live crypto trading signals and market sentiment data through the remote endpoint, plus Polymarket analytics. The manifest lists no individual tools, so the exact operations are not documented here. Access is offered through a free demo tier and x402 micropayments for paid use.
When to use it
Consider it when an assistant needs crypto market signals, sentiment readings or Polymarket analytics during trading research or market monitoring. The free demo lets you evaluate it before paying.
Requirements
A remote streamable HTTP connection to the provider's endpoint; no local runtime, package, environment variables or headers are declared. No authentication is declared, but paid use relies on x402 micropayments, which typically require a funded crypto wallet.
Before you install
Paid access uses x402 micropayments, so using it beyond the free demo can spend real funds from a crypto wallet. The server is financial in nature; signals and sentiment are third-party data, not investment advice. No tools, authentication or data-handling details are documented, so verify behavior before relying on it.

Installation

In SourceWeft

  1. Open DeepBlue Trading Intelligence 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/xyz.deepbluebase%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-trading-intelligence": {
      "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.0LatestSep 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.