MetaMesh-UGA

• metamesh.context — Compact snapshot of the MetaMesh gateway: active tool count, top categories, payment/billing status, last discovery. Best first call for context.
• 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.
• metamesh.metrics — Usage analytics: total tools, calls, success rate and recent error counts. Read-only.
• 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.
• stripe.stripe_implementation_planner — Stripe payment integration planner. Use this tool to help users accept payments, sell products online, set up billing, or build any Stripe integration. Call thi
• stripe.send_stripe_mcp_feedback — 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" Inval
• 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.get_stripe_account_info — This will get the account info for the logged in Stripe account.
• 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
• 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, quer
• stripe.stripe_api_read

No long description beyond the summary.