mcp-evidence
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 | Launches a Chromium browser context with video and trace recording enabled, and creates an evidence directory under |
| navigateA | Navigates the session's page to a URL. If the URL is relative, it resolves against the session's baseUrl. |
| clickA | Clicks an element, located either by CSS/text |
| fillB | Fills a form field located by CSS selector with the given value. |
| wait_forB | Waits for an element (located by CSS |
| screenshotB | Takes a screenshot and saves it immediately into the evidence directory, so it survives even if the session later errors. |
| finish_evidence_sessionA | Closes the browser context (finalizing the video), stops tracing, writes manifest.json, 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 7 tools
Each tool has a distinct purpose: session management (start/finish), navigation, page interaction (click/fill/wait), and evidence capture (screenshot). No overlap in functionality.
All tools use snake_case with a verb_noun pattern (e.g., start_evidence_session, finish_evidence_session, wait_for), and the naming is clear and predictable.
Seven tools cover the essential workflow for evidence gathering without being excessive or insufficient. Each tool earns its place.
The set covers the full lifecycle: launch, navigate, interact (click, fill, wait), capture (screenshot), and finalize. Minor omissions like scroll or keyboard input are not critical for the primary use case.