ProofStream MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| proofstream_submit_requestA | 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:
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. |
| proofstream_check_statusA | Check the status of a ProofStream verification request by case ID. Status values:
When status is "completed", the full evidence report and invoice have been emailed to the address provided at submission. |
| proofstream_get_pricingA | Get current ProofStream pricing and service details without making a request. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: checking status, getting pricing, and submitting requests. No overlap in functionality.
All tool names follow the consistent pattern 'proofstream_verb_noun' using snake_case, e.g., check_status, get_pricing, submit_request.
Three tools is appropriate for a focused service that covers the main workflow: pricing inquiry, submission, and status checking.
The tool set covers the essential lifecycle: pricing, submission, and status check. Minor gaps exist, such as no explicit cancellation tool, but the status includes cancellation.