Skip to content

ari-mcp v0.2.0 · npm + PyPI

Latest

Choose a tag to compare

@Antmanbuilds Antmanbuilds released this 26 May 03:36

ari-mcp v0.2.0

First multi-registry release of the ARI MCP server. Same 20 tools, byte-identical wire semantics across both runtimes (pinned by cross-language fixture tests).

Install

Runtime Command
Node.js / npm npx -y ari-mcp@0.2.0 install
Python / PyPI pipx install ari-mcp-server==0.2.0 && ari-mcp install

Note on the PyPI name. The PyPI distribution is published as ari-mcp-server because PyPI rejected the short name ari-mcp as too similar to an existing project. The installed CLI is still ari-mcp — so MCP host config blocks (Claude Desktop, Cursor, Continue, Windsurf, Zed, ChatGPT desktop, Gemini CLI) are identical between the two runtimes.

Registry links

What's in v0.2.0

The full 20-tool surface for Agentic Rate Indicators:

  • Pricing & verdictsfair_price, verdict, rate_card, bands, compare_services
  • Discovery & searchlist_services, search_services, service_detail, observations, recent_receipts
  • Leaderboards & trendsleaderboard, movers, volatility, coverage_summary
  • Receipts & verificationverify_receipt, receipt_detail, fetch_jwks, pinned_keys
  • Network metadatanetwork_status, version

Every JSON response is signed with an Ed25519 key (current key_id = ari-aedbd75d43c8) and stamped with a citable receipt id, so agents can refuse to overpay and humans can re-verify any decision weeks later.

End-to-end smoke (run yourself)

# npm path
npx -y ari-mcp@0.2.0 verify-receipt --service=0x402-ai-x402

# PyPI path
pipx install ari-mcp-server==0.2.0
ari-mcp verify-receipt --service=0x402-ai-x402

Both return PASS · receipt verified end-to-end against https://agentrateindicators.com with a real signed receipt.

Note on the source tree

The tag for this release points to the repository's main branch as it existed at release time. The authoritative source-of-truth for what is installed is the published tarball on each registry (both signed and immutable). The development history that produced these tarballs lives in the Replit workspace and will be synced to GitHub main in a follow-up.