Is the Perpdata MCP server down?

mcp-registry/dev.perpdata/perpdata · v0.1.0

Also listed as github/perpdata/perpdata

healthy
Last checked 2026-10-19 19:41 UTC · handshake 295ms

As of 2026-10-19 19:41 UTC, the Perpdata MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,895
outages (90d)
0
tools
6

Normalized perp funding (apr), OI, liquidations and cross-venue spreads. Free tier, no key needed.

Install Perpdata MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http perpdata-mcp-server https://api.perpdata.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "perpdata-mcp-server": {
      "type": "http",
      "url": "https://api.perpdata.dev/mcp"
    }
  }
}

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

Agent-readiness: C (78/100)

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

What to fix (3)

6 of 6 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_funding_history, get_funding_rates, get_funding_spreads, get_liquidations, get_open_interest and 1 more

2 parameter(s) across 2 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_funding_history, get_open_interest

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: 6 corrected tool definitions

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

get_funding_history 1 change 
{
  "name": "get_funding_history",
  "description": "Historical funding-rate snapshots (5-min resolution), newest first.",
  "inputSchema": {
    "type": "object",
    "required": [
      "symbol"
    ],
    "properties": {
      "limit": {
        "type": "number",
        "description": "Max rows, default 50, cap 500"
      },
      "venue": {
        "type": "string",
        "description": "Optional venue filter"
      },
      "symbol": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_funding_rates 1 change 
{
  "name": "get_funding_rates",
  "description": "Current perp funding rate per venue for a symbol, with annualized apr (0.05 = 5%/yr) and cross-venue spread. Venues: binance, bybit, okx, hyperliquid, bitget, gate.",
  "inputSchema": {
    "type": "object",
    "required": [
      "symbol"
    ],
    "properties": {
      "symbol": {
        "type": "string",
        "description": "Base asset, e.g. BTC"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_funding_spreads 1 change 
{
  "name": "get_funding_spreads",
  "description": "Ranked cross-venue funding spread per symbol (max apr minus min apr, decimals). Answers: where does the same perp pay most differently right now?",
  "inputSchema": {
    "type": "object",
    "properties": {
      "limit": {
        "type": "number",
        "description": "Max symbols, default 10, cap 25"
      }
    },
    "additionalProperties": false
  },
  "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/dev.perpdata/perpdata"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.perpdata/perpdata"}) 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%2Fdev.perpdata%2Fperpdata.svg)](https://glimind.com/server/mcp-registry%2Fdev.perpdata%2Fperpdata?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fdev.perpdata%2Fperpdata?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.perpdata%2Fperpdata.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.perpdata%2Fperpdata.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.perpdata%2Fperpdata?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:eb9837b50554a83f…, first seen 2026-10-17, included at leaf 1680 of 28,428. Version history · verify what your client received.

Tools (6)

Compare: 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 Perpdata MCP server down right now?

As of 2026-10-19 19:41 UTC, the Perpdata MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Perpdata MCP server provide?

Perpdata MCP server advertises 6 tools, including get_funding_history, get_funding_rates, get_funding_spreads, get_liquidations, get_open_interest.

How do I install Perpdata MCP server?

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

Is the Perpdata MCP server safe to connect to an AI agent?

Glimind scanned all 6 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 Perpdata 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