Skip to content

Manta Signal Gate MCP server

one.easyrider/signal-gateeasyrider.onestreamable-httpv0.1.0Scanned

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

7 tools: 3 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 3 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Manta Signal Gate MCP server can do

The Manta Signal Gate MCP server is published by easyrider.one, a domain the MCP Registry verified. It has 7 tools. It can create or change data (3 tools: subscribe_follow, follow_events and follow_state), but cannot delete data. 4 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 5, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 3Claude Code: ask
  • follow_eventsWith a follow token from subscribe_follow.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • follow_stateWith a follow token from subscribe_follow.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    With a follow token from subscribe_follow. The bot's current positions, to reconcile your own book.
  • subscribe_followPAID via x402 ($1.00 USDC).No findings

    Why it is in this group

    • The name "subscribe_follow" says "subscribe": a word for a change.
    Description, as the server wrote it
    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.
Only reads 4Show 4 read-only tools
  • get_historyPAID via x402 ($0.25 USDC).No findings

    Why it is in this group

    • The name "get_history" says "get": a word for reading.
    Description, as the server wrote it
    PAID via x402 ($0.25 USDC). The full event history of the live bot and its statistics. You are charged only on success.
  • get_sampleFree.No findings

    Why it is in this group

    • The name "get_sample" says "get": a word for reading.
    Description, as the server wrote it
    Free. Open positions and recent events delayed by 30 minutes, a sample of the paid data.
  • get_signalsPAID via x402 ($0.05 USDC).No findings

    Why it is in this group

    • The name "get_signals" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_statusFree.No findings

    Why it is in this group

    • The name "get_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:16 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
502
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 502.

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 200 to 502
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 502; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 502
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http signal-gate https://signals.easyrider.one/mcp
claude mcp add --transport http signal-gate https://signals.easyrider.one/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__signal-gate__get_status",
      "mcp__signal-gate__get_sample",
      "mcp__signal-gate__get_signals",
      "mcp__signal-gate__get_history"
    ],
    "ask": [
      "mcp__signal-gate__subscribe_follow",
      "mcp__signal-gate__follow_events",
      "mcp__signal-gate__follow_state"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as signal-gate. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/one.easyrider/signal-gate/verify?hash=005025aba0680be4bdce4e288fa477e2f80254f5e345da203871196ff65f7701" | jq -e '.changed == false'

Pinned hash 005025aba068, from Nov 5, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/one.easyrider/signal-gate/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for one.easyrider/signal-gate
[![Anlyon Radar](https://radar.anlyon.com/badge/one.easyrider/signal-gate.svg)](https://radar.anlyon.com/servers/one.easyrider/signal-gate)

Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.

Manta Signal Gate MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Manta Signal Gate MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Manta Signal Gate MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Manta Signal Gate MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Manta Signal Gate MCP server have?

7 tools: 3 write, 4 read. subscribe_follow, follow_events, follow_state, get_status, get_sample, get_signals and get_history.

Does the Manta Signal Gate MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Manta Signal Gate MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Manta Signal Gate MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 5, 2026.