Home / MCP registry index / dev.workers.perpgap.perp-gap-api/perp-gap
Perp Gap API
dev.workers.perpgap.perp-gap-api/perp-gap in the official MCP registry.
Endpoint https://perp-gap-api.perpgap.workers.dev/mcp.
The registry describes it as: Stock-perp gaps, verdicts and Hyperliquid prediction-market odds vs perp-implied probability. x402.
We read its 14 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
list_markets get_quote get_funding get_token_premium get_token_liquidity get_gap_sample get_gaps get_verdict get_history get_export get_research_card list_pm_markets get_pm_implied get_pm_scan
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dev-workers-perpgap-perp-gap-api-perp-gap)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.