Evidra
LocalAbout Evidra
Evidra — Flight recorder for AI infrastructure agents
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
docker run -i --rm -e EVIDRA_ENVIRONMENT -e EVIDRA_EVIDENCE_DIR -e EVIDRA_SIGNING_MODE -e EVIDRA_SIGNING_KEY -e EVIDRA_SIGNING_KEY_PATH ghcr.io/vitas/evidra-mcp:0.4.7EVIDRA_ENVIRONMENTEnvironment label (production, staging, development)EVIDRA_EVIDENCE_DIRDirectory for evidence JSONL storageEVIDRA_SIGNING_MODESigning mode: strict (default) or optional (ephemeral local mode)EVIDRA_SIGNING_KEYSecretBase64-encoded Ed25519 private key (required for strict mode)EVIDRA_SIGNING_KEY_PATHSecretPath to PEM-encoded Ed25519 private key (required for strict mode if key not inline)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
ghcr.io/vitas/evidra-mcp:0.4.7stdioTools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.