Is the Getava Ava MCP server down?

mcp-registry/xyz.getava/ava · v0.5.0

healthy
Last checked 2026-10-18 23:42 UTC · handshake 1s

As of 2026-10-18 23:42 UTC, the Getava Ava MCP server is up with a Glimind reliability score of 82/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 9 minutes.

uptime (30d checks)
99.9%
checks observed
3,692
outages (90d)
3
tools
15

Coding agents run multi-leg cross-chain DeFi. Legs re-derived from your sentence before signing.

Install Getava Ava MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "getava-ava-mcp-server": {
      "type": "http",
      "url": "https://api.getava.xyz/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (64/100)

D (64/100): 0 error(s), 5 warning(s) across 15 tool(s); ~3,390 tokens of tool definitions.
Scores higher than 1% of 15,341 MCP servers Glimind has audited.
Its tool list costs an agent ~3,390 tokens per session — more than 55% of servers.
64 → 64 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions39
Safety hints0
Token cost100
Client compatibility70
Protocol40
Reliability85
Stability100

What to fix (6)

15 of 15 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: ava_agent_record, ava_approve_execute, ava_copilot_turn, ava_create_agent, ava_create_mandate and 10 more

28 parameter(s) across 11 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: ava_copilot_turn, ava_create_agent, ava_create_mandate, ava_eval_mandate, ava_lend_execute and 6 more

4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: ava_approve_execute, ava_create_agent, ava_create_mandate, ava_lend_execute

Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

Handshake + tools/list takes ~2,742 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 7 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 11 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fxyz.getava%2Fava/fixes

ava_approve_execute 1 change
{
  "name": "ava_approve_execute",
  "description": "Human-in-the-loop approve: the one call that actually settles a plan from ava_copilot_turn. It is gated by the bound mandate's status and constraints and by server-side policy limits, and it CAN REFUSE (e.g. mandate paused/cancelled, a policy violation, a stale preview hash); a refusal means no funds moved and no success receipt was written, only a refusal record. Testnet mode settles against simulated balances and returns a receipt + before/after balances, never a real chain. Mainnet mode signs",
  "inputSchema": {
    "type": "object",
    "required": [
      "executionId",
      "userId",
      "portal"
    ],
    "properties": {
      "mode": {
        "enum": [
          "paper",
          "live"
        ],
        "type": "string",
        "description": "Default testnet. Live is fail-closed without a submit path."
      },
      "portal": {
        "type": "string",
        "description": "Portal slug matching the pending plan (e.g. sui)"
      },
      "userId": {
        "type": "string",
        "description": "Same userId used on ava_copilot_turn / portfolio"
      },
      "executionId": {
        "type": "string",
        "description": "executionId from actions[].type === approve_execute on the prior copilot turn"
      },
      "previewHash": {
        "type": "string",
        "description": "previewHash from ava_preview_tx. Binds the signature to the artifact the human reviewed; a stale hash fails before signing."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
ava_create_agent 1 change
{
  "name": "ava_create_agent",
  "description": "Register an agent instance under userId, before it has a wallet or a mandate. Mode A (multi-agent): agentId=byo-external + label (e.g. claude-workspace, cursor-arb) for a coding agent that already exists elsewhere. Mode B (hosted): agentId=defi-lend|defi-swap|defi-perp|portfolio hires an Ava-run agent. One userId may own many agent instances; this call alone never touches funds.",
  "inputSchema": {
    "type": "object",
    "required": [
      "userId",
      "portal",
      "agentId"
    ],
    "properties": {
      "label": {
        "type": "string",
        "description": "Optional label to distinguish agents under one human (e.g. claude-workspace, cursor-home, openclaw-night)."
      },
      "portal": {
        "type": "string"
      },
      "userId": {
        "type": "string"
      },
      "agentId": {
        "type": "string",
        "description": "Catalog id e.g. byo-external, defi-lend, defi-swap, defi-perp, portfolio"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
ava_create_mandate 1 change
{
  "name": "ava_create_mandate",
  "description": "Create a capital mandate: the objective, capital and constraints an agent is allowed to act under, optionally scoped to an agentInstanceId. Example: \"Earn on 500 USDC on Base, max 5% drawdown\". Or pass structured capital {asset,amount,chain}. Creating a mandate moves no money by itself and is not yet signed by an external wallet: it is Ava's own record of what was asked for, not a user-authorised instruction a stranger can rely on. Every later ava_approve_execute run under this mandate is gated ",
  "inputSchema": {
    "type": "object",
    "required": [
      "portal"
    ],
    "properties": {
      "name": {
        "type": "string"
      },
      "portal": {
        "type": "string"
      },
      "userId": {
        "type": "string"
      },
      "capital": {
        "type": "object"
      },
      "message": {
        "type": "string"
      },
      "objective": {
        "type": "string"
      },
      "conditions": {
        "type": "array"
      },
      "constraints": {
        "type": "object"
      },
      "agentInstanceId": {
        "type": "string",
        "description": "Optional: bind mandate to one agent under the user (BYO or hosted)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/xyz.getava/ava"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/xyz.getava/ava"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.getava%2Fava.svg)](https://glimind.com/server/mcp-registry%2Fxyz.getava%2Fava?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fxyz.getava%2Fava?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.getava%2Fava.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.getava%2Fava.svg
   :target: https://glimind.com/server/mcp-registry%2Fxyz.getava%2Fava?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3c6e22d56d757153…, first seen 2026-10-17, included at leaf 11606 of 23,854. Version history · verify what your client received.

Tools (15)

Compare: most reliable knowledge servers · most reliable finance servers · most reliable ai servers · most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Getava Ava MCP server down right now?

As of 2026-10-18 23:42 UTC, the Getava Ava MCP server is up with a Glimind reliability score of 82/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 9 minutes.

How many tools does Getava Ava MCP server provide?

Getava Ava MCP server advertises 15 tools, including ava_agent_record, ava_approve_execute, ava_copilot_turn, ava_create_agent, ava_create_mandate.

How do I install Getava Ava MCP server?

Point your MCP client at this streamable-http endpoint: https://api.getava.xyz/mcp

Is the Getava Ava MCP server safe to connect to an AI agent?

Glimind scanned all 15 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Getava Ava MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve