A
licenseNot graded
qualityB
maintenanceEnables assistants to inspect tamper-evident AI agent action journals through read-only verification, event querying, and policy-rule explanation.
62 PyPI
1
Apache 2.0
io.github.loopg/pramana-mcp
by reliai-in
Related Servers
Alternatives to io.github.loopg/pramana-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceCaptures AI agent runs and turns them into tamper-evident execution records showing tool use, timing, failures, recoveries, and human interventions. Records can be inspected, exported, and verified offline.MIT
- AlicenseAqualityAmaintenanceProvides read-only tools to generate test plans for AI agents, score agent runs, and produce reusable evaluation scorecards.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access observability and evaluation data, including run history, span traces, LLM-as-judge evaluation results, and regression reports.MIT
- AlicenseNot gradedqualityAmaintenanceRead-only local MCP server for inspecting AgentInspect TypeScript AI-agent traces. Lists runs, exposes bounded causal-failure and TraceFacts evidence, evaluates TraceContract checks, compares runs, and creates share-checked evidence without mutating traces or invoking agent tools.14,150 npm638MIT
- AlicenseCqualityBmaintenanceEnables deterministic, read-only multimodal evidence review by normalizing text, tables, PDFs, images, and screenshots into provenance metadata, with optional controlled filesystem access and no provider calls.1MIT
TDQS
A3.5/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: two list/get pairs for traces and model diffs, plus an independent offline verification tool. There is no overlap between listing, retrieving, and verifying operations, so misselection is unlikely.
Naming Consistency5/5
All five names follow a consistent snake_case verb_noun pattern (list_traces, get_trace, list_model_diffs, get_model_diff, verify_bundle). The list/get pairing is symmetric and predictable across both resources.
Tool Count5/5
Five tools is well-scoped for an observability/inspection server with two resources plus a verification utility. Each tool earns its place with no redundant entries.
Completeness4/5
The list/get pairs cover discovery and detail for traces and diffs, and verify_bundle handles the evidence-checking lifecycle, so read workflows are complete. Minor gaps exist (e.g. no trace export or diff-creation trigger), but these are workable given the inspection-focused scope.
Maintenance
ActivityMaintained
ResponsivenessNo issues