MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Foundry: prepaid AI compute in USDF 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.
What it does
Prepaid AI compute in USDF: models, quotes and chat with a receipt; pay per call (x402) or by key
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http foundry-prepaid-ai-compute-in-usdf-mcp https://api.usdf.fi/mcp
# 2 — ask your agent for something these tools do
# list_models, quote, list_tools and 7 more
Foundry: prepaid AI compute in USDF costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 foundry-prepaid-ai-compute-in-usdf-mcp https://api.usdf.fi/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take Authorization header (Bearer and a prepaid account's API key: chat, balance and receipts on that account. Without it, chat is paid per call with x402, balance reads a wallet address and receipt any request id.) if you want to set it.
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.
10 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.
Models the gateway serves with their prices (USD per 1M tokens, the same figure in USDF), context window, output limits and whether a route is available right now. No key needed.
No parameter schema on file.
The hold the chat tool places before running a request, in USDF and USD (output capped at 4096 tokens). It is an estimate, not a ceiling: a completed request is billed the provider's reported usage, normally less. Pass prompt or messages. No key needed; a request for attested hardware (a :private model id or provider.private), and any request from a Private-tier key, is quoted on its attested rout
| Parameter | Type | Required | Notes |
|---|---|---|---|
| model | string | yes | Model id from list_models |
| prompt | string | no | Prompt text, sent as one user message |
| messages | array | no | Chat messages in the OpenAI format: objects with a role (system, user, assistant or tool) and content (text, or an array of content parts) |
| max_tokens | number | no | Output token budget, a positive integer; defaults to the model's default_max_output, capped at max_output |
| provider | object | no | Routing asks as on the REST API, for example {"private": true} for attested hardware this gateway verified, at the model's price |
Tools you can call through POST /v1/tools/{id}, paid from the same balance and key as chat, each with its price in USDF (what it costs plus 5% at most) and the input it takes, ordered by title. Every tool listed can be called now. q keeps the tools whose id, title or description has those words; a page holds up to 200, and page.next names the next one. No key needed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Words a tool's id, title or description has |
| cursor | string | no | page.next of the page before |
What a call to a tool would hold for this input before it runs (its most it can cost), in USDF and USD, with the tool's price. It checks the input as the call would, and runs and holds nothing. No key needed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | yes | Tool id from list_tools |
| input | object | no | The input the call would send, as in the tool's input schema |
Calls a URL that asks for an x402 payment and pays it for you: the gateway pays the seller in USDC from its own float and charges this key in USDF cost plus 5% at most, no minimum (the seller's amount and a fee of at most 5% of it; never free credit), within the key's and its agent's limits. Needs an API key. Returns the seller's answer with the payment and its receipt; a payment is charged only o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The seller's URL (https) |
| method | string | no | Default GET, or POST when a body is given |
| headers | object | no | Headers for the seller (the payment headers are the gateway's) |
| body | no | The request body: text, or JSON sent as application/json | |
| max_price | string | no | The most to pay in USDF, the fee included ("0.05") |
| network | string | no | Pay on this network only: its CAIP-2 id, one GET /v1/x402/payer lists |
| quote | boolean | no | Answer the price and pay nothing |
Agents, APIs and tools priced per call, in one market, every listing in the same shape: its id (svc_...), name, description, tags, site and logo, how it is called (GET or POST), what one call costs in USDF from this key's balance, input and output examples, and the data policy. Ordered by popularity (default), price or newest. No key needed to search; agents_market_call calls one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Words to find in the name, description, tags or host |
| tag | string | no | Only listings with this tag |
| max_price | string | no | The most a call may cost in USDF ("0.01") |
| sort | string | no | popular (default), price (cheapest first) or new |
| limit | integer | no | — |
| offset | integer | no | — |
Calls a listing of the agents market by its id (svc_..., from agents_market_search), paid from this key's USDF balance (never free credit) within the key's and its agent's limits and at most max_price: what one call costs and nothing on top; a call its seller does not answer 2xx costs nothing, or no more than what its seller kept of it. Every listing is called the same way, and answers 503 market_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The listing's id (svc_...), from agents_market_search |
| input | no | What the call sends: JSON for a POST listing, an object of plain values (its query) for a GET one | |
| max_price | string | yes | The most this call may cost in USDF ("0.05"): required, as a seller may change its price; the listing's price is in agents_market_search |
Runs a chat completion and returns the text with its receipt (tokens, price, cost, balance, settlement). With an API key it spends from that key's balance, holding the most the request can cost first. Not streamed. Output is capped at 4096 tokens. A call without a progress token answers within 55 s of arriving. With a progress token, progress is sent every 15 s and the call may run 10 minutes, so
| Parameter | Type | Required | Notes |
|---|---|---|---|
| model | string | yes | Model id from list_models |
| messages | array | yes | Chat messages in the OpenAI format: objects with a role (system, user, assistant or tool) and content (text, or an array of content parts) |
| max_tokens | number | no | Output token budget, a positive integer; defaults to the model's default_max_output, capped at max_output |
| temperature | number | no | Sampling temperature, 0 to 2 |
| payment | no | With no key: the x402 payment for this call's quote, as the PAYMENT-SIGNATURE value (base64 JSON) or the payload object; _meta["x402/payment"] and the PAYMENT-SIGNATURE header are read too |
With an API key: what the key can spend now, the account's balance and the amount held for requests running, and what is left of the key's budget, in USDF. With address instead, and no key: that wallet's USDF and USDG on the chain now, and how much USDF it lets the signature-transfer contract spend, which x402 payments come from.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | no | A wallet address (0x...): its USDF and USDG on the chain, with no key |
With the API key that made the request: its receipt, with the usage, the price sheet version, the cost and, once settled, the settlement, its transaction and the rows behind the onchain digest. With no key: the public receipt of any request id, x402 ones included, with its line in the usage log, the payment, the settlement and where its proof is (GET /x402/v1/receipts/{id}).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | The id returned with the completion (also the x-request-id header) |
- 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 Foundry: prepaid AI compute in USDF or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_models | no tags | |
| quote | no tags | |
| list_tools | no tags | |
| quote_tool | no tags | |
| x402_pay | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| agents_market_search | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| agents_market_call | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| chat | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| balance | no tags | |
| receipt | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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 1.0.0.
No release note was published with this version.
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.
Any signed-in account that does not publish Foundry: prepaid AI compute in USDF can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.