Is the Stevesignals Steve Guard MCP server down?

mcp-registry/com.stevesignals.api/steve-guard · v1.0.0

healthy
Last checked 2026-10-18 11:07 UTC · handshake 521ms

As of 2026-10-18 11:07 UTC, the Stevesignals Steve Guard MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
100%
checks observed
3,656
outages (90d)
5
tools
15

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

Install Stevesignals Steve Guard MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (77/100)

C (77/100): 0 error(s), 3 warning(s) across 15 tool(s); ~2,184 tokens of tool definitions.
Scores higher than 29% of 15,364 MCP servers Glimind has audited.
Its tool list costs an agent ~2,184 tokens per session — lighter than 55% of servers.
77 → 77 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions67
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (4)

15 of 15 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: build_swap, check_mint, check_robinhood, check_robinhood_honeypot, copy_signals and 10 more

9 parameter(s) across 5 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: build_swap, copy_signals, recent_events, score_mint, verify_claim

Handshake + tools/list takes ~1,846 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.stevesignals.api%2Fsteve-guard/fixes

check_mint 1 change
{
  "name": "check_mint",
  "description": "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).",
  "inputSchema": {
    "type": "object",
    "required": [
      "mint"
    ],
    "properties": {
      "mint": {
        "type": "string",
        "description": "Solana mint address (base58)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
check_robinhood 1 change
{
  "name": "check_robinhood",
  "description": "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 ",
  "inputSchema": {
    "type": "object",
    "required": [
      "token"
    ],
    "properties": {
      "token": {
        "type": "string",
        "description": "Robinhood-chain ERC-20 token address (0x..., 42 chars)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
check_robinhood_honeypot 1 change
{
  "name": "check_robinhood_honeypot",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "token"
    ],
    "properties": {
      "token": {
        "type": "string",
        "description": "Robinhood-chain ERC-20 token address (0x..., 42 chars)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.stevesignals.api/steve-guard"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.stevesignals.api/steve-guard"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.stevesignals.api%2Fsteve-guard.svg)](https://glimind.com/server/mcp-registry%2Fcom.stevesignals.api%2Fsteve-guard?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.stevesignals.api%2Fsteve-guard?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.stevesignals.api%2Fsteve-guard.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.stevesignals.api%2Fsteve-guard.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.stevesignals.api%2Fsteve-guard?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:84f6fb41b8007246…, first seen 2026-10-17, included at leaf 13295 of 21,589. Version history · verify what your client received.

Tools (15)

Compare: most reliable finance servers · most reliable security servers · most reliable data servers · most reliable other servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Stevesignals Steve Guard MCP server down right now?

As of 2026-10-18 11:07 UTC, the Stevesignals Steve Guard MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 5 minutes.

How many tools does Stevesignals Steve Guard MCP server provide?

Stevesignals Steve Guard MCP server advertises 15 tools, including build_swap, check_mint, check_robinhood, check_robinhood_honeypot, copy_signals.

How do I install Stevesignals Steve Guard MCP server?

Point your MCP client at this streamable-http endpoint: https://api.stevesignals.com/mcp

Is the Stevesignals Steve Guard MCP server safe to connect to an AI agent?

Glimind scanned all 15 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Stevesignals Steve Guard MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.