prism-network
Registry code: 5771d7b8e1c0077b
Expose read-only Prism GPU availability, bounded repro preparation, capability-scoped status and evidence, verification checks, and public settlement receipts. Wallet signing and lease creation always require a separate human approval in the Prism web application.
- endpoint
- https://prismnetwork.tech/api/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is prism-network live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
- Is prism-network free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does prism-network have?
- 6 tools: prism_prepare_gpu_repro, prism_verify_gpu_repro, prism_gpu_repro_status, prism_gpu_repro_evidence, prism_gpu_receipts, prism_gpu_capacity.
- Is prism-network safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.4%· all time 99.4%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- list available gpu capacity and prices
- prepare a gpu reproduction job
- check gpu job status and evidence
- read settlement receipts
- takes → gives
- text → data
- tools
- 5 reads1 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
prism_gpu_receipts reads open 8h ago
Read public Prism settlement receipts. Receipts link platform-attested metering to an onchain settlement; they are not hardware attestation.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "limit": { "type": "integer", "default": 20, "maximum": 100, "minimum": 1 }, "receipt_id": { "type": "string", "maxLength": 128, "minLength": 1 }, "repro_spec_hash": { "type": "string", "pattern": "^[0-9a-f]{64}$" }, "transaction_hash": { "type": "string", "pattern": "^0x[0-9a-fA-F]{64}$" } } }arguments 25 linesprism_gpu_capacity reads open 8h ago
List live Prism GPU capacity and current starting hourly rates. This is read-only and does not reserve a GPU.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "min_vram_gib": { "type": "integer", "maximum": 192, "minimum": 1, "description": "Only return GPU classes meeting this memory minimum." } } }arguments 12 linesprism_prepare_gpu_repro changes data unknown 17h ago
Bind an exact command and digest-pinned image into a short-lived approval intent with a live cost ceiling. This tool cannot spend funds, sign a wallet transaction, or create a lease.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "image", "command", "duration_minutes", "min_vram_gib" ], "properties": { "image": { "type": "string", "maxLength": 512, "minLength": 1, "description": "Public OCI image pinned as repository@sha256:<64 lowercase hex characters>." }, "command": { "type": "string", "maxLength": 2048, "minLength": 1, "description": "Exact command to run on the GPU, up to 2 KiB UTF-8." }, "min_vram_gib": { "type": "integer", "maximum": 192, "minimum": 1 }, "duration_minutes": { "anyOf": [ { "type": "number", "const": 30 }, { "type": "number", "const": 60 }, { "type": "number", "const": 120 }, { "type": "number", "const": 360 } ] }, "expected_exit_code": { "type": "integer", "default": 0, "maximum": 255, "minimum": 0 } } }arguments 55 linesprism_verify_gpu_repro reads unknown 17h ago
Return the available token, spec, command, report-signature, result, and settlement checks for a GPU repro. Node means an enrolled device-signed report; managed means a Prism gateway-signed report from central SSH orchestration. Neither signature alone proves faithful computation.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "repro_token" ], "properties": { "repro_token": { "type": "string", "pattern": "^[A-Za-z0-9_-]{43}$" } } }arguments 13 linesprism_gpu_repro_status reads unknown 17h ago
Read the state and bounded result of one GPU repro using its 256-bit read capability. This cannot create or change a lease.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "repro_token" ], "properties": { "repro_token": { "type": "string", "pattern": "^[A-Za-z0-9_-]{43}$" } } }arguments 13 linesprism_gpu_repro_evidence reads unknown 8h ago
Read capability-scoped execution evidence for one GPU repro. A node report is signed by an enrolled device key; a managed report is signed by the Prism gateway for a centrally orchestrated SSH run. Either signature authenticates a report, but neither alone proves faithful computation.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "repro_token" ], "properties": { "repro_token": { "type": "string", "pattern": "^[A-Za-z0-9_-]{43}$" } } }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id5771d7b8e1c0077b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/5771d7b8e1c0077b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/5771d7b8e1c0077b?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.