Pa1m Hyperliquid
REMOTE · HYPERLIQUID.HYPA1M.XYZ · SCANNED AUG 3
Hyperliquid DEX data: prices, order books, candles, funding rates, portfolios. Pay-per-call, x402.
Available components
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. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared sse, but the endpoint returned HTTP 400. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · hyperliquid.hypa1m.xyz
claude mcp add --transport http retampweb-pa1m-hyperliquid https://hyperliquid.hypa1m.xyz/mcp
[mcp_servers.retampweb-pa1m-hyperliquid] url = "https://hyperliquid.hypa1m.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"retampweb-pa1m-hyperliquid": {
"type": "remote",
"url": "https://hyperliquid.hypa1m.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add retampweb-pa1m-hyperliquid --url https://hyperliquid.hypa1m.xyz/mcp --transport streamable-http
mcp_servers:
retampweb-pa1m-hyperliquid:
url: "https://hyperliquid.hypa1m.xyz/mcp" {
"mcpServers": {
"retampweb-pa1m-hyperliquid": {
"type": "http",
"url": "https://hyperliquid.hypa1m.xyz/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- 31 Jul 26 −31
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
- Schema quality: 616 → 715 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 27 Jul 26 52
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://hyperliquid.hypa1m.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hyperliquid.hypa1m.xyz | CN=YE1,O=Let's Encrypt,C=US | 25 Jul 2026 | 23 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 534817ba9cbc4593bfc0bfc746dc6d85b24 |
| SANs: hyperliquid.hypa1m.xyz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of hyperliquid.hypa1m.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| hypa1m.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://hyperliquid.hypa1m.xyz/mcp | HTTP error | 400 | |
| http (plaintext) | http://hyperliquid.hypa1m.xyz/mcp | HTTPS enforced | 301 | https://hyperliquid.hypa1m.xyz/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
candles_candles__coin__get ~95
Candles ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Coin ticker e.g. ETH |
| interval | string | — | Candle interval: 1m,5m,15m,1h,4h,1d |
| lookback | integer | — | Number of candles to return (max 5000) |
No output schema declared.
No examples provided.
favicon_favicon_ico_get ~49
Favicon Serve Pa1m logo as favicon for x402scan and browser tabs. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
funding_funding_get ~31
Funding ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
health_health_get ~30
Health ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
history_history__address__get ~45
History ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address 0x... |
No output schema declared.
No examples provided.
leaderboard_leaderboard_get ~51
Leaderboard ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| window | string | — | Time window: day, week, month, allTime |
No output schema declared.
No examples provided.
llms_txt_llms_txt_get ~49
Llms Txt ### Responses: **200**: Successful Response (Success Response) Content-Type: text/plain **Example Response:** ```json "string" ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
meta_meta_get ~30
Meta ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
open_orders_open_orders__address__get ~48
Open Orders ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address 0x... |
No output schema declared.
No examples provided.
openapi_json_openapi_json_get ~36
Openapi Json ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
orderbook_orderbook__coin__get ~49
Orderbook ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Coin ticker e.g. BTC |
No output schema declared.
No examples provided.
portfolio_portfolio__address__get ~46
Portfolio ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address 0x... |
No output schema declared.
No examples provided.
predicted_funding_predicted_funding_get ~37
Predicted Funding ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prices_prices_get ~30
Prices ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
root__get ~30
Root ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
top_top_get ~59
Top Free: mid prices for top 5 perps (BTC/ETH/SOL/BNB/XRP). 20 req/min per IP. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.