ProofStream
NPM · PROOFSTREAM-MCP · SCANNED AUG 3
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. 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 88 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · proofstream-mcp
claude mcp add proofstreamai-proofstream-mcp -- npx -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": {
"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.
- 3 Aug 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.
- 2 Aug 26 +18
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: MIT functional
- 1 Aug 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −31
- Known CVEs: partial → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Dependency health: partial → unverified ▼ functional
- 29 Jul 26 +33
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Schema quality: unverified → good ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 27 Jul 26 37
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.