PZERO
REMOTE · MCP.PZERO.STUDIO · SCANNED SEP 21
Prepaid inference for agents over hosted MCP. Chat, image, and video.
Available components
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1175 tokens (~48/item across 24 items; 18 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% 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 19 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
How do I install the PZERO MCP server?
PZERO is a hosted endpoint at https://mcp.pzero.studio/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 · mcp.pzero.studio
claude mcp add --transport http studio-pzero-mcp 'https://mcp.pzero.studio/mcp'
{
"mcpServers": {
"studio-pzero-mcp": {
"url": "https://mcp.pzero.studio/mcp"
}
}
} {
"servers": {
"studio-pzero-mcp": {
"type": "http",
"url": "https://mcp.pzero.studio/mcp"
}
}
} [mcp_servers.studio-pzero-mcp] url = "https://mcp.pzero.studio/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"studio-pzero-mcp": {
"type": "remote",
"url": "https://mcp.pzero.studio/mcp",
"enabled": true
}
}
} openclaw mcp add studio-pzero-mcp --url 'https://mcp.pzero.studio/mcp' --transport streamable-http
mcp_servers:
studio-pzero-mcp:
url: "https://mcp.pzero.studio/mcp" {
"McpServers": {
"studio-pzero-mcp": {
"Transport": "http",
"Url": "https://mcp.pzero.studio/mcp"
}
}
} assistant mcp add studio-pzero-mcp -t streamable-http -u 'https://mcp.pzero.studio/mcp'
{
"mcpServers": {
"studio-pzero-mcp": {
"type": "http",
"url": "https://mcp.pzero.studio/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Sept 2026 · Probed https://mcp.pzero.studio/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.protocol-zero.ai | CN=YE1,O=Let's Encrypt,C=US | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 505ec781385dfdbd528eb5a95f912660cff |
| SANs: api.protocol-zero.ai, api.pzero.studio, docs.protocol-zero.ai, docs.pzero.studio, mcp.pzero.studio, protocol-zero.ai, pzero.studio, sellers.pzero.studio, telemetry.protocol-zero.ai, telemetry.pzero.studio, www.protocol-zero.ai, www.pzero.studio | ||||||
| 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 mcp.pzero.studio. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| studio. | present | 1354 | 8 | Verified |
| pzero.studio. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.pzero.studio/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://mcp.pzero.studio/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://mcp.pzero.studio/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Problem | metadata_incomplete |
| Resource | https://mcp.pzero.studio/mcp |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.pzero.studio/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.pzero.studio/mcp | HTTPS enforced | 301 | https://mcp.pzero.studio/mcp |
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 →
agent_me ~44
GET /v1/agent/me — balances, key prefix, max price. Pending USDC is not spendable until confirmed. If confirmed is low, call funding_instructions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chat_completions ~83
POST /v1/chat/completions (buffered). Pass a live model id from get_models. Returns completion plus cost trace headers.
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | null|integer | – | – |
| messages | null|array | yes | OpenAI-style messages |
| model | string | yes | Live model id from get_models |
| temperature | null|number | – | – |
No output schema declared.
No examples provided.
create_key ~46
POST /v1/agent/keys — mint another key. Does NOT add USDC credit. Plaintext shown once.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Label for the new API key |
No output schema declared.
No examples provided.
funding_instructions ~51
How to fund a PZERO account and authenticate MCP. MCP never accepts payment or wallet keys. Fund via Studio x402 top-up or agent HTTP signup/refill, then use Authorization Bearer pzero_…
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
generate_image ~114
POST /v1/image/generate — intent tool for image generation. Rejects enable_web_search. Returns images plus cost trace.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect_ratio | string | – | – |
| enable_web_search | null|boolean | – | – |
| hide_watermark | null|boolean | – | – |
| model | string | yes | Live image model id from get_models |
| n | null|integer | – | Variants 1-4 |
| prompt | string | yes | – |
| quality | string | – | – |
| resolution | string | – | – |
No output schema declared.
No examples provided.
generate_video ~105
Intent tool: POST /v1/video/queue (settles then enqueues). Returns queue_id + cost. Confirm before calling — this spends prepaid USDC. Poll with get_generation_status or wait_for_video.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect_ratio | string | – | – |
| audio | null|boolean | – | – |
| duration | null|integer | – | – |
| model | string | yes | Live video model id from get_models |
| prompt | string | yes | – |
| resolution | string | – | – |
No output schema declared.
No examples provided.
get_capacity ~48
GET /v1/capacity — routable DIEM and price bands before funding or spend decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| max_price_cents | null|integer | – | Optional buyer ceiling 30-80 |
No output schema declared.
No examples provided.
get_generation_status ~41
POST /v1/video/retrieve once — JSON status or delivered MP4.
| Name | Type | Req | Description |
|---|---|---|---|
| queue_id | string | yes | Queue id from video_queue / generate_video |
No output schema declared.
No examples provided.
get_models ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Optional venice model id (bare or pzero/). Omit for the full list. |
No output schema declared.
No examples provided.
get_request ~45
GET /v1/agent/requests/{support_reference} — recover cost/trace for a prior request.
| Name | Type | Req | Description |
|---|---|---|---|
| support_reference | string | yes | UUID support reference from a prior call |
No output schema declared.
No examples provided.
list_keys ~26
GET /v1/agent/keys — list active API key metadata (never plaintext).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
revoke_key ~48
DELETE /v1/agent/keys/{id} — irreversible. Do not revoke the key used by this MCP session unless intentional.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | UUID of the key to revoke |
No output schema declared.
No examples provided.
set_max_price ~74
PATCH /v1/agent/max-price — raise/lower ceiling (30-80). Use when tools return no_eligible_supply with cheapest_posted_cents. Does not auto-apply.
| Name | Type | Req | Description |
|---|---|---|---|
| max_price_cents_per_dollar | integer | yes | Buyer ceiling in cents per DIEM dollar, 30-80 |
No output schema declared.
No examples provided.
video_complete ~37
POST /v1/video/complete — optional cleanup after retrieve.
| Name | Type | Req | Description |
|---|---|---|---|
| queue_id | string | yes | Queue id from video_queue / generate_video |
No output schema declared.
No examples provided.
video_queue ~81
POST /v1/video/queue — paid settle+enqueue. Prefer generate_video for agents.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect_ratio | string | – | – |
| audio | null|boolean | – | – |
| duration | null|integer | – | – |
| model | string | yes | Live video model id from get_models |
| prompt | string | yes | – |
| resolution | string | – | – |
No output schema declared.
No examples provided.
video_quote ~87
POST /v1/video/quote — no settle, no job. Check clears_now vs price ceiling vs funding before queue.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect_ratio | string | – | – |
| audio | null|boolean | – | – |
| duration | null|integer | – | – |
| model | string | yes | Live video model id from get_models |
| prompt | string | yes | – |
| resolution | string | – | – |
No output schema declared.
No examples provided.
video_retrieve ~39
POST /v1/video/retrieve — power-user status/media poll.
| Name | Type | Req | Description |
|---|---|---|---|
| queue_id | string | yes | Queue id from video_queue / generate_video |
No output schema declared.
No examples provided.
wait_for_video ~67
Poll video retrieve until delivered or failed. Backs off on 502.
| Name | Type | Req | Description |
|---|---|---|---|
| interval_ms | null|integer | – | Poll interval ms, default 5000 |
| max_polls | null|integer | – | Max polls, default 120 |
| queue_id | string | yes | – |
No output schema declared.
No examples provided.
What is the PZERO MCP server?
PZERO is an MCP server listed in the public MCP registry as studio.pzero/mcp. Prepaid inference for agents over hosted MCP. Chat, image, and video. This page covers its hosted endpoint (https://mcp.pzero.studio/mcp).
Is the PZERO MCP server safe to use?
PZERO scores 85 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 PZERO MCP server expose?
PZERO exposes 18 tools: agent_me, chat_completions, create_key, funding_instructions, generate_image, and 13 more. Their descriptions and schemas cost roughly 1,106 tokens of context every time the server is loaded.
Does the PZERO MCP server require authentication?
Yes. PZERO asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the PZERO MCP server still maintained?
PZERO is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.