# PerpCheck (remote · api.youraitools.co)

Hyperliquid pre-trade order check: will it be rejected, fix values, liquidation, impact, funding.

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.youraitools.co`: 74/100 (this document), [markdown](https://verifymcp.io/servers/co-youraitools-perpcheck/perpcheck-mcp.md), [page](https://verifymcp.io/servers/co-youraitools-perpcheck/perpcheck-mcp)

## Channel facts

- Endpoint: `https://api.youraitools.co/perpcheck/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 571 tokens (~571/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the PerpCheck MCP server?

PerpCheck is a hosted endpoint at https://api.youraitools.co/perpcheck/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.

### Claude

```bash
claude mcp add --transport http co-youraitools-perpcheck 'https://api.youraitools.co/perpcheck/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-youraitools-perpcheck": {
      "url": "https://api.youraitools.co/perpcheck/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-youraitools-perpcheck": {
      "type": "http",
      "url": "https://api.youraitools.co/perpcheck/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-youraitools-perpcheck]
url = "https://api.youraitools.co/perpcheck/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-youraitools-perpcheck": {
      "type": "remote",
      "url": "https://api.youraitools.co/perpcheck/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-youraitools-perpcheck --url 'https://api.youraitools.co/perpcheck/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-youraitools-perpcheck:
    url: "https://api.youraitools.co/perpcheck/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-youraitools-perpcheck": {
      "Transport": "http",
      "Url": "https://api.youraitools.co/perpcheck/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-youraitools-perpcheck -t streamable-http -u 'https://api.youraitools.co/perpcheck/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-youraitools-perpcheck": {
      "type": "http",
      "url": "https://api.youraitools.co/perpcheck/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 68)

First indexed and scored.

## MCP tools (1)

### `check_perp_order` (~491 tokens)

Hyperliquid pre-trade order check

Checks a Hyperliquid perp order BEFORE your agent sends it: would the exchange reject it, and what does it cost and risk? Give coin, side and size (coins, as you would send it) or notional (USD); optional limit price (omit = market order), leverage, margin cross/isolated, reduceOnly. Returns verdict REJECT_LIKELY / CAUTION / OK, issues[] with fix values (size decimals, price tick, $10 minimum, max leverage by margin tier, isolated-only, OI cap, delisted, far-from-mark), warnings[], rules, isolated liquidation estimate and distance, taker impact from the live L2 book, funding carry per day, market facts, confidence and sources_failed. Read-only: never places, signs or holds orders and needs no keys. Free: 30 calls/day per IP with full results (max 10/min; invalid input is not counted). After that the tool returns an error with the x402 pay URL ($0.01 USDC per full check at /v1/full, or $0.003 lite at /v1/lite) or prepaid credits. Not financial advice; the exchange decides whether an order is accepted. PerpCheck is a read-only pre-trade check: it never places, signs or holds orders, has no custody and never asks for keys.

Input parameters:

- `coin` (string, required): Hyperliquid main-dex perp name, e.g. BTC, ETH, SOL, HYPE, kPEPE
- `leverage` (number): Leverage, e.g. 10 (default 1)
- `margin` (string): cross (default) or isolated
- `notional` (number): Order value in USD (instead of size), e.g. 100
- `price` (string|number): Limit price exactly as you would send it (tick rule is checked). Omit for a market order (then taker impact is estimated from the L2 book).
- `reduceOnly` (boolean): true if the order only reduces a position (exempt from the minimum and OI cap)
- `side` (string, required): long/buy or short/sell
- `size` (string|number): Order size in coins, exactly as you would send it (decimals are checked), e.g. 0.001. Give size or notional.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-youraitools-perpcheck/perpcheck-mcp#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 71
- 2026-10-30: 71
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 69
- 2026-10-26: 69
- 2026-10-25: 68
- 2026-10-24: 68
- 2026-10-23: 68

## Common questions

### What is the PerpCheck MCP server?

PerpCheck is an MCP server listed in the public MCP registry as co.youraitools/perpcheck. Hyperliquid pre-trade order check: will it be rejected, fix values, liquidation, impact, funding. This page covers its hosted endpoint (https://api.youraitools.co/perpcheck/mcp).

### Is the PerpCheck MCP server safe to use?

PerpCheck scores 74 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 PerpCheck MCP server expose?

PerpCheck exposes 1 tool: check_perp_order. Their descriptions and schemas cost roughly 491 tokens of context every time the server is loaded.

### Does the PerpCheck MCP server require authentication?

No. We connected to PerpCheck without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the PerpCheck MCP server still maintained?

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

### What did VerifyMCP test on the PerpCheck MCP server?

VerifyMCP ran 13 checks on PerpCheck, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.youraitools.co/perpcheck/mcp
- Website: https://api.youraitools.co/perpcheck
- Changelog RSS feed: https://verifymcp.io/servers/co-youraitools-perpcheck/perpcheck-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-youraitools-perpcheck/perpcheck-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/co-youraitools-perpcheck/perpcheck-mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-youraitools-perpcheck/perpcheck-mcp