# conkurrence

Multi-model rating for AI evaluation: measures agreement among model raters (Fleiss' κ, Kendall's W) to find contested items for expert review. Agreement is reliability, not validity. Maintenance mode.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.5
- **Author:** JE Vectors LLC
- **License:** BUSL-1.1
- **npm:** conkurrence
- **Source:** https://github.com/AlligatorC0der/conkurrence
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-20T04:42:51.857Z
- **Version scanned:** 1.0.5
- **CVEs:** none found by OSV at scan time

## Tools

12 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `conkurrence_bedrock_health` — Test Bedrock model accessibility. Probes each model with a minimal invocation to verify IAM permissions and model enablement. Reports which models are accessibl
- `conkurrence_compare` — Compare two Conkurrence runs side-by-side. Shows κ deltas, per-field changes, classification shifts, and cost differences. Provide run_ids or inline results.
- `conkurrence_estimate` — Estimate the cost and token usage for a Conkurrence evaluation run before executing it.
- `conkurrence_license` — Manage your ConKurrence license. Actions: "validate" checks a license key against the API, "activate" stores a key for this MCP session, "status" shows current 
- `conkurrence_list_runs` — List all Conkurrence runs stored in the current session. Shows run_id, schema name, timestamp, overall kappa, item count, and cost for each run. Use run_ids wit
- `conkurrence_providers` — Check which AI provider API keys are configured. Reports availability of Bedrock (AWS credential chain), OpenAI (OPENAI_API_KEY), Gemini (GOOGLE_API_KEY or GEMI
- `conkurrence_report` — Generate a detailed markdown report from Conkurrence results. Provide either a run_id (from a previous conkurrence_run) or inline results.
- `conkurrence_run` — Execute a Conkurrence evaluation. If multiple model providers are configured, measures inter-rater consensus across models (Fleiss κ). If no API credentials are
- `conkurrence_suggest` — Analyze sample items and suggest an evaluation schema. Returns field suggestions with reliability estimates. Use before creating a schema to get AI-guided field
- `conkurrence_templates` — List available evaluation templates or get the full contents of a specific template. Templates include schema, sample data, and config files.
- `conkurrence_trend` — Analyze trends across multiple Conkurrence runs. Shows overall and per-field kappa progression, degradation alerts, schema evolution, and classification distrib
- `conkurrence_validate_schema` — Validate an evaluation schema for use with Conkurrence. Returns validation results including any errors or warnings.

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"conkurrence\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"conkurrence\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/conkurrence
- Install plan: https://forgeregistry.com/api/v1/packages/conkurrence/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/conkurrence
- HTML page: https://forgeregistry.com/registry/conkurrence
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.