agent-services-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROVENANCE_URL | No | The URL of the provenance-receipts service | https://provenance-receipts.gpmiddleton71.workers.dev |
| QUALITY_GATE_URL | No | The URL of the quality-gate service | https://quality-gate.gpmiddleton71.workers.dev |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| certify_provenanceA | Certify the ORIGIN of a piece of content via the provenance-receipts service. Returns an Ed25519-signed receipt committing to a SHA-256 hash of the content, your caller-attested generator_metadata, and a service-set timestamp. PROVES: the content is unmodified (hash) and the receipt was issued by the holder of the service's signing key. DOES NOT PROVE: it does not independently verify generator_metadata — the receipt proves you CLAIMED that metadata at certification time, not that a specific model actually produced the content. This is proof-of-origin/tamper-evidence, not AI-detection and not a truth guarantee. Note: /v1/certify is the paid action; when the underlying service has x402 payments enabled it may require a micropayment. This wrapper forwards the request as-is. |
| verify_provenanceA | Verify a provenance receipt against its content via provenance-receipts. Re-hashes the content and checks the Ed25519 signature; returns { valid, details }. |
| score_qualityA | Score content against the quality-gate service's PUBLISHED rubric and get an Ed25519-signed score receipt. The rubric scores four dimensions — clarity, completeness, internal consistency, and obvious-error freedom (0–25 each, summing to 0–100) — plus flags from a closed vocabulary. Read the exact rubric with get_quality_rubric. WHAT THIS IS: a reproducible score AGAINST OUR PUBLISHED RUBRIC (vX). WHAT IT IS NOT: a measure of absolute truth, an external/third-party standard, or a fact-check — 'obvious-error freedom' catches errors evident from the text or common knowledge, not external verification. Optional target_score (0–100) enables 'no pass, no pay': if the score is below your target, no receipt is issued and (when payments are on) no charge is made — the response returns the failing breakdown with receipt: null. Note: /v1/score is the paid action (one Claude API scoring pass per call) and may require an x402 micropayment when the underlying service has payments enabled. |
| verify_qualityA | Verify a quality score receipt against its content via quality-gate. Re-hashes the content and checks the Ed25519 signature, which covers the score itself — so a forged or altered score fails. Returns { valid, details }. Free. A 200 response means verification ran — always read |
| get_quality_rubricA | Fetch the published Quality Gate rubric (markdown) that score_quality grades against, along with its version. Read this to understand exactly what a quality score means and does not mean. Free; takes no input. |
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 5 tools
Each tool has a distinct purpose: certifying provenance, fetching the quality rubric, scoring quality, and verifying receipts for both provenance and quality. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., certify_provenance, verify_quality), making the set predictable and easy to navigate.
With only 5 tools, the set is well-scoped for the domain of provenance and quality attestation. Each tool earns its place, covering core actions without unnecessary bloat.
The tool surface covers the full workflow: certification, scoring with a rubric, and verification for both. There are no obvious gaps for the stated purpose of provenance and quality assurance.