# MetaMesh-UGA

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

- name: dev.metamesh-uga/metamesh-uga
- version: 2.0.3
- connection class: R0 (autonomous)
- trust: 88/100
- quality: 73/100 (needs work)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/dev.metamesh-uga%2Fmetamesh-uga
- tools: https://api.protogrid.dev/v1/servers/dev.metamesh-uga%2Fmetamesh-uga/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 100
- liveness: 99
- freshness: 65
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-96% ~updated-103d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 73/100 (needs work)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2024-11-05; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: metamesh.context (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); metamesh.health (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); stripe.get_stripe_account_info (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 2,600 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 75 (weight 15)

- warn `stability.changes`: 6 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 15, about 2,600 tokens to load them all
- tool set hash: 2c5af6f80bfba25ae60a77d556716244
- tools last changed: 2026-10-20T15:54:14.726Z
- badge: [![protogrid quality](https://protogrid.dev/badge/dev.metamesh-uga/metamesh-uga.svg)](https://protogrid.dev/servers/dev.metamesh-uga/metamesh-uga)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-20 `stripe.stripe_analytics` changed (inputSchema)
- 2026-10-16 `stripe.stripe_api_write` changed (description, inputSchema)
  - before: 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 …
  - after: 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 see its parameters, unless the searc…
- 2026-10-16 `stripe.stripe_api_read` changed (description, inputSchema)
  - before: 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…
  - after: Read data from any Stripe API GET operation: 1. Use stripe_api_search to find the operation ID. 2. Use stripe_api_details to see its parameters, unless the search result already l…
- 2026-10-03 `stripe.stripe_analytics` changed (inputSchema)
- 2026-10-02 `stripe.stripe_analytics` changed (inputSchema)
- 2026-09-24 `stripe.stripe_api_write` changed (inputSchema)
- 2026-09-24 `stripe.stripe_api_read` changed (inputSchema)

Full history: https://api.protogrid.dev/v1/servers/dev.metamesh-uga%2Fmetamesh-uga/changes

## Remotes

- https://api.metamesh-uga.dev/mcp (streamable-http, auth none, reachable true, uptime30d 0.96460176)

## Packages

_none_

## Tools (15)

- `metamesh.context`: Compact snapshot of the MetaMesh gateway: active tool count, top categories, payment/billing status, last discovery. Best first call for context.
- `metamesh.discovery_status`: Control/observability: status of the registry discovery engine (active tools, last run, pages fetched).
- `metamesh.health`: Gateway health: database connectivity, payment configuration and feature flags.
- `metamesh.metrics`: Usage analytics: total tools, calls, success rate and recent error counts. Read-only.
- `metamesh.search_tools`: Search the catalog of 13k+ MCP tools by keyword. Returns concise matches (name, category, description). Use this instead of listing all tools.
- `metamesh.tool_info`: Detailed info for a specific catalog tool: description, category, trust/security score, state, source.
- `stripe.get_stripe_account_info`: This will get the account info for the logged in Stripe account.

- `stripe.search_stripe_documentation`: 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…
- `stripe.send_stripe_feedback`: Share feedback about Stripe's products.

Submit when the user gives product feedback or you observe something concrete that worked or failed. Do not report model behavior, the use…
- `stripe.stripe_analytics`: This tool is for analyzing Stripe Sigma and Metrics data (e.g. about revenue, charges, products, invoices, subscriptions, disputes, transactions, tax tables, payments etc) and run…
- `stripe.stripe_api_details`: 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…
- `stripe.stripe_api_read`: Read data from any Stripe API GET operation:
1. Use stripe_api_search to find the operation ID.
2. Use stripe_api_details to see its parameters, unless the search result already l…
- `stripe.stripe_api_search`: 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…
- `stripe.stripe_api_write`: 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 see its parameters, unless the searc…
- `stripe.stripe_implementation_planner`: Stripe integration planner. Use this tool to help users accept payments, sell products online, set up billing, set up a marketplace or platform, or build any Stripe integration. C…