$AI on HyperEVM
REMOTE · THETICKERIS.AI · SCANNED OCT 5
Quote and build unsigned buy/sell transactions for $AI on its HyperEVM bonding curve. No keys held.
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 → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 899 tokens (~179/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the $AI on HyperEVM MCP server?
$AI on HyperEVM is a hosted endpoint at https://thetickeris.ai/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.
remote · thetickeris.ai
claude mcp add --transport http ai-thetickeris-agent-rail 'https://thetickeris.ai/mcp'
{
"mcpServers": {
"ai-thetickeris-agent-rail": {
"url": "https://thetickeris.ai/mcp"
}
}
} {
"servers": {
"ai-thetickeris-agent-rail": {
"type": "http",
"url": "https://thetickeris.ai/mcp"
}
}
} [mcp_servers.ai-thetickeris-agent-rail] url = "https://thetickeris.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-thetickeris-agent-rail": {
"type": "remote",
"url": "https://thetickeris.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-thetickeris-agent-rail --url 'https://thetickeris.ai/mcp' --transport streamable-http
mcp_servers:
ai-thetickeris-agent-rail:
url: "https://thetickeris.ai/mcp" {
"McpServers": {
"ai-thetickeris-agent-rail": {
"Transport": "http",
"Url": "https://thetickeris.ai/mcp"
}
}
} assistant mcp add ai-thetickeris-agent-rail -t streamable-http -u 'https://thetickeris.ai/mcp'
{
"mcpServers": {
"ai-thetickeris-agent-rail": {
"type": "http",
"url": "https://thetickeris.ai/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.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +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.
- 29 Sept 26 +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.
- 28 Sept 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +8
- Authorization: unverified → partial ▲ security
- Stability: unverified → 0.03 ▲ functional
- Tool “ai_build_buy_tx” now declares an output schema ▲ functional
- Tool “ai_build_sell_tx” now declares an output schema ▲ functional
- Tool “ai_market” now declares an output schema ▲ functional
- Tool “ai_quote_buy” now declares an output schema ▲ functional
- Tool “ai_quote_sell” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Tool “ai_build_buy_tx” changed its title: Build Buy Transaction cosmetic
- Tool “ai_build_sell_tx” changed its title: Build Sell Transaction cosmetic
- Tool “ai_market” changed its title: Market Snapshot cosmetic
- Tool “ai_quote_buy” changed its title: Quote Buy cosmetic
- Tool “ai_quote_sell” changed its title: Quote Sell cosmetic
- 26 Sept 26 67
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 5 Oct 2026 · Probed https://thetickeris.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=thetickeris.ai | CN=YE1,O=Let's Encrypt,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5612f59e70dd69401710ce3a77f8c152af2 |
| SANs: thetickeris.ai, www.thetickeris.ai | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of thetickeris.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| thetickeris.ai. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; script-src 'self'; style-src 'self'; font-src 'self'; img-src 'self' data:; connect-src 'self' https://rpc.hyperliquid.xyz https://api.hyperliquid.xyz wss://thetickeris.ai; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://thetickeris.ai/mcp | Verified | 200 | |
| http (plaintext) | http://thetickeris.ai/mcp | HTTPS enforced | 301 | https://thetickeris.ai/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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ai_build_buy_tx Build Buy Transaction ~159
Build an unsigned buy transaction against the AiCurve contract. Returns calldata only; the caller signs and sends it. Includes an estimated gas limit when `from` is given. The minimum $AI out is the live quote minus slippage_bps, so a price move past that tolerance makes the tx revert instead of filling worse. Use ai_quote_buy to preview without building; use ai_build_sell_tx to sell.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | 0x sender address; when given the tx includes a gas estimate |
| hype | string | yes | HYPE amount to spend, decimal string, max 10000 |
| slippage_bps | integer | – | Slippage tolerance in basis points, 0-5000, default 200 |
| Name | Type | Req | Description |
|---|---|---|---|
| disclosure | string | yes | – |
| quote | object | yes | – |
| tx | object | yes | – |
No examples provided.
ai_build_sell_tx Build Sell Transaction ~166
Build the unsigned transaction(s) to sell $AI: an approve first if allowance is insufficient, then the sell. Returns calldata only; the caller signs and sends, in order. When an approve is included, send the sell after the approve is mined and estimate its gas then. The minimum HYPE out is the net quote minus slippage_bps. Use ai_quote_sell to preview without building; use ai_build_buy_tx to buy.
| Name | Type | Req | Description |
|---|---|---|---|
| ai | string | yes | $AI amount to sell, decimal string, max 1000000000 |
| from | string | yes | 0x seller address, required to check allowance and estimate gas |
| slippage_bps | integer | – | Slippage tolerance in basis points, 0-5000, default 200 |
| Name | Type | Req | Description |
|---|---|---|---|
| disclosure | string | yes | – |
| quote | object | yes | – |
| steps | array | yes | – |
No examples provided.
ai_market Market Snapshot ~82
Read-only snapshot of the $AI/HYPE AiCurve: price, sold, retired, circulating, reserve, supply, sell fee (read live from chain), contracts, chain id, rpc, and the fee/no-guarantee disclosure. Takes no amount; for a price on a specific amount use ai_quote_buy (the recommended first call) or ai_quote_sell.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | yes | – |
| circulating | string | – | – |
| contracts | object | yes | – |
| disclosure | string | yes | – |
| priceHype | string | yes | – |
| priceHypeWei | string | – | – |
| reserveHype | string | – | – |
| retired | string | – | – |
| rpc | string | yes | – |
| sellFeeBps | integer | yes | – |
| sold | string | yes | – |
| supply | string | yes | – |
No examples provided.
ai_quote_buy Quote Buy ~95
Recommended first call for a new agent: quote how much $AI a given amount of HYPE buys right now, before slippage. Read-only, no wallet needed, no key, no transaction. To buy it for real, call ai_build_buy_tx next with the same hype amount.
| Name | Type | Req | Description |
|---|---|---|---|
| hype | string | yes | HYPE amount as a decimal string, e.g. "1.5" (max 10000) |
| Name | Type | Req | Description |
|---|---|---|---|
| disclosure | string | yes | – |
| tokensOut | string | yes | – |
No examples provided.
ai_quote_sell Quote Sell ~89
Quote how much HYPE a given amount of $AI returns right now, net of the on-chain sell fee. Use it to preview a sell; it returns no transaction. To get the calldata, call ai_build_sell_tx with the same ai amount.
| Name | Type | Req | Description |
|---|---|---|---|
| ai | string | yes | $AI amount as a decimal string, e.g. "1000" (max 1000000000) |
| Name | Type | Req | Description |
|---|---|---|---|
| disclosure | string | yes | – |
| hypeOut | string | yes | – |
No examples provided.
What is the $AI on HyperEVM MCP server?
$AI on HyperEVM is an MCP server listed in the public MCP registry as ai.thetickeris/agent-rail. Quote and build unsigned buy/sell transactions for $AI on its HyperEVM bonding curve. No keys held. This page covers its hosted endpoint (https://thetickeris.ai/mcp).
Is the $AI on HyperEVM MCP server safe to use?
$AI on HyperEVM scores 77 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 $AI on HyperEVM MCP server expose?
$AI on HyperEVM exposes 5 tools: ai_market, ai_quote_buy, ai_quote_sell, ai_build_buy_tx, ai_build_sell_tx. Their descriptions and schemas cost roughly 591 tokens of context every time the server is loaded.
Does the $AI on HyperEVM MCP server require authentication?
No. We connected to $AI on HyperEVM without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the $AI on HyperEVM MCP server still maintained?
$AI on HyperEVM is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.