ProofStream
NPM · PROOFSTREAM-MCP · SCANNED SEP 25
Dispatch a human verifier to physically verify anything in the real world. For AI agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 141 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 596 tokens (~198/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% 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
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 ProofStream MCP server?
ProofStream runs locally as an npm package, launched with npx -y proofstream-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · proofstream-mcp
claude mcp add proofstreamai-proofstream-mcp -- npx -y proofstream-mcp
{
"mcpServers": {
"proofstreamai-proofstream-mcp": {
"command": "npx",
"args": [
"-y",
"proofstream-mcp"
]
}
}
} {
"servers": {
"proofstreamai-proofstream-mcp": {
"command": "npx",
"args": [
"-y",
"proofstream-mcp"
]
}
}
} codex mcp add proofstreamai-proofstream-mcp -- npx -y proofstream-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"proofstreamai-proofstream-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"proofstream-mcp"
],
"enabled": true
}
}
} openclaw mcp add proofstreamai-proofstream-mcp --command npx --arg -y --arg proofstream-mcp
mcp_servers:
proofstreamai-proofstream-mcp:
command: "npx"
args: ["-y", "proofstream-mcp"] {
"McpServers": {
"proofstreamai-proofstream-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"proofstream-mcp"
]
}
}
} assistant mcp add proofstreamai-proofstream-mcp -t stdio -c npx -a -y proofstream-mcp
{
"mcpServers": {
"proofstreamai-proofstream-mcp": {
"command": "npx",
"args": [
"-y",
"proofstream-mcp"
]
}
}
} 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
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 25 Sept 2026 · Analysed npm/proofstream-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
proofstream_check_status ~140
Check the status of a ProofStream verification request by case ID. Status values: - pending_review: Request received, awaiting ProofStream acceptance - confirmed: Accepted, payment captured, verification scheduled - scheduled: Verification date/time confirmed - in_progress: Verifier on-site, livestream active (if requested) - completed: Verification done, report delivered to email - cancelled: Request declined (no charge) When status is "completed", the full evidence report and invoice have been emailed to the address provided at submission.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | Case ID returned from proofstream_submit_request (e.g., PS-ABC123) |
No output schema declared.
No examples provided.
proofstream_get_pricing ~24
Get current ProofStream pricing and service details without making a request.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
proofstream_submit_request ~432
Submit a human verification request to ProofStream. A real human will go on-site with a camera, livestream the verification, and deliver a timestamped evidence report (photo + video + written findings). Use this when your workflow requires physical confirmation of something in the real world. Services available: - product_verification ($39 standard / $79 with livestream): Authenticate a physical product — serial numbers, packaging, labels, authentication markers. - document_verification ($99 standard / $149 with livestream): Confirm a physical document exists, matches claimed content, photograph stamps/signatures/seals. - property_asset_check ($249 standard / $349 with livestream): On-site visual condition documentation of a property, vehicle, or asset. Urgency options: standard (24-72 hours), rush (+50%, within 24h), same_day (+100%) Returns a case_id you can use to check status. Card is authorized but NOT charged until ProofStream accepts the request.
| Name | Type | Req | Description |
|---|---|---|---|
| access_notes | string | – | Access instructions, contact info for site access |
| billing | string | – | – |
| client_type | string | – | Type of requester |
| company | string | – | Organization name (optional) |
| deliverables | array | – | Required deliverables (Timestamped photo report always included) |
| description | string | yes | What needs to be verified — be specific |
| string | yes | Email for report delivery and credentials | |
| livestream | string | – | Whether to include live video feed access (adds cost) |
| location | string | yes | Physical address or location of the item/property to verify |
| metrics | string | – | Specific checkpoints or things to look for during verification |
| name | string | yes | Requester full name |
| preferred_date | string | – | Preferred verification date (YYYY-MM-DD) |
| service | string | yes | product = Product Verification | document = Document Verification | property = Property & Asset Check |
| urgency | string | – | standard = 24-72 hours | rush = within 24h (+50%) | same_day = +100% |
No output schema declared.
No examples provided.
What is the ProofStream MCP server?
ProofStream is an MCP server listed in the public MCP registry as io.github.ProofStreamai/proofstream-mcp. Dispatch a human verifier to physically verify anything in the real world. For AI agents. This page covers its npm package (proofstream-mcp).
Is the ProofStream MCP server safe to use?
ProofStream scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 ProofStream MCP server expose?
ProofStream exposes 3 tools: proofstream_submit_request, proofstream_check_status, proofstream_get_pricing. Their descriptions and schemas cost roughly 596 tokens of context every time the server is loaded.
Is the ProofStream MCP server still maintained?
ProofStream is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the ProofStream MCP server under?
ProofStream declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.