Skip to content

$AI on HyperEVM MCP server

ai.thetickeris/agent-railthetickeris.aistreamable-httpv1.0.0Scanned

Quote and build unsigned buy/sell transactions for $AI on its HyperEVM bonding curve. No keys held.

5 tools: 4 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 4 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the $AI on HyperEVM MCP server can do

The $AI on HyperEVM MCP server is published by thetickeris.ai, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: ai_quote_buy, ai_quote_sell, ai_build_buy_tx and ai_build_sell_tx), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 30, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 4Claude Code: ask
  • ai_build_buy_txBuild an unsigned buy transaction against the AiCurve contract.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Build Buy Transaction
  • ai_build_sell_txBuild the unsigned transaction(s) to sell $AI: an approve first if allowance is insufficient, then the sell.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Build Sell Transaction
  • ai_quote_buyRecommended first call for a new agent: quote how much $AI a given amount of HYPE buys right now, before slippage.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Quote Buy
  • ai_quote_sellQuote how much HYPE a given amount of $AI returns right now, net of the on-chain sell fee.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Quote Sell
Only reads 1Show 1 read-only tool
  • ai_marketRead-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 …No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Market Snapshot

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 18:28 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: thetickeris.ai does not resolve.

Posture changes

  1. Nov 6, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http agent-rail https://thetickeris.ai/mcp
claude mcp add --transport http agent-rail https://thetickeris.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agent-rail__ai_market"
    ],
    "ask": [
      "mcp__agent-rail__ai_quote_buy",
      "mcp__agent-rail__ai_quote_sell",
      "mcp__agent-rail__ai_build_buy_tx",
      "mcp__agent-rail__ai_build_sell_tx"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agent-rail. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.thetickeris/agent-rail/verify?hash=a3545a5efbe995ddc23d00d9b860a7ef81be88893b1bfba0ca0bfb6e3692f8dc" | jq -e '.changed == false'

Pinned hash a3545a5efbe9, from Oct 30, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.thetickeris/agent-rail/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.thetickeris/agent-rail
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.thetickeris/agent-rail.svg)](https://radar.anlyon.com/servers/ai.thetickeris/agent-rail)

Source: MCP Registry. Synced Oct 21, 2026, 17:43 UTC.

$AI on HyperEVM MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the $AI on HyperEVM MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the $AI on HyperEVM MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the $AI on HyperEVM MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the $AI on HyperEVM MCP server have?

5 tools: 4 write, 1 read. ai_quote_buy, ai_quote_sell, ai_build_buy_tx, ai_build_sell_tx and ai_market.

Does the $AI on HyperEVM MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the $AI on HyperEVM MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the $AI on HyperEVM MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 30, 2026.