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.

com.stevesignals.api/steve-guard

REMOTE · API.STEVESIGNALS.COM

Solana + Robinhood-Chain token safety & net-USD accumulation intel for trading agents.

0 this week 72 Trust /100

Last scanned (3 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

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 Security46
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1722 tokens (~114/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 57% 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 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.

  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 0
    • New tool “exhaustion” functional
  • 26 Sept 26 0
    • Stability: 0.97 → pass security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 44% → 55% ▲ functional
    • New tool “exit_check” functional
    • New tool “impersonation_check” functional
    • New tool “timing_signal” functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Sept 26 0
    • Schema quality: 767 → 923 ▼ functional
    • New tool “check_robinhood” functional
  • 30 Aug 26 0
    • Schema quality: 625 → 767 ▼ functional
    • Tool coverage: 31% → 36% ▲ functional
    • New tool “check_robinhood_honeypot” functional
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 5 Nov 2026 · Probed https://api.stevesignals.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=stevesignals.com CN=WE1,O=Google Trust Services,C=US 4 Oct 2026 2 Jan 2027 ECDSA 256 ECDSA-SHA256 eb2d0783618891460e38fc7846741e7f
SANs: stevesignals.com, *.stevesignals.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.stevesignals.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
stevesignals.com. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.stevesignals.com/mcp Verified 200
http (plaintext) http://api.stevesignals.com/mcp Inconclusive 405
MCP tools · 15 exposed · ~1,677 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
build_swap ~120

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 funds.

NameTypeReqDescription
amountintegeryesinput amount in smallest units (lamports for SOL)
input_mintstringyes–
output_mintstringyes–
user_pubkeystringyesthe agent's own wallet pubkey (signer)

No output schema declared.

No examples provided.

check_mint ~80

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).

NameTypeReqDescription
mintstringyesSolana mint address (base58)

No output schema declared.

No examples provided.

check_robinhood ~156

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, strong-loaders) -> 0-100 score + accumulation/distribution verdict. The dollar-weighted net-USD footprint separates real accumulation from a 'count trap' (more buys but net distribution). Specialist coverage generic EVM rug-checkers lack. Free 10/day, then paid via guard_pricing.

NameTypeReqDescription
tokenstringyesRobinhood-chain ERC-20 token address (0x..., 42 chars)

No output schema declared.

No examples provided.

check_robinhood_honeypot ~142

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) MISSES. Verdict: SAFE / HONEYPOT / CANT_BUY + round-trip loss %. Pre-trade safety check for autonomous agents trading Robinhood Chain crypto. Free 10/day, then paid via guard_pricing.

NameTypeReqDescription
tokenstringyesRobinhood-chain ERC-20 token address (0x..., 42 chars)

No output schema declared.

No examples provided.

copy_signals ~78

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 yet proven. Non-custodial.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

exhaustion ~149

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 declining bucket-over-bucket → sellers running out, bottom forming) / BUY_CLIMAX (price rising but buy-pressure fading → buyer appetite peaking, top forming) / ACCELERATION_UP / ACCELERATION_DOWN / STEADY. Leading: pressure-momentum breaks BEFORE the price reversal. RH-chain (0x) or Solana (base58).

NameTypeReqDescription
tokenstringyes0x-address or base58 mint

No output schema declared.

No examples provided.

exit_check ~164

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 under 5%/10% slippage, liquidity, thin-volume warning, verdict = EASY_EXIT/MODERATE/THIN/TRAP/NO_EXIT. Call BEFORE entering to size the position to your real exit capacity. RH-chain (0x) or Solana (base58).

NameTypeReqDescription
size_usdnumber–intended position size in USD (default 1000)
tokenstringyes0x-address or base58 mint

No output schema declared.

No examples provided.

flow_inflection ~132

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) / REVERSAL_UP (money started arriving — early entry) / DISTRIBUTING / CHOPPY. Robinhood-chain (0x) or Solana (base58). Call before an entry to avoid buying a top a static footprint would miss.

NameTypeReqDescription
tokenstringyesRobinhood-chain 0x-address or Solana base58 mint

No output schema declared.

No examples provided.

guard_pricing ~29

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

impersonation_check ~129

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, is_canonical, the real contract if this is an impersonator, a famous-name flag, and impersonation_risk (LOW/MEDIUM/HIGH). Robinhood-chain (0x) or Solana (base58).

NameTypeReqDescription
tokenstringyesRobinhood-chain 0x-address or Solana base58 mint

No output schema declared.

No examples provided.

recent_events ~64

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

NameTypeReqDescription
sinceinteger––
typesstring–comma list: launch,graduation,whale

No output schema declared.

No examples provided.

score_mint ~77

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.

NameTypeReqDescription
mintstringyes–

No output schema declared.

No examples provided.

timing_signal ~164

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. signal = ENTER (money in + price not yet run) / WAIT_PULLBACK (accumulating but extended) / TAKE_PROFIT (distribution after a run) / EXIT_NOW (money out + falling) / WATCH, plus entry_quality 0-100. Best entry = capital in + price fresh; best exit = capital out + price extended. RH-chain (0x) or Solana (base58).

NameTypeReqDescription
tokenstringyes0x-address or base58 mint

No output schema declared.

No examples provided.

track_record ~114

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 accuracy, and calibration_slices (e.g. high-confidence-only, confirmed-only). Lets an agent decide how much to trust each signal type. Paper outcomes, |return|>500% excluded as glitch — descriptive, not a profit promise.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

verify_claim ~79

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.

NameTypeReqDescription
claimstring––
ninteger––
samplearray––
win_ratenumber––

No output schema declared.

No examples provided.

Install

How do I install the com.stevesignals.api/steve-guard MCP server?

com.stevesignals.api/steve-guard is a hosted endpoint at https://api.stevesignals.com/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 · api.stevesignals.com

# add to Claude Code
claude mcp add --transport http com-stevesignals-api-steve-guard 'https://api.stevesignals.com/mcp'
Common questions

What is the com.stevesignals.api/steve-guard MCP server?

com.stevesignals.api/steve-guard is an MCP server listed in the public MCP registry as com.stevesignals.api/steve-guard. Solana + Robinhood-Chain token safety & net-USD accumulation intel for trading agents. This page covers its hosted endpoint (https://api.stevesignals.com/mcp).

Is the com.stevesignals.api/steve-guard MCP server safe to use?

com.stevesignals.api/steve-guard scores 72 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 com.stevesignals.api/steve-guard MCP server expose?

com.stevesignals.api/steve-guard exposes 15 tools: check_mint, flow_inflection, impersonation_check, exit_check, timing_signal, and 10 more. Their descriptions and schemas cost roughly 1,677 tokens of context every time the server is loaded.

Does the com.stevesignals.api/steve-guard MCP server require authentication?

No. We connected to com.stevesignals.api/steve-guard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.stevesignals.api/steve-guard MCP server still maintained?

com.stevesignals.api/steve-guard is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.