MetaMesh-UGA
REMOTE · API.METAMESH-UGA.DEV · SCANNED AUG 3
Serverless edge control plane to discover, route and monetize 14,982+ MCP tools.
Available components
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. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1551 tokens (~103/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.metamesh-uga.dev
claude mcp add --transport http dev-metamesh-uga-metamesh-uga https://api.metamesh-uga.dev/mcp
[mcp_servers.dev-metamesh-uga-metamesh-uga] url = "https://api.metamesh-uga.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-metamesh-uga-metamesh-uga": {
"type": "remote",
"url": "https://api.metamesh-uga.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-metamesh-uga-metamesh-uga --url https://api.metamesh-uga.dev/mcp --transport streamable-http
mcp_servers:
dev-metamesh-uga-metamesh-uga:
url: "https://api.metamesh-uga.dev/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +1
- Schema quality: fail → pass ▲ functional
- “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” cosmetic
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://api.metamesh-uga.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=metamesh-uga.dev | CN=WE1,O=Google Trust Services,C=US | 16 Jun 2026 | 14 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 23fea5baf18121830e7cc3d9787e7b35 |
| SANs: metamesh-uga.dev, *.metamesh-uga.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of api.metamesh-uga.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| metamesh-uga.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.metamesh-uga.dev/mcp | Verified | 200 | |
| sse | https://api.metamesh-uga.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.metamesh-uga.dev/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
metamesh.context ~39
Compact snapshot of the MetaMesh gateway: active tool count, top categories, payment/billing status, last discovery. Best first call for context.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
metamesh.discovery_status ~32
Control/observability: status of the registry discovery engine (active tools, last run, pages fetched).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
metamesh.health ~22
Gateway health: database connectivity, payment configuration and feature flags.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
metamesh.metrics ~28
Usage analytics: total tools, calls, success rate and recent error counts. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
metamesh.search_tools ~80
Search the catalog of 13k+ MCP tools by keyword. Returns concise matches (name, category, description). Use this instead of listing all tools.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max results (default 10, max 50) |
| q | string | yes | Search query, e.g. "github", "database", "email" |
No output schema declared.
No examples provided.
metamesh.tool_info ~41
Detailed info for a specific catalog tool: description, category, trust/security score, state, source.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Exact tool name |
No output schema declared.
No examples provided.
stripe.create_refund ~239
This tool will refund a payment intent in Stripe.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The ID of the PaymentIntent to refund. |
| reason | string | — | The reason for the refund. |
No output schema declared.
No examples provided.
stripe.get_stripe_account_info ~25
This will get the account info for the logged in Stripe account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
stripe.search_stripe_documentation ~149
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…
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | — | The programming language to search for in the documentation. |
| question | string | yes | 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… |
No output schema declared.
No examples provided.
stripe.send_stripe_mcp_feedback ~145
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…
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | User persona, their broader goal, current task, and estimated technical proficiency. |
| quote | string | yes | User's exact message containing feedback. Max 1000 chars. |
| sentiment | string | yes | positive, negative, or neutral |
| source | string | yes | 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. |
No output schema declared.
No examples provided.
stripe.stripe_api_details ~75
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…
| Name | Type | Req | Description |
|---|---|---|---|
| stripe_api_operation_id | string | yes | The operation ID to get details for (e.g. 'PostCustomers', 'GetPaymentIntents') |
No output schema declared.
No examples provided.
stripe.stripe_api_read ~125
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…
| Name | Type | Req | Description |
|---|---|---|---|
| parameters | object | yes | 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 | yes | The operation ID to execute |
No output schema declared.
No examples provided.
stripe.stripe_api_search ~90
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…
| Name | Type | Req | Description |
|---|---|---|---|
| intent | string | yes | The intent of the operation |
| limit | integer | — | Maximum number of results to return |
| resource | string | yes | Target resource the operation is looking to manipulate |
No output schema declared.
No examples provided.
stripe.stripe_api_write ~291
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 …
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The operation ID to execute |
No output schema declared.
No examples provided.
stripe.stripe_implementation_planner ~170
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…
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | For new guides: describe the use case or business requirements. For existing guides: provide the latest user response or the full accepted transcript. |
No output schema declared.
No examples provided.