MetaMesh-UGA MCP server
dev.metamesh-uga/metamesh-ugametamesh-uga.devstreamable-httpv2.0.3Scanned
Serverless edge control plane to discover, route and monetize 14,982+ MCP tools.
16 tools: 1 do something that can't be undone, 8 change things and 7 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the MetaMesh-UGA MCP server can do
The MetaMesh-UGA MCP server is published by metamesh-uga.dev, a domain the MCP Registry verified. It has 16 tools. It can do things that cannot be undone, such as sending, paying or publishing (stripe.send_stripe_feedback) and create or change data (8 tools: metamesh.context, metamesh.tool_info, metamesh.metrics, metamesh.health and 4 more), but cannot delete data. 7 tools only read.
1 tool can send data out of your system (stripe.send_stripe_feedback).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 2.0.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
16 tools
Can't be undone 1Claude Code: ask
stripe.send_stripe_feedbackShare feedback about Stripe's products.Can send data outNo findings
Why it is in this group
- The name "stripe.send_stripe_feedback" says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "stripe.send_stripe_feedback" says "send": it sends or publishes something to other people.
Description, as the server wrote it 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…
Changes things 8Claude Code: ask
metamesh.contextCompact snapshot of the MetaMesh gateway: active tool count, top categories, payment/billing status, last discovery.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Compact snapshot of the MetaMesh gateway: active tool count, top categories, payment/billing status, last discovery. Best first call for context.
metamesh.healthGateway health: database connectivity, payment configuration and feature flags.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Gateway health: database connectivity, payment configuration and feature flags.
metamesh.metricsUsage analytics: total tools, calls, success rate and recent error counts.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Usage analytics: total tools, calls, success rate and recent error counts. Read-only.
metamesh.tool_infoDetailed info for a specific catalog tool: description, category, trust/security score, state, source.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Detailed info for a specific catalog tool: description, category, trust/security score, state, source.
stripe.stripe_analyticsThis tool is for analyzing Stripe Sigma and Metrics data (e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_writeWrite data via any Stripe API POST/PATCH/PUT/DELETE operation: 1.No findings
Why it is in this group
- The name "stripe.stripe_api_write" says "write": a word for a change.
Description, as the server wrote it Write data via any Stripe API POST/PATCH/PUT/DELETE operation: 1. Use an operation ID returned by stripe_api_search. Do not infer or guess operation IDs. 2. Use stripe_api_details…
stripe.stripe_implementation_plannerStripe integration planner.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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…
stripe.stripe_reportsDeprecated: `stripe_reports` has been replaced by `stripe_analytics`.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Deprecated: `stripe_reports` has been replaced by `stripe_analytics`. Do not call this tool. Call `stripe_analytics` instead with the same `intent` and `params`, except use the `s…
Only reads 7Show 7 read-only tools
metamesh.discovery_statusControl/observability: status of the registry discovery engine (active tools, last run, pages fetched).No findings
Why it is in this group
- The name "metamesh.discovery_status" says "status": a word for reading.
Description, as the server wrote it Control/observability: status of the registry discovery engine (active tools, last run, pages fetched).
metamesh.search_toolsSearch the catalog of 13k+ MCP tools by keyword.No findings
Why it is in this group
- The name "metamesh.search_tools" says "search": a word for reading.
Description, as the server wrote it Search the catalog of 13k+ MCP tools by keyword. Returns concise matches (name, category, description). Use this instead of listing all tools.
stripe.get_stripe_account_infoThis will get the account info for the logged in Stripe account.No findings
Why it is in this group
- The name "stripe.get_stripe_account_info" says "get": a word for reading.
Description, as the server wrote it This will get the account info for the logged in Stripe account.
stripe.search_stripe_documentationSearch the Stripe documentation for the given question and language.No findings
Why it is in this group
- The name "stripe.search_stripe_documentation" says "search": a word for reading.
Description, as the server wrote it 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.stripe_api_detailsGet detailed parameter information for a specific Stripe API operation.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it 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_readRead data from any Stripe API GET operation: 1.No findings
Why it is in this group
- The name "stripe.stripe_api_read" says "read": a word for reading.
Description, as the server wrote it 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_searchSearch for Stripe API operations by providing an intent and a resource to operate on.No findings
Why it is in this group
- The name "stripe.stripe_api_search" says "search": a word for reading.
Description, as the server wrote it 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…
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:52 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- yes
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (1 irreversible, 7 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.metamesh-uga.dev/mcp: tools/list returned 15 tools to an anonymous client, including stripe.send_stripe_feedback (irreversible), metamesh.context (write), metamesh.tool_info (write), metamesh.metrics (write), metamesh.health (write) and 3 more
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 9 to 8
- Nov 6, 2026
- Tools that change things, listed without credentials: 8 to 9
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 9 -> 8.View diff
- Tools that change things, listed without credentials: 9 to 8
Tools1 added, 3 changed.+1 added~3 changedView diff
- Added:stripe.stripe_reportsChanges things
- Changed:stripe.send_stripe_feedbackCan't be undoneinputSchema
- Changed:stripe.stripe_analyticsChanges thingsinputSchema
- Changed:stripe.stripe_api_writeChanges thingsdescription
PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 9.View diff
- Tools that change things, listed without credentials: 8 to 9
Install
Pinned to version 2.0.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http metamesh-uga https://api.metamesh-uga.dev/mcpclaude mcp add --transport http metamesh-uga https://api.metamesh-uga.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__metamesh-uga__metamesh_search_tools",
"mcp__metamesh-uga__metamesh_discovery_status",
"mcp__metamesh-uga__stripe_search_stripe_documentation",
"mcp__metamesh-uga__stripe_get_stripe_account_info",
"mcp__metamesh-uga__stripe_stripe_api_search",
"mcp__metamesh-uga__stripe_stripe_api_details",
"mcp__metamesh-uga__stripe_stripe_api_read"
],
"ask": [
"mcp__metamesh-uga__metamesh_context",
"mcp__metamesh-uga__metamesh_tool_info",
"mcp__metamesh-uga__metamesh_metrics",
"mcp__metamesh-uga__metamesh_health",
"mcp__metamesh-uga__stripe_stripe_implementation_planner",
"mcp__metamesh-uga__stripe_send_stripe_feedback",
"mcp__metamesh-uga__stripe_stripe_api_write",
"mcp__metamesh-uga__stripe_stripe_analytics",
"mcp__metamesh-uga__stripe_stripe_reports"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as metamesh-uga. Review it before you use it.
Capability tags behind 1 rule
- mcp__metamesh-uga__stripe_send_stripe_feedback outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.metamesh-uga/metamesh-uga/verify?hash=2237576508fa1bbec1d68db8b6779ace2769982f6132a20cde374d33b617d26a" | jq -e '.changed == false'Pinned hash 2237576508fa, from Nov 11, 2026, 08:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.metamesh-uga/metamesh-uga/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.metamesh-uga/metamesh-uga)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:11 UTC.
MetaMesh-UGA MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MetaMesh-UGA MCP server safe?
- No scan can promise that. What its definitions show: 16 tools, 9 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the MetaMesh-UGA MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the MetaMesh-UGA MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: stripe.send_stripe_feedback.
What tools does the MetaMesh-UGA MCP server have?
- 16 tools: 1 irreversible, 8 write, 7 read. stripe.send_stripe_feedback, metamesh.context, metamesh.tool_info, metamesh.metrics, metamesh.health, stripe.stripe_implementation_planner, stripe.stripe_api_write, stripe.stripe_analytics and 8 more.
Does the MetaMesh-UGA MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the MetaMesh-UGA MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): stripe.send_stripe_feedback.
Has the MetaMesh-UGA MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.