Is the Metamesh Uga MCP server down?

mcp-registry/dev.metamesh-uga/metamesh-uga · v1.0.0

grade A

healthy

Last checked 2026-10-18 05:18 UTC · handshake 168ms

As of 2026-10-18 05:18 UTC, the Metamesh Uga MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)

100%

checks observed

3,642

outages (90d)

tools

Serverless edge control plane to discover, route and monetize 14,982+ MCP tools.

Install Metamesh Uga MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http metamesh-uga-mcp-server https://api.metamesh-uga.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "metamesh-uga-mcp-server": {
      "type": "http",
      "url": "https://api.metamesh-uga.dev/mcp"
    }
  }
}

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

Agent-readiness: C (71/100)

grade C

C (71/100): 0 error(s), 5 warning(s) across 15 tool(s); ~3,062 tokens of tool definitions.

Scores higher than 7% of 15,350 MCP servers Glimind has audited.

Its tool list costs an agent ~3,062 tokens per session — more than 55% of servers.

71 → 71 since 2026-10-17

no tool-poisoning patterns

Schemas100

Descriptions100

Safety hints9

Token cost100

Client compatibility20

Protocol100

Reliability85

Stability62

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: metamesh.context, metamesh.discovery_status, metamesh.health, metamesh.metrics, metamesh.search_tools and 10 more

15 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).

Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →

Tools: metamesh.context, metamesh.discovery_status, metamesh.health, metamesh.metrics, metamesh.search_tools and 10 more

2 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: stripe.send_stripe_feedback, stripe.stripe_api_write

Handshake + tools/list takes ~1,893 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.

In the last 30 days: 1 tool(s) removed and 7 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

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: 15 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.metamesh-uga%2Fmetamesh-uga/fixes

metamesh.context 1 change

Renamed "metamesh.context" → "metamesh_context" (letters, digits, _ and - only; max 64). Keep the old name as an alias for a release if clients already call it. (verify)

{
  "name": "metamesh_context",
  "description": "Compact snapshot of the MetaMesh gateway: active tool count, top categories, payment/billing status, last discovery. Best first call for context.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  }
}

metamesh.discovery_status 2 changes

Renamed "metamesh.discovery_status" → "metamesh_discovery_status" (letters, digits, _ and - only; max 64). Keep the old name as an alias for a release if clients already call it. (verify)
Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "metamesh_discovery_status",
  "description": "Control/observability: status of the registry discovery engine (active tools, last run, pages fetched).",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

metamesh.health 2 changes

Renamed "metamesh.health" → "metamesh_health" (letters, digits, _ and - only; max 64). Keep the old name as an alias for a release if clients already call it. (verify)
Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "metamesh_health",
  "description": "Gateway health: database connectivity, payment configuration and feature flags.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "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/dev.metamesh-uga/metamesh-uga"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.metamesh-uga/metamesh-uga"}) over MCP.

Passed

Every tool has a well-formed, typed input schema.
Every tool and parameter is described.
No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
Compact tool list (~3,062 tokens).
Speaks MCP 2025-06-18.
100.00% uptime over 30 days.

Largest tool definitions

stripe.stripe_analytics ~632 tokens
stripe.stripe_api_write ~496 tokens
stripe.send_stripe_feedback ~347 tokens
stripe.stripe_implementation_planner ~304 tokens
stripe.search_stripe_documentation ~284 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:

Markdown

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.metamesh-uga%2Fmetamesh-uga.svg)](https://glimind.com/server/mcp-registry%2Fdev.metamesh-uga%2Fmetamesh-uga?ref=badge)

HTML

<a href="https://glimind.com/server/mcp-registry%2Fdev.metamesh-uga%2Fmetamesh-uga?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.metamesh-uga%2Fmetamesh-uga.svg" alt="MCP agent-readiness"></a>

reStructuredText

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.metamesh-uga%2Fmetamesh-uga.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.metamesh-uga%2Fmetamesh-uga?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:89ea393dd42643e6…, first seen 2026-10-17, included at leaf 10858 of 20,451. Version history · verify what your client received.

Tools (15)

Compare: most reliable knowledge servers · most reliable devops servers · most reliable search servers · most reliable finance servers · most reliable communication 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 Metamesh Uga MCP server down right now?

As of 2026-10-18 05:18 UTC, the Metamesh Uga MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Metamesh Uga MCP server provide?

Metamesh Uga MCP server advertises 15 tools, including metamesh.context, metamesh.discovery_status, metamesh.health, metamesh.metrics, metamesh.search_tools.

How do I install Metamesh Uga MCP server?

Point your MCP client at this streamable-http endpoint: https://api.metamesh-uga.dev/mcp

Is the Metamesh Uga 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 Metamesh Uga 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.