MetaMesh-UGA

Measured conclusion: Alive, not deep-tested. L2 outcome: not_attempted.

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

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "MetaMesh-UGA": {
      "url": "https://api.metamesh-uga.dev/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured 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.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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.

  Parameters:

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

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• metamesh.tool_info

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

  Parameters:

  • name (required) — string — Exact tool name

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• metamesh.metrics

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

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• metamesh.discovery_status

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

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• metamesh.health

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

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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…

  Parameters:

  • accept — boolean — Set to true when returning the completed decision trees with your chosen options. Include selected_leaf_nodes with the IDs of all terminal leaves reached.
  • message — string — For new guides: describe the use case or business requirements.
  • 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 response, omit this field entirely. Invalid guide_ids will be rejected.
  • selected_leaf_nodes — array — The IDs of all terminal leaves reached while traversing the guide's decision tree.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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…

  Parameters:

  • sentiment (required) — string — positive, negative, or neutral
  • message (required) — string — What broke or worked, concrete and specific. At least 5 words.
  • context (required) — string — What the user was trying to accomplish. Do not include sensitive business information.
  • actor — string — Who decided to submit: human or agent. Defaults to agent.
  • feature_area — string — Product area this feedback is about.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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…

  Parameters:

  • question (required) — string — The user question about integrating with Stripe will be used to search the documentation.
  • language — string — The programming language to search for in 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 parameter references. Use false (default) for conceptual explanations, best practices, integration guides, or troubleshooting help.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• stripe.get_stripe_account_info

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

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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…

  Parameters:

  • intent (required) — string — The intent of the operation
  • resource (required) — string — Target resource the operation is looking to manipulate
  • limit — integer — Maximum number of results to return

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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…

  Parameters:

  • stripe_api_operation_id (required) — string — The operation ID to get details for (e.g. 'PostCustomers', 'GetPaymentIntents')

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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…

  Parameters:

  • stripe_api_operation_id (required) — string — The operation ID to execute
  • parameters — object — All path, query, and request-body values for the API call. Include path parameters here, named as in the path's curly braces (e.g. 'id' for /v1/customers/{id}). Array fields (e.g. line_items) must be passed as a JSON array value, not as a plain string.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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…

  Parameters:

  • stripe_api_operation_id (required) — string — The operation ID to execute
  • parameters — object — All path, query, and request-body values for the API call. Include path parameters here, named as in the path's curly braces (e.g. 'id' for /v1/customers/{id}). Array fields (e.g. line_items) must be passed as a JSON array value, not as a plain string.
  • 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 include an approval request ID and a URL to an approval page for the human to approve the tool call. You, as the LLM agent, should: 1. Present this URL to the human as a clickable markdown link. Tell them that they have to approve this tool call at that URL, and that they should tell you when they have approved the operation. 2. The human will approve that call. 3. After the human tells you they have approved the operation, you must call the tool again with the `approval_token` parameter and the exact same parameters. The operation will then go through.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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…

  Parameters:

  • intent (required) — string — The intent of the tool call.
  • params — object — The parameters for the tool call. Required parameters depend on the intent.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.