MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
MetaMesh-UGA is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
15
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Serverless edge control plane to discover, route and monetize 14,982+ MCP tools.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http metamesh-uga-mcp https://api.metamesh-uga.dev/mcp
# 2 — ask your agent for something these tools do
# metamesh.context, metamesh.search_tools, metamesh.tool_info and 12 more
MetaMesh-UGA costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MUAll 1 server
metamesh-uga1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http metamesh-uga-mcp https://api.metamesh-uga.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Compact snapshot of the MetaMesh gateway: active tool count, top categories, payment/billing status, last discovery. Best first call for context.
No parameter schema on file.
Search the catalog of 13k+ MCP tools by keyword. Returns concise matches (name, category, description). Use this instead of listing all tools.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | Search query, e.g. "github", "database", "email" |
| limit | number | no | Max results (default 10, max 50) |
Detailed info for a specific catalog tool: description, category, trust/security score, state, source.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Exact tool name |
Usage analytics: total tools, calls, success rate and recent error counts. Read-only.
No parameter schema on file.
Control/observability: status of the registry discovery engine (active tools, last run, pages fetched).
No parameter schema on file.
Gateway health: database connectivity, payment configuration and feature flags.
No parameter schema on file.
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| guide_id | string | no | 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 | no | For new guides: describe the use case or business requirements. |
| accept | boolean | no | 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. |
| selected_leaf_nodes | array | no | The IDs of all terminal leaves reached while traversing the guide's decision tree. |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sentiment | string | yes | positive, negative, or neutral |
| message | string | yes | What broke or worked, concrete and specific. At least 5 words. |
| context | string | yes | What the user was trying to accomplish. Do not include sensitive business information. |
| feature_area | string | no | Product area this feedback is about. |
| actor | string | no | Who decided to submit: human or agent. Defaults to agent. |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The user question about integrating with Stripe will be used to search the documentation. |
| language | string | no | The programming language to search for in the documentation. |
| search_only_api_ref | boolean | no | 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 |
This will get the account info for the logged in Stripe account.
No parameter schema on file.
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| intent | string | yes | The intent of the operation |
| resource | string | yes | Target resource the operation is looking to manipulate |
| limit | integer | no | Maximum number of results to return |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stripe_api_operation_id | string | yes | The operation ID to get details for (e.g. 'PostCustomers', 'GetPaymentIntents') |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stripe_api_operation_id | string | yes | The operation ID to execute |
| parameters | object | no | 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 va |
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 …
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stripe_api_operation_id | string | yes | The operation ID to execute |
| parameters | object | no | 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 va |
| human_confirmation | object | no | 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 includ |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| intent | string | yes | The intent of the tool call. |
| params | object | no | The parameters for the tool call. Required parameters depend on the intent. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install MetaMesh-UGA or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.0.3.
2.0.3
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish MetaMesh-UGA can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.