Skip to content

Steve Signals MCP server

Which MCP servers are Steve Signals's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-25

← Back to Steve Signals

Whose server it is
  • Registry namecom.stevesignals.api/steve-guardverified in the MCP registry

The registry name sits under stevesignals.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-25
  • Stateanswerschecked 2026-10-25
  • Tools15
  • Server calls itselfsteve-guard
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 216 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: screen tokens for honeypots and sell restrictions before buying; measure net dollar flow behind buy and sell counts.
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • For "screen tokens for honeypots and sell restrictions before buying", the likely first call is check_robinhood_honeypot.
  • For "measure net dollar flow behind buy and sell counts", the likely first call is flow_inflection.
  • Parameters are untyped or undescribed in 5 of 15 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-25
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer528 ms
  • Space in an agent's context≈ 1,993 tokensthe definitions of all its tools (15), which an agent carries on every turn
  • Tool definitionsB · 78 of 100
  • Typed results0 of 15 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 5 of 15
  • Not saying whether it only reads or can destroy: 15 of 15

What an agent can do with it

  • can do · screen tokens for honeypots and sell restrictions before buying
  • can do · measure net dollar flow behind buy and sell counts
  • not sure · track whether new wallet buyers are accelerating

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers15 tools · read 2026-10-25
  • check_mint

    Trap check for a fresh Solana mint (pump.fun focus): rug-check verdict, dev first-buy SOL, reserves, liveness. Safety screen, not a profit claim; verify via track_record. Free 10/day, then $0.01/check (see guard_pricing).

  • flow_inflection

    Has net-USD money-flow DIRECTION just flipped for this token? Unique temporal signal (not a static snapshot): returns flow_state = ACCUMULATING / DISTRIBUTION_ONSET (money started leaving in the last hour vs prior window — early exit) /…

  • impersonation_check

    Is THIS token the REAL contract for its ticker, or a same-symbol copycat? Scammers reuse famous/existing tickers; an agent told to buy '$FOO' needs the legit contract. Returns rank-by-liquidity among all same-symbol tokens on-chain…

  • exit_check

    Can you get OUT of a $size position, and at what slippage? Not binary 'sellable' — size-aware exit-liquidity. A token can be sellable yet trap you (thin pool: exiting $5k costs 20%+). Returns exit_slippage_pct for your size, max exit…

  • timing_signal

    Is NOW a good entry, a wait, or an exit point? Fuses three axes no other tool combines: money-flow DIRECTION (capital arriving vs leaving, from temporal net-USD), price EXTENSION (already run / fresh / crashing), and short-term MOMENTUM…

  • exhaustion

    Pressure RATE-OF-CHANGE (2nd derivative) — a signal no other tool computes. Measures whether buy/sell pressure is ACCELERATING or EXHAUSTING across consecutive time-buckets. signal = SELL_EXHAUSTION (price falling but sell-pressure…

  • track_record

    Machine-readable, append-only signal track record. Includes a by_signal_type breakdown: for each signal (ENTER, EXIT_NOW, STEALTH_ACCUM, DISTRIBUTION_TRAP, TAKE_PROFIT…) the sample size and average 1h/6h/24h return plus directional…

  • guard_pricing

    Pricing + x402-style payment instructions (USDC on Solana, on-chain verified instant redeem).

  • recent_events

    Live on-chain events (fresh launches, graduations, whale big-buys). Last 30min free; historical is paid. K3 event stream.

  • verify_claim

    Adversarial red-team of a trading claim/backtest: small-n, CI, tail-driven expectancy, asymmetric window, circularity, unaccounted cost. Returns flags + verdict. K1 verification service.

  • score_mint

    Validated-edge score: reports ONLY signals that passed our locked-holdout validation (strong-start mcap >=3x -> graduation 0.8%->33%, low reserve -> OR 0.35, fast-graduation rug risk). Descriptive base-rate shift, not a price prediction.

  • copy_signals

    Recent buys by wallets with PROVEN realized on-chain PnL (win-rate + SOL profit shown), each with a live Guard safety check and an execution hint. HONEST: wallet track records are real; the EV of copying them is under live validation, not…

  • build_swap

    Build a NON-CUSTODIAL Solana swap transaction (via Jupiter) with a 0.20% service fee embedded + a Guard safety check on the output mint. Returns an UNSIGNED transaction; the agent signs and sends with its own wallet. We never hold keys or…

  • check_robinhood_honeypot

    Robinhood Chain (EVM, chain 4663) token honeypot check via REAL on-chain buy+sell SIMULATION (stateOverride detector-contract, no funds spent). Detects sell-blocked / whitelist / high-tax honeypots that static analysis (e.g. GoPlus)…

  • check_robinhood

    Robinhood Chain (chain 4663) token pre-buy INTEL — near-zero competitor coverage. One call: safety (honeypot/tax/mint via GoPlus) + wallet distribution (top-holder %, holders) + NET-USD wallet-footprint (buy$ vs sell$, repeat-buyers…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "steve-guard": {
      "type": "http",
      "url": "https://api.stevesignals.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http stevesignals https://api.stevesignals.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.stevesignals.com/mcp as a custom connector in the settings.

OpenAPI spec

42 paths, read 2026-10-25. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.