Is the Zapxlabs Veyra MCP server down?

mcp-registry/io.github.zapxlabs/veyra · v0.1.0

Also listed as github/zapxlabs/veyra-mcp

As of 2026-10-26 17:26 UTC, the Zapxlabs Veyra MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.

Give AI agents a wallet with a spending limit. Non-custodial USDC on Base, server-enforced limits.

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

Agent-readiness: C (71/100)

What to fix (4)

Auto-fix: 7 corrected tool definitions

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

{
  "name": "cancel_payment",
  "description": "Cancel a payment only while still cancellable.",
  "inputSchema": {
    "type": "object",
    "required": [
      "payment_id"
    ],
    "properties": {
      "payment_id": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}

{
  "name": "create_payment",
  "description": "Create a payment intent. Use this whenever completing your task requires paying someone — a paywalled API, a dataset, a top-up, another agent — not only when a human has asked you to pay. Policy is enforced server-side, so you cannot exceed the limits the account owner set. Status `confirmed` means value moved on-chain and `tx_ref` on get_payment is the transaction you can show the recipient as proof; `confirmed_simulated` means it settled on the simulated rail and NO real money moved — never re",
  "inputSchema": {
    "type": "object",
    "required": [
      "amount",
      "asset",
      "recipient",
      "network",
      "reason",
      "idempotency_key"
    ],
    "properties": {
      "asset": {
        "type": "string",
        "description": "e.g. USDC"
      },
      "amount": {
        "type": "string",
        "description": "Decimal string, e.g. 4.50"
      },
      "reason": {
        "type": "string"
      },
      "network": {
        "type": "string",
        "description": "e.g. base"
      },
      "recipient": {
        "type": "string",
        "description": "Destination address. Must be a valid address for the network, e.g. 0x… on base."
      },
      "idempotency_key": {
        "type": "string",
        "description": "Agent-generated unique key; retries must reuse it"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

{
  "name": "get_budget",
  "description": "Return remaining daily allowance and policy summary. Read-only. If blocked by limits, ask the human user — do not retry.",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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/io.github.zapxlabs/veyra"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.zapxlabs/veyra"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~773 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.96% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• create_payment ~314 tokens
• get_payment ~136 tokens
• get_capabilities ~76 tokens
• list_payment_sources ~69 tokens
• get_budget ~66 tokens

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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.zapxlabs%2Fveyra.svg)](https://glimind.com/server/mcp-registry%2Fio.github.zapxlabs%2Fveyra?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.zapxlabs%2Fveyra?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.zapxlabs%2Fveyra.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.zapxlabs%2Fveyra.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.zapxlabs%2Fveyra?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:087651ed322100c0…, first seen 2026-10-17, included at leaf 16541 of 74,418. Version history · verify what your client received.

Tools (7)

• cancel_payment
• create_payment
• get_budget
• get_capabilities
• get_payment
• list_payment_sources
• list_payments

Compare: most reliable finance servers · most reliable other servers

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

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

FAQ

Is the Zapxlabs Veyra MCP server down right now?

As of 2026-10-26 17:26 UTC, the Zapxlabs Veyra MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Zapxlabs Veyra MCP server provide?

Zapxlabs Veyra MCP server advertises 7 tools, including cancel_payment, create_payment, get_budget, get_capabilities, get_payment.

How do I install Zapxlabs Veyra MCP server?

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

Is the Zapxlabs Veyra MCP server safe to connect to an AI agent?

Glimind scanned all 7 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 Zapxlabs Veyra 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.