
Prismnetwork Tech
io.github.prismnetwork-techPublished by GitHub account prismnetwork-techv0.10.0Updated Oct 25, 2026
Rent real NVIDIA GPUs from your agent. Browse with no wallet; pay per second onchain.
The publisher's own server: Tech.eu Funding Explorer
Overview
Lets an assistant browse and lease real NVIDIA GPUs through Prism Network, paying per second onchain, and run commands or paid inference on them.
- What you can do
- Browse live GPU capacity and pricing, and check the price index and public receipts without a wallet. Check the agent wallet's address and balances, the enforced spending limits, and the wallet's leases. Lease a GPU and keep it with SSH access, or lease and run a one-shot command; run commands on an existing lease and release it to stop billing. Buy single or batch LLM generations, or confidential generations inside a GPU TEE, and verify their attestations. Seal private items in a wallet-derived vault, list and read them, release them into a lease, or delete them.
- When to use it
- Use it when an assistant needs real GPU compute for training, benchmarking or batch jobs, or paid LLM inference, without setting up cloud accounts by hand. Browsing capacity and prices is free, so it is also useful just to compare GPU costs.
- Requirements
- Runs locally via npx as a stdio process, so Node.js is needed. Leasing and inference need PRISM_AGENT_KEY, a wallet private key, plus PRISM_ESCROW; the wallet must hold USDG and Robinhood-Chain ETH for gas. Optional: PRISM_DAILY_BUDGET_USDG, PRISM_MAX_USDG, PRISM_SPEND_POLICY. Provisioning can block for one to four minutes, so long tool calls must be allowed.
Installation
In SourceWeft
- Open Prismnetwork Tech in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@prismnetwork/mcp
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.
Try it without a wallet
Looking costs nothing and needs no configuration:
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.
Tools
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 alease_idand SSH access. The SSH block carrieshost_key_fingerprintandhost_key_claimwhen the network can say which machine should answer, and says so plainly when it cannot. Check it before connecting by hand;prism_runchecks 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 classisolatedor 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.
Spending limits
Two ceilings bound what this server can spend, and a refusal quotes both.
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.
Spend policy
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:
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.
Vault
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.
Configure
Point your MCP client (Claude Desktop / Code) at the published server:
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:
Timing
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.
Source: mcp/README.md at commit 4e32eb5
Tools
0Version history
2- v0.10.0LatestSep 27, 2026
- v0.9.4Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Tech integrations
Tech.eu Funding Explorer
eu.tech.fundingOfficial publisher
Lets an assistant search European tech funding rounds, companies, investors and exits, with EUR-normalized, source-linked figures.
ScorpTech x402 API
com.it.scorptechOfficial publisher
ScorpTech x402 API's hosted MCP server, published by scorptech.it.com; no sign-in required; Streamable HTTP; 200 tools.

Website Tech Stack Detector
Published by GitHub account prometheus-maker
Apify-hosted MCP server that identifies the technologies behind websites — CMS, frameworks, analytics, CDN, hosting — from a list of URLs.

Website Tech Stack Lookup
Published by GitHub account catalyst-labs-dev
Domains in, tech stack out: 7,600+ technologies, versions, DNS/email providers. $0.003/site.

Data Lantern Website Technology Detector
Published by GitHub account xiezhengyang1990-beep
Remote Apify-hosted MCP server that lets an assistant run batch website technology detection with supporting evidence.