_ registry / mcp streamable-http · checked 6m ago

metamesh-uga-gateway

https://api.metamesh-uga.dev

Registry code: 8c0b04dfcf84abd9

api record

Universal Gateway Adapter for MCP servers. Serverless, edge-native, AI agent ready.

from a public catalogue that lists it, not from the operator

endpoint
https://api.metamesh-uga.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is metamesh-uga-gateway live?
Yes — it answered the hub's last check (checked 6m ago). It answered 100% of checks over the last 30 days.
Is metamesh-uga-gateway free to use?
Yes — the hub reached it with no key and no payment.
What tools does metamesh-uga-gateway have?
15 tools: metamesh.search_tools, stripe.stripe_api_read, metamesh.metrics, stripe.stripe_implementation_planner, stripe.send_stripe_feedback, stripe.stripe_api_details, stripe.stripe_analytics, stripe.stripe_api_write, ….
Is metamesh-uga-gateway safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
110ms

last good check

priced tools
0

of 15 tools

_ answered our checks, 90 days 320 checks · signed record
  • unknown → live
_ what it is for
topic
developer tools apis & integration
used for
  • search a catalog of mcp tools
  • read stripe data
  • write stripe data
  • search stripe documentation
takes → gives
text, data → data, text
tools
13 reads1 changes data1 sends messages
note
resells another provider
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 15 tools
3 open 12 never probed 3 of 15 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • metamesh.health reads open 14h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • metamesh.discovery_status reads open 14h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • stripe.get_stripe_account_info reads open 14h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • metamesh.search_tools reads unknown 7h ago

    Search the catalog of 13k+ MCP tools by keyword. Returns concise matches (name, category, description). Use this instead of listing all tools.

    mcp-tool

    {
  "type": "object",
  "required": [
    "q"
  ],
  "properties": {
    "q": {
      "type": "string",
      "description": "Search query, e.g. \"github\", \"database\", \"email\""
    },
    "limit": {
      "type": "number",
      "description": "Max results (default 10, max 50)"
    }
  }
}
    arguments 16 lines
  • stripe.stripe_api_read reads unknown 7h ago

    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…

    mcp-tool

    {
  "type": "object",
  "required": [
    "stripe_api_operation_id"
  ],
  "properties": {
    "parameters": {
      "type": "object",
      "description": "All path, query, and request-body values for the API call. Include path parameters (e.g. 'customer' for /v1/customers/{customer}) here. Array fields (e.g. line_items) must be passed as a JSON array value, not as a plain string."
    },
    "stripe_api_operation_id": {
      "type": "string",
      "examples": [
        "PostCustomers",
        "GetPaymentIntents"
      ],
      "description": "The operation ID to execute"
    }
  }
}
    arguments 20 lines
  • metamesh.metrics reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • stripe.stripe_implementation_planner reads unknown never probed

    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…

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "accept": {
      "type": "boolean",
      "description": "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": {
      "type": "string",
      "description": "For new guides: describe the use case or business requirements."
    },
    "guide_id": {
      "type": "string",
      "description": "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": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "The IDs of all terminal leaves reached while traversing the guide's decision tree."
    }
  }
}
    arguments 25 lines
  • stripe.send_stripe_feedback sends messages unknown never probed

    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…

    mcp-tool

    {
  "type": "object",
  "required": [
    "sentiment",
    "message",
    "context"
  ],
  "properties": {
    "actor": {
      "enum": [
        "human",
        "agent"
      ],
      "type": "string",
      "description": "Who decided to submit: human or agent. Defaults to agent."
    },
    "context": {
      "type": "string",
      "maxLength": 2000,
      "minLength": 20,
      "description": "What the user was trying to accomplish. Do not include sensitive business information."
    },
    "message": {
      "type": "string",
      "maxLength": 2000,
      "minLength": 20,
      "description": "What broke or worked, concrete and specific. At least 5 words."
    },
    "sentiment": {
      "enum": [
        "positive",
        "negative",
        "neutral"
      ],
      "type": "string",
      "description": "positive, negative, or neutral"
    },
    "feature_area": {
      "enum": [
        "payments",
        "connect",
        "subscriptions",
        "billing",
        "payouts",
        "reporting",
        "invoicing",
        "invoices",
        "checkout",
        "tax",
        "radar",
        "issuing",
        "terminal",
        "treasury",
        "capital",
        "docs",
        "webhooks",
        "cli",
        "dashboard",
        "crypto",
        "stablecoins",
        "managed-payments",
        "mcp",
        "identity",
        "skills",
        "apps",
        "other"
      ],
      "type": "string",
      "description": "Product area this feedback is about."
    }
  }
}
    arguments 72 lines
  • stripe.stripe_api_details reads unknown never probed

    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…

    mcp-tool

    {
  "type": "object",
  "required": [
    "stripe_api_operation_id"
  ],
  "properties": {
    "stripe_api_operation_id": {
      "type": "string",
      "description": "The operation ID to get details for (e.g. 'PostCustomers', 'GetPaymentIntents')"
    }
  }
}
    arguments 12 lines
  • stripe.stripe_analytics reads unknown never probed

    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…

    mcp-tool

    {
  "type": "object",
  "required": [
    "intent"
  ],
  "properties": {
    "intent": {
      "enum": [
        "execute_query_run",
        "retrieve_query_run",
        "search_query_tables",
        "retrieve_query_table",
        "execute_query_template",
        "retrieve_query_template"
      ],
      "type": "string",
      "description": "The intent of the tool call."
    },
    "params": {
      "type": "object",
      "properties": {
        "sql": {
          "type": "string",
          "description": "Used with execute_query_run. The SQL query to execute (Trino 414)."
        },
        "grains": {
          "type": "array",
          "items": {
            "enum": [
              "day",
              "week",
              "month"
            ],
            "type": "string"
          },
          "description": "Used with execute_query_template. Time grain: 'day', 'week', or 'month'. Default is 'month'."
        },
        "metric": {
          "enum": [
            "gross_volume",
            "subscriber_churn_rate",
            "gross_mrr_churn_rate",
            "churned_subscribers",
            "net_mrr_churn_rate",
            "churned_revenue",
            "new_subscribers",
            "active_subscribers",
            "active_subscriber_growth"
          ],
          "type": "string",
          "description": "Used with execute_query_template. The canonical metric name."
        },
        "dimensions": {
          "type": "array",
          "items": {
            "enum": [
              "product",
              "price"
            ],
            "type": "string"
          },
          "description": "Used with execute_query_template. Dimensions to group by: 'product', 'price'."
        },
        "table_name": {
          "type": "string",
          "pattern": "^[a-zA-Z0-9_]+$",
          "description": "Used with retrieve_query_table. The table name."
        },
        "query_run_id": {
          "type": "string",
          "pattern": "^(qryrun|qrun)_[a-zA-Z0-9_]+$",
          "description": "Used with retrieve_query_run or retrieve_query_template. The QueryRun ID to retrieve."
        },
        "search_string": {
          "type": "string",
          "description": "Used with search_query_tables. Keyword to search table names and descriptions."
        },
        "metric_filters": {
          "type": "array",
          "items": {
            "enum": [
              "top5"
            ],
            "type": "string"
          },
          "description": "Used with execute_query_template. Filters to apply: 'top5' or 'all'. Default is 'all'."
        },
        "result_options": {
          "type": "object",
          "properties": {
            "compress_file": {
              "type": "boolean",
              "description": "Whether to compress the generated results file."
            }
          },
          "description": "Used with execute_query_run. Optional settings for the QueryRun results."
        }
      },
      "description": "The parameters for the tool call. Required parameters depend on the intent."
    }
  }
}
    arguments 102 lines
  • stripe.stripe_api_write changes data unknown never probed

    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 …

    mcp-tool

    {
  "type": "object",
  "required": [
    "stripe_api_operation_id"
  ],
  "properties": {
    "parameters": {
      "type": "object",
      "description": "All path, query, and request-body values for the API call. Include path parameters (e.g. 'customer' for /v1/customers/{customer}) here. Array fields (e.g. line_items) must be passed as a JSON array value, not as a plain string."
    },
    "human_confirmation": {
      "type": "object",
      "properties": {
        "approval_token": {
          "type": "string",
          "description": "The ID of the approval token for the request. This is required on only the post-human-confirmation invocation. An example ID is `approval_123`."
        }
      },
      "description": "This tool might require human confirmation. To run it, first invoke it with the desired parameters, ignoring the `approval_token` parameter.\nIf 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.\nYou, as the LLM agent, should:\n\n1. 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.\n2. The human will approve that call.\n3. 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.\n"
    },
    "stripe_api_operation_id": {
      "type": "string",
      "examples": [
        "PostCustomers",
        "GetPaymentIntents"
      ],
      "description": "The operation ID to execute"
    }
  }
}
    arguments 30 lines
  • metamesh.tool_info reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Exact tool name"
    }
  }
}
    arguments 12 lines
  • stripe.stripe_api_search reads unknown 6m ago

    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…

    mcp-tool

    {
  "type": "object",
  "required": [
    "intent",
    "resource"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 5,
      "maximum": 20,
      "minimum": 1,
      "description": "Maximum number of results to return"
    },
    "intent": {
      "type": "string",
      "examples": [
        "create",
        "list",
        "refund"
      ],
      "description": "The intent of the operation"
    },
    "resource": {
      "type": "string",
      "examples": [
        "customer",
        "payout methods",
        "issuing card transactions"
      ],
      "description": "Target resource the operation is looking to manipulate"
    }
  }
}
    arguments 34 lines
  • stripe.search_stripe_documentation reads unknown 7h ago

    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…

    mcp-tool

    {
  "type": "object",
  "required": [
    "question"
  ],
  "properties": {
    "language": {
      "enum": [
        "dotnet",
        "go",
        "java",
        "node",
        "php",
        "ruby",
        "python",
        "curl"
      ],
      "type": "string",
      "description": "The programming language to search for in the documentation."
    },
    "question": {
      "type": "string",
      "maxLength": 1000,
      "description": "The user question about integrating with Stripe will be used to search the documentation."
    },
    "search_only_api_ref": {
      "type": "boolean",
      "description": "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."
    }
  }
}
    arguments 31 lines
  • metamesh.context reads unknown never probed

    Compact snapshot of the MetaMesh gateway: active tool count, top categories, payment/billing status, last discovery. Best first call for context.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 8c0b04dfcf84abd9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8c0b04dfcf84abd9/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/8c0b04dfcf84abd9/badge.svg)](https://brick.blue/agent/8c0b04dfcf84abd9?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
328ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.