Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Foundry: prepaid AI compute in USDF

REMOTE · API.USDF.FI

Prepaid AI compute in USDF: models, quotes and chat with a receipt; pay per call (x402) or by key

Available components

73 Trust /100

Last scanned (14 hours ago)

Scores higher than 64% of remote servers

Reachable. Last reached 22 Oct 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2163 tokens (~216/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 0
    • Tool “balance” rewrote its description, which is the text the model reads security
    • Tool “chat” rewrote its description, which is the text the model reads security
  • 19 Oct 26 +1
    • “x402_pay” reworded the description of “network” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 18 Oct 26 0
    • Tool “agents_market_call” rewrote its description, which is the text the model reads security
    • Tool “balance” rewrote its description, which is the text the model reads security
    • Tool “chat” rewrote its description, which is the text the model reads security
    • Tool “list_tools” rewrote its description, which is the text the model reads security
    • Tool “quote_tool” rewrote its description, which is the text the model reads security
    • Tool “receipt” rewrote its description, which is the text the model reads security
    • Tool “x402_pay” rewrote its description, which is the text the model reads security
  • 17 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Oct 26 70

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Oct 2026 · Probed https://api.usdf.fi/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.usdf.fi CN=YE1,O=Let's Encrypt,C=US 6 Oct 2026 4 Jan 2027 ECDSA 256 ECDSA-SHA384 5827090c2a31769ba3a309f6eb79c17c001
SANs: api.usdf.fi
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.usdf.fi. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
fi. present 18073 13 Verified
usdf.fi. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.usdf.fi/mcp Verified 200
http (plaintext) http://api.usdf.fi/mcp HTTPS enforced 301 https://api.usdf.fi/mcp
MCP tools · 10 exposed · ~2,163 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
agents_market_call ~233

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_calls_unarmed while calls to the market are not switched on. Needs an API key. Returns the seller's answer and the receipt. The input goes to the seller, whose own policy governs what it keeps.

NameTypeReqDescription
idstringyesThe listing's id (svc_...), from agents_market_search
input––What the call sends: JSON for a POST listing, an object of plain values (its query) for a GET one
max_pricestringyesThe 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

No output schema declared.

No examples provided.

agents_market_search ~184

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.

NameTypeReqDescription
limitinteger––
max_pricestring–The most a call may cost in USDF ("0.01")
offsetinteger––
qstring–Words to find in the name, description, tags or host
sortstring–popular (default), price (cheapest first) or new
tagstring–Only listings with this tag

No output schema declared.

No examples provided.

balance ~114

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.

NameTypeReqDescription
addressstring–A wallet address (0x...): its USDF and USDG on the chain, with no key

No output schema declared.

No examples provided.

chat ~717

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 the client must reset its timeout on progress (resetTimeoutOnProgress: true in the TypeScript SDK) or wait that long. At its deadline, or when the client's connection closes, a call is cut: the text produced so far is returned with finish_reason "length" and billed on the provider's usage report where the provider gives one, otherwise on an estimate never above max_tokens; for a model whose reasoning is not streamed, at the held output budget. Cancellation messages are not supported: a call the client stops waiting for without disconnecting runs to completion or its deadline and is billed. With no key, the call is paid with x402 in USDF (signature transfer) or USDG (signed transfer), as POST /x402/v1/chat/completions: without a payment it returns isError with the payment requirements (x402Version, resource, accepts) as structuredContent; sign one accept and call again with the payment in _meta["x402/payment"], the payment argument or the PAYMENT-SIGNATURE header. The quote is the call's maximum cost at the published price (prompt at one token per byte, output at max_tokens, capped as above, no minimum), paid up front; the call is charged what it uses at that price and the rest is refunded in the asset paid, the gateway paying the gas. A paid call runs to its end or its deadline whether or not the client waits and returns the receipt and _meta["x402/payment-response"]; at the deadline the text so far is returned with finish_reason "length" and a note, charged what it used and the rest refunded. A call no provider accepted before its deadline, or whose provider failed or end…

NameTypeReqDescription
max_tokensnumber–Output token budget, a positive integer; defaults to the model's default_max_output, capped at max_output
messagesarrayyesChat messages in the OpenAI format: objects with a role (system, user, assistant or tool) and content (text, or an array of content parts)
modelstringyesModel id from list_models
payment––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
temperaturenumber–Sampling temperature, 0 to 2

No output schema declared.

No examples provided.

list_models ~48

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_tools ~131

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.

NameTypeReqDescription
cursorstring–page.next of the page before
qstring–Words a tool's id, title or description has

No output schema declared.

No examples provided.

quote ~233

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 routes, at the model's price.

NameTypeReqDescription
max_tokensnumber–Output token budget, a positive integer; defaults to the model's default_max_output, capped at max_output
messagesarray–Chat messages in the OpenAI format: objects with a role (system, user, assistant or tool) and content (text, or an array of content parts)
modelstringyesModel id from list_models
promptstring–Prompt text, sent as one user message
providerobject–Routing asks as on the REST API, for example {"private": true} for attested hardware this gateway verified, at the model's price

No output schema declared.

No examples provided.

quote_tool ~93

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.

NameTypeReqDescription
inputobject–The input the call would send, as in the tool's input schema
toolstringyesTool id from list_tools

No output schema declared.

No examples provided.

receipt ~119

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}).

NameTypeReqDescription
request_idstringyesThe id returned with the completion (also the x-request-id header)

No output schema declared.

No examples provided.

x402_pay ~291

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 once the chain shows it, and one that never settles costs nothing. quote: true answers what it would cost and pays nothing. Third-party tools to call this way are listed under marketplace in list_tools (GET /v1/tools?source=marketplace).

NameTypeReqDescription
body––The request body: text, or JSON sent as application/json
headersobject–Headers for the seller (the payment headers are the gateway's)
max_pricestring–The most to pay in USDF, the fee included ("0.05")
methodstring–Default GET, or POST when a body is given
networkstring–Pay on this network only: its CAIP-2 id, one GET /v1/x402/payer lists
quoteboolean–Answer the price and pay nothing
urlstringyesThe seller's URL (https)

No output schema declared.

No examples provided.

Install

How do I install the Foundry: prepaid AI compute in USDF MCP server?

Foundry: prepaid AI compute in USDF is a hosted endpoint at https://api.usdf.fi/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.usdf.fi

# add to Claude Code
claude mcp add --transport http fi-usdf-gateway 'https://api.usdf.fi/mcp'
Common questions

What is the Foundry: prepaid AI compute in USDF MCP server?

Foundry: prepaid AI compute in USDF is an MCP server listed in the public MCP registry as fi.usdf/gateway. Prepaid AI compute in USDF: models, quotes and chat with a receipt; pay per call (x402) or by key. This page covers its hosted endpoint (https://api.usdf.fi/mcp).

Is the Foundry: prepaid AI compute in USDF MCP server safe to use?

Foundry: prepaid AI compute in USDF scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Foundry: prepaid AI compute in USDF MCP server expose?

Foundry: prepaid AI compute in USDF exposes 10 tools: list_models, quote, list_tools, quote_tool, x402_pay, and 5 more. Their descriptions and schemas cost roughly 2,163 tokens of context every time the server is loaded.

Does the Foundry: prepaid AI compute in USDF MCP server require authentication?

No. We connected to Foundry: prepaid AI compute in USDF without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Foundry: prepaid AI compute in USDF MCP server still maintained?

Foundry: prepaid AI compute in USDF is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.