Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Manta Signal Gate

REMOTE · SIGNALS.EASYRIDER.ONE

Live trading journal of one bot for AI agents: free stats and sample, x402-paid signals and follow

+4 this week 71 Trust /100

Last scanned (7 minutes ago)

Scores higher than 61% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 446 tokens (~63/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 30. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Oct 26 +3

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 20. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 3 Oct 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Probed https://signals.easyrider.one/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=signals.easyrider.one CN=YE2,O=Let's Encrypt,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA384 5c7d35ee2f45455d7a7a43f07020e272d95
SANs: signals.easyrider.one
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of signals.easyrider.one. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
one. present 64939 8 Verified
easyrider.one. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://signals.easyrider.one/mcp Verified 200
http (plaintext) http://signals.easyrider.one/mcp HTTPS enforced 308 https://signals.easyrider.one/mcp
MCP tools · 7 exposed · ~345 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
follow_events ~68

With a follow token from subscribe_follow. New trading events with ids; pass the returned cursor as 'after' to continue. Act only on events with a small age_seconds.

NameTypeReqDescription
afterinteger––
limitinteger––
tokenstringyestoken from subscribe_follow

No output schema declared.

No examples provided.

follow_state ~39

With a follow token from subscribe_follow. The bot's current positions, to reconcile your own book.

NameTypeReqDescription
tokenstringyestoken from subscribe_follow

No output schema declared.

No examples provided.

get_history ~39

PAID via x402 ($0.25 USDC). The full event history of the live bot and its statistics. You are charged only on success.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_sample ~28

Free. Open positions and recent events delayed by 30 minutes, a sample of the paid data.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_signals ~80

PAID via x402 ($0.05 USDC). Live open positions with entry, stop loss, take profit, last price and the events of the last 24 hours. The call returns a payment-required error until an x402 payment is attached to the request _meta. You are charged only on success; stale data is refused and costs nothing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_status ~46

Free. Statistics of the live bot (closed trades, win rate, live days, small_sample), a summary of the open book and the freshness of the data. Read this before paying.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

subscribe_follow ~45

PAID via x402 ($1.00 USDC). Returns a token valid for 24 hours. Pass it to follow_events and follow_state. You are charged only on success.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Manta Signal Gate MCP server?

Manta Signal Gate is a hosted endpoint at https://signals.easyrider.one/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · signals.easyrider.one

# add to Claude Code
claude mcp add --transport http one-easyrider-signal-gate 'https://signals.easyrider.one/mcp'
Common questions

What is the Manta Signal Gate MCP server?

Manta Signal Gate is an MCP server listed in the public MCP registry as one.easyrider/signal-gate. Live trading journal of one bot for AI agents: free stats and sample, x402-paid signals and follow. This page covers its hosted endpoint (https://signals.easyrider.one/mcp).

Is the Manta Signal Gate MCP server safe to use?

Manta Signal Gate scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Manta Signal Gate MCP server expose?

Manta Signal Gate exposes 7 tools: get_status, get_sample, get_signals, get_history, subscribe_follow, and 2 more. Their descriptions and schemas cost roughly 345 tokens of context every time the server is loaded.

Does the Manta Signal Gate MCP server require authentication?

No. We connected to Manta Signal Gate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Manta Signal Gate MCP server still maintained?

Manta Signal Gate is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.