mcp-evidence-api
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/meovan07/mcp-evidence-api'
If you have feedback or need assistance with the MCP directory API, please join our Discord server