Home / MCP registry index / xyz.getava/ava

Ava

xyz.getava/ava in the official MCP registry. Endpoint https://api.getava.xyz/mcp. Source: github.com/kamalbuilds/ava-4.0.

The registry describes it as: Coding agents run multi-leg cross-chain DeFi. Legs re-derived from your sentence before signing.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http ava https://api.getava.xyz/mcp

{
  "mcpServers": {
    "ava": {
      "url": "https://api.getava.xyz/mcp"
    }
  }
}

code --add-mcp '{"name":"ava","type":"http","url":"https://api.getava.xyz/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

ava_copilot_turn ava_approve_execute ava_lend_execute ava_portfolio ava_session ava_create_agent ava_provision_wallet ava_preview_tx ava_plan_workflow ava_plan_standing ava_create_mandate ava_list_mandates ava_eval_mandate ava_agent_record ava_get_receipt

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 3aeb32578952ce2b. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/xyz-getava-ava/badge.svg)](https://lazaretto.dev/mcp-registry/xyz-getava-ava)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers