# MetaMesh-UGA (remote · api.metamesh-uga.dev)

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

- Trust score: 57/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.metamesh-uga.dev`: 57/100 (this document), [markdown](https://verifymcp.io/servers/dev-metamesh-uga-metamesh-uga/api.md), [page](https://verifymcp.io/servers/dev-metamesh-uga-metamesh-uga/api)

## Channel facts

- Endpoint: `https://api.metamesh-uga.dev/mcp`
- Transports: `streamable-http, sse`
- Auth: `none`
- Version: `2.0.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1551 tokens (~103/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.dev-metamesh-uga-metamesh-uga]
url = "https://api.metamesh-uga.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-metamesh-uga-metamesh-uga": {
      "type": "remote",
      "url": "https://api.metamesh-uga.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-metamesh-uga-metamesh-uga --url https://api.metamesh-uga.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-metamesh-uga-metamesh-uga:
    url: "https://api.metamesh-uga.dev/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 55, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 56, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 55, +1)

- [functional improvement] Schema quality: fail → pass
- [cosmetic] “stripe.stripe_api_write” reworded the description of “stripe_api_operation_id”
- [cosmetic] “stripe.stripe_api_read” reworded the description of “parameters”
- [cosmetic] “stripe.stripe_api_read” reworded the description of “stripe_api_operation_id”
- [cosmetic] “stripe.stripe_api_write” reworded the description of “parameters”

### 2026-07-27 (score 54, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 54)

First indexed and scored.

## MCP tools (15)

### `metamesh.context` (~39 tokens)

Compact snapshot of the MetaMesh gateway: active tool count, top categories, payment/billing status, last discovery. Best first call for context.

### `metamesh.search_tools` (~80 tokens)

Search the catalog of 13k+ MCP tools by keyword. Returns concise matches (name, category, description). Use this instead of listing all tools.

Input parameters:

- `limit` (number): Max results (default 10, max 50)
- `q` (string, required): Search query, e.g. "github", "database", "email"

### `metamesh.tool_info` (~41 tokens)

Detailed info for a specific catalog tool: description, category, trust/security score, state, source.

Input parameters:

- `name` (string, required): Exact tool name

### `metamesh.metrics` (~28 tokens)

Usage analytics: total tools, calls, success rate and recent error counts. Read-only.

### `metamesh.discovery_status` (~32 tokens)

Control/observability: status of the registry discovery engine (active tools, last run, pages fetched).

### `metamesh.health` (~22 tokens)

Gateway health: database connectivity, payment configuration and feature flags.

### `stripe.search_stripe_documentation` (~149 tokens)

Search the Stripe documentation for the given question and language.

It takes two arguments:
\- question (str): The user question to search an answer for in the Stripe documentati…

Input parameters:

- `language` (string): The programming language to search for in the documentation.
- `question` (string, required): The user question about integrating with Stripe will be used to search the documentation.
- `search_only_api_ref` (boolean): When set to true, search only in the Stripe API reference documentation instead of the full documentation set. Use true when users need specific API implementation details, code examples, or paramete…

### `stripe.get_stripe_account_info` (~25 tokens)

This will get the account info for the logged in Stripe account.

### `stripe.create_refund` (~239 tokens)

This tool will refund a payment intent in Stripe.

Input parameters:

- `amount` (integer): The amount to refund in currency minor units, e.g. cents for USD and yen for JPY.
- `human_confirmation` (object): This tool might require human confirmation. To run it, first invoke it with the desired parameters, ignoring the `approval_token` parameter. If it requires human confirmation, the response will inclu…
- `payment_intent` (string, required): The ID of the PaymentIntent to refund.
- `reason` (string): The reason for the refund.

### `stripe.stripe_implementation_planner` (~170 tokens)

Stripe payment integration planner. Use this tool to help users accept payments, sell products online, set up billing, or build any Stripe integration. Call this BEFORE writing co…

Input parameters:

- `accept` (boolean): Set to true when returning the completed decision tree with your chosen options to receive the finalized integration guide.
- `guide_id` (string): ONLY pass a guide_id that was returned by a previous call to this tool in this conversation. Never fabricate, guess, or reuse guide_ids from other sessions. If you do not have a guide_id from a prior…
- `message` (string, required): For new guides: describe the use case or business requirements. For existing guides: provide the latest user response or the full accepted transcript.

### `stripe.send_stripe_mcp_feedback` (~145 tokens)

Submit feedback from user or agent about Stripe's MCP server tools.

Valid: "the search tool returned irrelevant results", "I wish there was a tool for X"
Invalid: Stripe API comp…

Input parameters:

- `context` (string, required): User persona, their broader goal, current task, and estimated technical proficiency.
- `quote` (string, required): User's exact message containing feedback. Max 1000 chars.
- `sentiment` (string, required): positive, negative, or neutral
- `source` (string, required): user or agent
- `tool_name` (string): The name of the tool the user is giving feedback about. Include if confident that feedback is about a specific tool.

### `stripe.stripe_api_search` (~90 tokens)

Search for Stripe API operations by providing an intent and a resource to operate on.

For the resource, use a specific, descriptive phrase (e.g. "issuing card transactions", "pay…

Input parameters:

- `intent` (string, required): The intent of the operation
- `limit` (integer): Maximum number of results to return
- `resource` (string, required): Target resource the operation is looking to manipulate

### `stripe.stripe_api_details` (~75 tokens)

Get detailed parameter information for a specific Stripe API operation.
Provide the stripe_api_operation_id from stripe_api_search results to see all path, query, and body paramet…

Input parameters:

- `stripe_api_operation_id` (string, required): The operation ID to get details for (e.g. 'PostCustomers', 'GetPaymentIntents')

### `stripe.stripe_api_read` (~125 tokens)

Read data from any Stripe API GET operation:
1\. Use stripe_api_search to find the operation ID.
2\. Use stripe_api_details to understand its parameters (required for operations wit…

Input parameters:

- `parameters` (object, required): Parameters for the API call. Include path parameters (e.g. 'customer' for /v1/customers/{customer}), query parameters, and body parameters. Array fields (e.g. line_items) must be passed as a JSON arr…
- `stripe_api_operation_id` (string, required): The operation ID to execute

### `stripe.stripe_api_write` (~291 tokens)

Write data via any Stripe API POST/PATCH/PUT/DELETE operation:
1\. Use stripe_api_search to find the operation ID.
2\. Use stripe_api_details to understand its parameters (required …

Input parameters:

- `human_confirmation` (object): This tool might require human confirmation. To run it, first invoke it with the desired parameters, ignoring the `approval_token` parameter. If it requires human confirmation, the response will inclu…
- `parameters` (object, required): Parameters for the API call. Include path parameters (e.g. 'customer' for /v1/customers/{customer}), query parameters, and body parameters. Array fields (e.g. line_items) must be passed as a JSON arr…
- `stripe_api_operation_id` (string, required): The operation ID to execute

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-metamesh-uga-metamesh-uga/api#diagnostics

## Score history

- 2026-08-03: 57
- 2026-08-02: 56
- 2026-08-01: 56
- 2026-07-31: 55
- 2026-07-30: 56
- 2026-07-29: 56
- 2026-07-28: 55
- 2026-07-27: 54
- 2026-07-26: 54

## Links

- Remote endpoint: https://api.metamesh-uga.dev/mcp
- Repository: https://github.com/SiouxTXT/metamesh-uga
- Website: https://metamesh-uga.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-metamesh-uga-metamesh-uga/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-metamesh-uga-metamesh-uga/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dev-metamesh-uga-metamesh-uga/api