Is the Speteai Agentdata MCP server down?

mcp-registry/io.github.speteai/agentdata-mcp · v1.0.0

Also listed as pulsemcp/agentdata

healthy
Last checked 2026-10-22 18:37 UTC · handshake 302ms

As of 2026-10-22 18:37 UTC, the Speteai Agentdata MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
100%
checks observed
4,325
outages (90d)
14
tools
35

Verifiable crypto signals, recorded history and always-on monitoring for AI agents via x402 on Base.

Install Speteai Agentdata MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http speteai-agentdata-mcp-server https://agentdata-api.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "speteai-agentdata-mcp-server": {
      "type": "http",
      "url": "https://agentdata-api.com/mcp"
    }
  }
}

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

Agent-readiness: B (81/100)

B (81/100): 0 error(s), 2 warning(s) across 35 tool(s); ~5,346 tokens of tool definitions.
Scores higher than 35% of 15,554 MCP servers Glimind has audited.
Its tool list costs an agent ~5,346 tokens per session — more than 60% of servers.
80 → 81 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions80
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

35 of 35 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: get_arbitrage_opportunities, get_arbitrage_spread_history, get_base_activity, get_changes_since_last_call, get_correlation and 30 more

10 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: get_historical, get_new_memecoins, get_support_resistance, get_technical_indicators, watch_condition

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: 31 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%2Fio.github.speteai%2Fagentdata-mcp/fixes

get_arbitrage_opportunities 1 change 
{
  "name": "get_arbitrage_opportunities",
  "description": "Cross-exchange spreads MEXC/Binance/Bybit/OKX ($0.005 USDC)",
  "inputSchema": {
    "type": "object",
    "properties": {
      "payment": {
        "type": "string",
        "description": "Optional. Base64 x402 payment payload you signed yourself (ERC-3009 TransferWithAuthorization, USDC on Base). Call without it once to receive the payment requirements, sign those, then call again with this argument. This server forwards the payload and never holds a key."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_arbitrage_spread_history 1 change 
{
  "name": "get_arbitrage_spread_history",
  "description": "30 days of hourly cross-exchange spreads (MEXC/Binance/Bybit/OKX) ($0.015 USDC). Every venue publishes its own prices; nobody archives the spread between them.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "payment": {
        "type": "string",
        "description": "Optional. Base64 x402 payment payload you signed yourself (ERC-3009 TransferWithAuthorization, USDC on Base). Call without it once to receive the payment requirements, sign those, then call again with this argument. This server forwards the payload and never holds a key."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_base_activity 1 change 
{
  "name": "get_base_activity",
  "description": "Base network TPS + block activity ($0.003 USDC)",
  "inputSchema": {
    "type": "object",
    "properties": {
      "payment": {
        "type": "string",
        "description": "Optional. Base64 x402 payment payload you signed yourself (ERC-3009 TransferWithAuthorization, USDC on Base). Call without it once to receive the payment requirements, sign those, then call again with this argument. This server forwards the payload and never holds a key."
      }
    }
  },
  "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/io.github.speteai/agentdata-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.speteai/agentdata-mcp"}) 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%2Fio.github.speteai%2Fagentdata-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.speteai%2Fagentdata-mcp?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.speteai%2Fagentdata-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.speteai%2Fagentdata-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.speteai%2Fagentdata-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.speteai%2Fagentdata-mcp?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:2f84e3a9d446cb98…, first seen 2026-10-17, included at leaf 4857 of 47,510. Version history · verify what your client received.

Tools (35)

Compare: most reliable finance servers · most reliable data 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 Speteai Agentdata MCP server down right now?

As of 2026-10-22 18:37 UTC, the Speteai Agentdata MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Speteai Agentdata MCP server provide?

Speteai Agentdata MCP server advertises 35 tools, including get_arbitrage_opportunities, get_arbitrage_spread_history, get_base_activity, get_changes_since_last_call, get_correlation.

How do I install Speteai Agentdata MCP server?

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

Is the Speteai Agentdata MCP server safe to connect to an AI agent?

Glimind scanned all 35 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 Speteai Agentdata 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.

Feedback
Help us improve