proofrelay
Server 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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| proofrelay.get_verifier_statusA | Read-only status lookup for public ProofRelay discovery metadata. Use first to confirm the hosted MCP endpoint, server-card URL, product URL, public tool count, and trust boundary. Requires no authentication, performs no network call from this local wrapper, mutates nothing, and returns JSON text with status, URLs, counts, and non-confidential boundary notes. |
| proofrelay.recommend_checkpointA | Read-only checkpoint recommendation for a high-level agent action class. Use before relied-upon actions such as paid_tool_call, revenue_action, external_reliance, or financial_transaction; use get_verifier_status for discovery only and verify_bundle after evidence metadata exists. Requires no authentication, mutates nothing, and returns JSON text with status pass, skipped, or needs_review plus checkpoint and reason fields. |
| proofrelay.verify_bundleA | Read-only public-safe bundle shape check for synthetic or non-confidential evidence metadata. Use when you already have a bundle fixture and need a local pass/fail boundary check before sharing or routing to hosted verification; use recommend_checkpoint when deciding whether a checkpoint is needed. Requires no authentication, mutates nothing, does not certify real-world facts, and returns JSON text with status, checks, problems, verifier, and hosted endpoint fields. |
| proofrelay.scan_mcp_riskA | Read-only advisory scan of caller-supplied public MCP descriptor metadata. Use before registering or trusting an MCP server to flag mutating tools, payment or wallet language, credential signals, or missing public metadata; use verify_bundle for evidence bundles instead. Requires no authentication, does not fetch server_url, mutates nothing, is not a security certification, and returns JSON text with status, findings, recommended_control, non_claims, and boundary fields. |
| proofrelay.describe_cli_sdk_helperA | Read-only integration guide for the invisible pass/fail/review helper pattern. Use when an agent or developer needs to understand how to wrap actions with ProofRelay-style checkpoint statuses; use recommend_checkpoint for a specific action decision. Requires no authentication, mutates nothing, and returns JSON text describing statuses, hosted endpoint, and the action-to-audit flow. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| proofrelay-public-safe-bundle-review | Ask an agent to review a non-confidential evidence bundle without exposing secrets. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ProofRelay MCP server card | Public server-card URL and tool-count metadata. |
| ProofRelay public trust boundary | Public-safe data boundary and non-claims. |
TDQS
Scored across 5 tools
Each tool targets a clearly distinct concern: discovery status, checkpoint recommendation, bundle verification, MCP risk scanning, and helper documentation. The descriptions cross-reference one another and specify exactly when each tool should be used, leaving little room for misselection.
All tool names follow a consistent lowercase snake_case verb_object pattern: get_verifier_status, recommend_checkpoint, verify_bundle, scan_mcp_risk, describe_cli_sdk_helper. The verbs and objects are specific and predictable, with no mixed conventions or vague generic names.
With exactly 5 tools, the server is well-scoped for a read-only advisory utility. Each tool earns its place by covering a separate step in the ProofRelay workflow without redundancy or unnecessary expansion.
For the server's declared read-only advisory purpose, the tool surface is complete: discovery status, checkpoint recommendation, bundle verification, MCP risk scanning, and integration guidance are all present. The descriptions clearly separate local checks from hosted verification, so there are no obvious dead ends within the intended scope.