MCP server for kensa, the open source agent evals harness
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"kensa-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# kensa-mcp MCP (Model Context Protocol) server for [kensa](https://github.com/satyaborg/kensa), the open source agent evals harness. This is a thin shim around `kensa[mcp]` so you can run the server with a single command: ```bash uvx kensa-mcp ``` Or register it with Claude Code in one line: ```bash claude mcp add kensa -- uvx kensa-mcp ``` The server exposes kensa's eval workflow (`init`, `doctor`, `run`, `judge`, `eval`, `report`, `analyze`) as MCP tools, and run artefacts as resources under `kensa://`. See the [MCP server docs](https://kensa.sh/docs/mcp-server) for the full reference. ## Relationship to kensa `kensa-mcp` depends on `kensa[mcp]` pinned to the same version. Installing `kensa-mcp` pulls in all of kensa. If you already have kensa in your project, you can also run the server via `kensa mcp` (the CLI subcommand) without installing this package. ## License MIT.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.