Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Rent real NVIDIA GPUs from your agent. Browse with no wallet; pay per second onchain.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
PRISM_AGENT_KEY, PRISM_ESCROW, PRISM_DAILY_BUDGET_USDG, PRISM_MAX_USDG, PRISM_SPEND_POLICYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"prismnetwork-tech": {
"command": "npx",
"args": [
"-y",
"@prismnetwork/mcp"
],
"env": {
"PRISM_AGENT_KEY": "your-value",
"PRISM_ESCROW": "your-value",
"PRISM_DAILY_BUDGET_USDG": "your-value",
"PRISM_MAX_USDG": "your-value",
"PRISM_SPEND_POLICY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add prismnetwork-tech --env PRISM_AGENT_KEY=your-value --env PRISM_ESCROW=your-value --env PRISM_DAILY_BUDGET_USDG=your-value --env PRISM_MAX_USDG=your-value --env PRISM_SPEND_POLICY=your-value -- npx -y @prismnetwork/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"prismnetwork-tech": {
"command": "npx",
"args": [
"-y",
"@prismnetwork/mcp"
],
"env": {
"PRISM_AGENT_KEY": "your-value",
"PRISM_ESCROW": "your-value",
"PRISM_DAILY_BUDGET_USDG": "your-value",
"PRISM_MAX_USDG": "your-value",
"PRISM_SPEND_POLICY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"prismnetwork-tech": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@prismnetwork/mcp"
],
"env": {
"PRISM_AGENT_KEY": "your-value",
"PRISM_ESCROW": "your-value",
"PRISM_DAILY_BUDGET_USDG": "your-value",
"PRISM_MAX_USDG": "your-value",
"PRISM_SPEND_POLICY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
PRISM_ESCROW envPRISM_DAILY_BUDGET_USDG envPRISM_MAX_USDG envPRISM_SPEND_POLICY envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account prismnetwork-tech, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: PRISM_AGENT_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.10.0) reached the registry 41 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, dotnet-mcp
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
An MCP server that lets Claude (or any MCP client) see and lease real GPUs through Prism Network. Give it a wallet and it handles auth, onchain payment, provisioning, and SSH.
Looking costs nothing and needs no configuration:
claude mcp add prism -- npx -y @prismnetwork/mcp
Then ask what you can rent. prism_list_gpus answers from live capacity with real prices. Leasing spends money, so those tools ask for a wallet and say so.
| Tool | Wallet |
|---|---|
prism_budget | no |
prism_list_gpus | no |
prism_price_index | no |
prism_receipts | no |
prism_wallet | yes |
prism_leases | yes |
prism_infer | yes |
prism_infer_batch | yes |
prism_confidential_infer | yes |
prism_verify_attestation | no |
prism_lease_and_run | yes |
prism_lease | yes |
prism_run | yes |
prism_batch_run | yes |
prism_end_lease | yes |
prism_vault_store | yes |
prism_vault_list | yes |
prism_vault_read | yes |
prism_vault_delete | yes |
prism_vault_release | yes |
prism_budget: the spending limits this server enforces, what it has spent in the last 24 hours, and the recent charges.prism_wallet: the agent's address and USDG/ETH balances.prism_list_gpus: GPUs available to lease, with price per second and per hour.prism_price_index: sourced and settled pricing per GPU model, for cost estimates.prism_receipts: recent settled receipts from the public proof feed, with the settlement transaction on Robinhood Chain.prism_leases: this wallet's leases and their state.prism_infer: buy one LLM generation from the managed inference endpoint, paying the quoted USDG price from this wallet (about 0.01 USDG). Waits through a cold start; an unconsumed payment is kept and reused on the next call instead of paying twice.prism_infer_batch: buy many generations in one paid call, at the single-generation price times the number of prompts. Each prompt runs whole on a rented GPU and they are spread across every GPU the endpoint holds, so a list of prompts finishes far sooner than the same prompts sent one at a time. Returns every answer in order with a Merkle receipt naming the leases that did the work.prism_confidential_infer: buy one generation that runs inside a GPU TEE. The message contents are encrypted to a key the enclave's own attestation commits to, so this server's relay carries ciphertext and cannot read the prompt or the answer. Returns the answer, the cost and a receipt id the workload signed over the exact bytes of the exchange.prism_verify_attestation: check one of those generations against its receipt and the hardware behind it. The server remembers the digests of the last few confidential calls, so the verdict is bound to the bytes it actually sent and received. Every check is reported with its result, including the two that cannot be established today: private-key custody, and where TLS terminates.prism_lease_and_run: lease a GPU, run a command, return the output (one shot).prism_lease: lease a GPU and keep it; returns a lease_id and SSH access. The SSH block carries host_key_fingerprint and host_key_claim when the network can say which machine should answer, and says so plainly when it cannot. Check it before connecting by hand; prism_run checks it for you.prism_run: run a command on an existing lease.prism_batch_run: fund a lease that runs one command with no interactive access; the node reports the signed output. Matches only suppliers at trust class isolated or above, so it can find no supplier when none is online.prism_end_lease: release a lease. Billing stops at the release; the unused deposit returns after settlement.prism_vault_store: seal private data under the wallet-derived key.prism_vault_list: list sealed items; values are never returned.prism_vault_read: decrypt one item in this process.prism_vault_delete: permanently delete an item.prism_vault_release: authorize an item into a lease that clears its trust floor.Two ceilings bound what this server can spend, and a refusal quotes both.
| Variable | Default | What it bounds |
|---|---|---|
PRISM_MAX_USDG | 1 | Any single lease or generation. max_usdg on a call may lower it, never raise it past this. |
PRISM_DAILY_BUDGET_USDG | 5 | Everything in a rolling 24 hours. 0 removes the ceiling. |
PRISM_LEDGER_PATH | ~/.prism/spend.json | Where the spend is recorded. |
A max_usdg above PRISM_MAX_USDG is clamped back to it. The argument is written by the agent being bounded, so it is treated as a request for a lower ceiling and never as permission for a higher one.
Spend is written before the money moves, so a crash between funding an escrow and answering is counted rather than forgiven, and a restart does not hand back a fresh day's allowance. Only an attempt that provably never reached the chain is reverted. Two clients pointed at one wallet share one ceiling, because they share the ledger file.
None of this is the real limit. Fund a dedicated wallet with what you are willing to lose: that balance is what survives a bug in everything above.
The limits above cap how much an agent spends. A spend policy decides whether a given lease has a reason you accept. Set PRISM_SPEND_POLICY to the policy as JSON, or to the path of a JSON file:
{
"policy_id": "gpu-v1", "allow": ["fine_tune", "benchmark"], "require": ["needs_gpu"], "minimums": { "needs_gpu": 0.8 } }
Every lease tool then takes a decision: the action, what made the call, and typed answers with a confidence from 0 to 1. A decision that misses the policy is refused with every reason before anything is quoted, funded or counted against the budget. One that passes is hashed into the escrow deposit, so the lease on chain carries a reference only that decision reproduces. prism_budget shows the policy in force. Without PRISM_SPEND_POLICY a decision is optional and still binds when given.
The binding shows a decision existed before the money moved and met your rules. It does not show the decision was sound.
Tools that spend are annotated destructiveHint and carry anthropic/requiresUserInteraction, so Claude Code asks before every one of them even in modes that otherwise approve tools automatically.
An agent that handles a card, an identity document or a credential should not write it into a leased workspace. prism_vault_store seals it under a key derived from the agent's wallet inside this server process; Prism receives ciphertext and holds no way to read it.
Each item names the weakest workspace trust class it may ever be released into, and new items default to confidential, above anything the network serves today. prism_vault_release is therefore refused on current capacity instead of handing a secret to a host that can read it. Lowering an item's floor is a deliberate act, and allowed releases are recorded against the account.
Point your MCP client (Claude Desktop / Code) at the published server:
{
"mcpServers": { "prism": { "command": "npx", "args": ["-y", "@prismnetwork/mcp"], "env": { "PRISM_AGENT_KEY": "0x ", "PRISM_ESCROW": "0xfD4228eEEfC49e4b76A0CD40af9fdd546220B2FD" } } } }
The wallet needs USDG (0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168) and Robinhood-Chain ETH for gas. See the SDK's Funding section for how to fund a fresh wallet.
Or add it to Claude Code in one line:
claude mcp add prism \
--env PRISM_ESCROW=0xfD4228eEEfC49e4b76A0CD40af9fdd546220B2FD \ --env PRISM_AGENT_KEY=0x \ -- npx -y @prismnetwork/mcp
prism_lease and prism_lease_and_run block while a GPU provisions (usually one to four minutes, occasionally longer on a slow host). Configure your MCP client to allow long tool calls.