Back to Browse

Akari X402 MCP Server

by Edvyno
Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Akari x402 tools: funding-edge + token-safety previews, service list, paid 402 call helper.

About

Akari x402 tools: funding-edge + token-safety previews, service list, paid 402 call helper.

Remote endpoints: streamable-http: https://03s9tr085tfe5agke0tpqng34o.ingress.quanglong.org/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

35 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

env_vars

Applies to the server that hosts this plugin, not to your machine.

file_system

Applies to the server that hosts this plugin, not to your machine.

HTTP Network Access

Connects to external APIs or services over the internet.

Shell Command Execution

Runs commands on the server that hosts it, not on your machine.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-edvyno-akari-x402": {
      "url": "https://03s9tr085tfe5agke0tpqng34o.ingress.quanglong.org/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

akari-x402

An MCP server for Akari Agent Services — machine-payable crypto intelligence sold over x402 (HTTP 402, USDC on Base). Install it and your agent gets three free tools plus a paid-call helper that understands the 402 handshake.

No account, no API key, no signup. Prices are per call, settled in USDC.

# run it (stdio). Host config: { "command": "npx", "args": ["-y", "akari-x402"] }
npx -y akari-x402

Status of the npm name (honest): the package is published to the official MCP registry as io.github.edvyno/akari-x402 (remote: the stable origin's /mcp), but the npm package is not published yet — this desk has no npm credentials and npm 2FA is not bypassed. Until it is, the install line that has actually been executed end to end is the git spec:

npx -y github:edvyno/akari-x402

Tools

toolpricewhat it does
list_servicesfreeReads /.well-known/agent-services.json: every paid route, its price, the payment rail (network, payTo, flow), the cheapest entry point and the free surfaces.
funding_edge_previewfree3 real rows of the perp funding ranking built on realized funding (fundingHistory summed over 24h, net of round-trip cost) on Hyperliquid perps + the HIP-3 dexes, plus _meta.measured recomputed on every call.
token_safety_previewfreeLiquidity, pairs, 24h volume, concentration flags and a verdict for any Base token — before an agent pays or routes into it.
paid_call$0.03–$49Calls any x402 route. No key: returns the decoded 402 challenge (price, network, asset, payTo, EIP-712 domain) and spends nothing. With a key: signs EIP-3009 and returns the paid payload + settlement receipt.

Paying

The key is read only from the environment. It is never a tool argument and never logged.

export AKARI_PRIVATE_KEY=0x…      # a Base wallet holding USDC (no ETH needed: the facilitator pays gas)
export AKARI_MAX_PRICE_USD=1.00   # hard per-call cap, enforced before signing (default $1.00)

Then call paid_call with confirm_pay: true. Flow per call:

  1. GET the route → 402 with a base64 PAYMENT-REQUIRED header.
  2. Sign EIP-3009 TransferWithAuthorization over the USDC EIP-712 domain (chain 8453).
  3. Re-GET with X-PAYMENT: <base64 payload> → 200 + PAYMENT-RESPONSE receipt.

Nothing is broadcast locally: the authorization is off-chain and the facilitator settles it. Every call is bounded by AKARI_MAX_PRICE_USD, so an agent cannot spend more than you allow.

Point it at another origin

AKARI_ORIGIN=https://your-mirror.example npx -y akari-x402   # or AKARI_ORIGIN_FILE=/path/to/url.txt

Default origin: https://03s9tr085tfe5agke0tpqng34o.ingress.quanglong.org (the desk's stable Akash ingress — a mirror that relays the origin verbatim, including the 402 challenge bytes).

Host config examples

Claude Desktop / Cursor / Cline (mcpServers):

{
  "mcpServers": {
    "akari-x402": {
      "command": "npx",
      "args": ["-y", "akari-x402"],
      "env": { "AKARI_MAX_PRICE_USD": "1.00" }
    }
  }
}

Remote alternative (no install, JSON-RPC over HTTP): POST https://03s9tr085tfe5agke0tpqng34o.ingress.quanglong.org/mcp — the same desk also runs a remote MCP endpoint, listed in the official MCP registry as io.github.edvyno/akari-crypto-intel.

What this package will not do

  • It will not invent data. Every row comes from the live scanner that produces the paid product; if the origin is down the tool returns the HTTP status, not a plausible-shaped fake.
  • It will not spend without confirm_pay: true and a key you exported yourself.
  • It will not ship a retired hostname as its default. If the origin moves, change AKARI_ORIGIN.

Test it yourself

node test/mcp_stdio_test.mjs funding_edge_preview   # initialize + tools/list + one live tool call

Builder program

40 % of every settled sale referred by ?ref=0xYourWallet goes to that wallet — fork this server, add your ref, ship it. Terms: /x402/affiliate. Program page: https://edvyno.github.io/akari-proof/builder.html

MIT.

Reviews

No reviews yet

Be the first to review this server!