mcp-evidence-api
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_evidence_sessionA | Creates an evidence directory under |
| requestA | Makes an HTTP request and logs the full request/response pair (headers, body, status, timing) as evidence. Sensitive headers (authorization, cookie, api-key, etc.) are redacted before being written to disk. |
| finish_evidence_sessionA | Writes requests.json (all request/response pairs) and manifest.json (summary + failure count), and returns the evidence folder path. Always call this at the end of a verification run. |
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
Each tool has a distinct role: start session, make request, finish session. There is no overlap in functionality.
Tools use snake_case with imperative verbs. 'request' is less descriptive but still follows the verb pattern; the other two follow verb_noun. Overall consistent.
Three tools perfectly cover the session lifecycle: start, execute, finish. No redundancy or missing steps.
The toolset provides a complete workflow for recording HTTP evidence: session creation, request logging, and session finalization. No obvious gaps.