mcp-registry/studio.pzero/mcp · v1.0.0
As of 2026-10-26 21:32 UTC, the Pzero MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.
Prepaid inference for agents over hosted MCP. Chat, image, and video.
Point your MCP client at this streamable-http endpoint: https://mcp.pzero.studio/mcp
24 parameter(s) across 6 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
13 of 18 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 6 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fstudio.pzero%2Fmcp/fixes
{
"name": "get_capacity",
"description": "GET /v1/capacity — routable DIEM and price bands before funding or spend decisions.",
"inputSchema": {
"type": "object",
"properties": {
"max_price_cents": {
"type": [
"null",
"integer"
],
"description": "Optional buyer ceiling 30-80"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_generation_status",
"description": "POST /v1/video/retrieve once — JSON status or delivered MP4.",
"inputSchema": {
"type": "object",
"required": [
"queue_id"
],
"properties": {
"queue_id": {
"type": "string",
"description": "Queue id from video_queue / generate_video"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_models",
"description": "GET /v1/models — resolve a live model id before inference. Optional id retrieves one public row (same object as that id in the list). Do not hardcode model ids.",
"inputSchema": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Optional venice model id (bare or pzero/). Omit for the full list."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/studio.pzero/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/studio.pzero/mcp"}) over MCP.
generate_image ~172 tokensgenerate_video ~161 tokenschat_completions ~154 tokensvideo_quote ~136 tokensvideo_queue ~130 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fstudio.pzero%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fstudio.pzero%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fstudio.pzero%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fstudio.pzero%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fstudio.pzero%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7f4b76bcc214d455…, first seen 2026-10-17, included at leaf 593 of 75,576. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable ml servers · most reliable security servers · most reliable media servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 21:32 UTC, the Pzero MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.
Pzero MCP server advertises 18 tools, including agent_me, chat_completions, create_key, funding_instructions, generate_image.
Point your MCP client at this streamable-http endpoint: https://mcp.pzero.studio/mcp
Glimind scanned all 18 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.