Northcap Signals

io.github.MohamedAbdisamedPublished by GitHub account MohamedAbdisamedv1.0.0Updated Oct 24, 2026

Pay-per-call DRT/ICT crypto trading signals for AI agents (LONG/SHORT, entry/SL/TP).

The publisher's own server: SIGNALS Loyalty Agent Platform

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

A remote MCP endpoint that supplies pay-per-call DRT/ICT crypto trading signals, including LONG/SHORT direction with entry, stop-loss and take-profit levels.

What you can do
Northcap Signals is a remote MCP server that provides crypto trading signals to an AI assistant. According to its registry description, it delivers DRT/ICT signals with LONG or SHORT direction and entry, stop-loss and take-profit levels. No tool list is published, so the exact callable operations are not documented here.
When to use it
Consider it if you want an assistant to pull crypto trading signal ideas in the DRT/ICT style and discuss entry, stop-loss and take-profit levels. It is not a general-purpose market data or portfolio tool, and its value depends on trusting the signal source.
Requirements
It runs as a remote streamable HTTP endpoint, so no local runtime or package install is needed. The manifest declares no authentication, environment variables or headers, and no account or API key is documented. Network access to the provider's endpoint is required.
Before you install
The description says signals are pay-per-call, so using it may incur charges; confirm pricing and how payment is handled before connecting. No authentication is declared, so treat any data sent to the endpoint as going to a third party. Signals are not financial advice and trading can lose money.

Installation

In SourceWeft

  1. Open Northcap 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.MohamedAbdisamed%2Fnorthcap-signals/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": {
    "northcap-signals": {
      "type": "http",
      "url": "https://horse-contrast-chemical-affect.trycloudflare.com/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.

Other Signals integrations