ConKurrence is a statistically validated consensus measurement toolkit for AI evaluation pipelines. It uses multiple AI models as independent raters
Conkurrence MCP server exists for a simple reason — assistants are far more useful when they can act on Conkurrence directly instead of describing what you should do. ConKurrence is a statistically validated consensus measurement toolkit for AI evaluation pipelines. It uses multiple AI models as independent raters, measures inter-rater reliability with Fleiss' kappa and bootstrap confidence intervals.
Once Conkurrence is connected, these are the calls the assistant has available:
conkurrence_run — Execute an evaluation across multiple AI ratersconkurrence_report — Generate a detailed markdown reportconkurrence_compare — Side-by-side comparison of two runsconkurrence_trend — Track agreement over multiple runsconkurrence_suggest — AI-powered schema suggestion from your dataconkurrence_validate_schema — Validate a schema before runningconkurrence_estimate — Estimate cost and token usageconkurrence on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Conkurrence's toolset — conkurrence_run, conkurrence_report, conkurrence_compare and 4 more — is a fair guide to whether it matches your workflow. It is maintained by alligatorc0der; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| conkurrence_run | Execute an evaluation across multiple AI raters |
| conkurrence_report | Generate a detailed markdown report |
| conkurrence_compare | Side-by-side comparison of two runs |
| conkurrence_trend | Track agreement over multiple runs |
| conkurrence_suggest | AI-powered schema suggestion from your data |
| conkurrence_validate_schema | Validate a schema before running |
| conkurrence_estimate | Estimate cost and token usage |
{
"mcpServers": {
"conkurrence": {
"command": "npx",
"args": ["-y", "conkurrence"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.