Skip to main content
Glama
ProofStreamai

ProofStream MCP Server

Official

proofstream_submit_request

Submit a verification request to dispatch a human verifier on-site for real-world confirmation, with livestream and timestamped evidence report.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRequester full name
emailYesEmail for report delivery and credentials
companyNoOrganization name (optional)
client_typeNoType of requesterAI Agent / Autonomous System
serviceYesproduct = Product Verification | document = Document Verification | property = Property & Asset Check
livestreamNoWhether to include live video feed access (adds cost)no
urgencyNostandard = 24-72 hours | rush = within 24h (+50%) | same_day = +100%standard
descriptionYesWhat needs to be verified — be specific
locationYesPhysical address or location of the item/property to verify
preferred_dateNoPreferred verification date (YYYY-MM-DD)
metricsNoSpecific checkpoints or things to look for during verification
access_notesNoAccess instructions, contact info for site access
deliverablesNoRequired deliverables (Timestamped photo report always included)
billingNoone_time
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It details human on-site verification, livestream, report deliverables, and billing behavior (authorized but not charged until acceptance). Fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is informative but lengthy (multiple paragraphs). However, it is well-structured with clear sections for services, urgency, and process. Could be more concise without losing value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, parameters, pricing, services, process, and billing. No output schema but mentions return of case_id. Adequate for complex tool with 14 parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 93%, so baseline is 3. Description adds pricing context per service and urgency surcharges, and clarifies billing authorization. Adds meaningful value beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool submits a human verification request to ProofStream for physical confirmation. It distinguishes from siblings (check_status and get_pricing) by specifying the action and scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use ('physical confirmation of something in the real world') and lists services/urgency options. Lacks explicit when-not-to-use or alternative tool references, but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ProofStreamai/proofstream-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server