CompletionKit
REMOTE · COMPLETIONKIT.COM · SCANNED SEP 22
Prompt evals over MCP: run a prompt on your dataset, score each output 1-5 with an LLM judge.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 3722 tokens (~68/item across 54 items; 54 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 18% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "prompts_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 54 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the CompletionKit MCP server?
CompletionKit is a hosted endpoint at https://completionkit.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · completionkit.com
claude mcp add --transport http com-completionkit-evals 'https://completionkit.com/mcp'
{
"mcpServers": {
"com-completionkit-evals": {
"url": "https://completionkit.com/mcp"
}
}
} {
"servers": {
"com-completionkit-evals": {
"type": "http",
"url": "https://completionkit.com/mcp"
}
}
} [mcp_servers.com-completionkit-evals] url = "https://completionkit.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-completionkit-evals": {
"type": "remote",
"url": "https://completionkit.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-completionkit-evals --url 'https://completionkit.com/mcp' --transport streamable-http
mcp_servers:
com-completionkit-evals:
url: "https://completionkit.com/mcp" {
"McpServers": {
"com-completionkit-evals": {
"Transport": "http",
"Url": "https://completionkit.com/mcp"
}
}
} assistant mcp add com-completionkit-evals -t streamable-http -u 'https://completionkit.com/mcp'
{
"mcpServers": {
"com-completionkit-evals": {
"type": "http",
"url": "https://completionkit.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Sept 26 0
- Server version: 0.28.42 → 0.28.43 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 13 Aug 26 0
- Server version: 0.28.38 → 0.28.42 functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Aug 26 0
- Schema quality: good → excellent functional
- Server version: 0.28.32 → 0.28.38 functional
- “runs_create” reworded the description of “temperature” cosmetic
- “runs_update” reworded the description of “temperature” cosmetic
- 5 Aug 26 0
- Tool “responses_list” rewrote its description, which is the text the model reads security
- Tool “runs_get” rewrote its description, which is the text the model reads security
- Schema quality: 55 → 66 ▼ functional
- Tool coverage: 9% → 18% ▲ functional
- Server version: 0.28.23 → 0.28.32 functional
- “responses_list” added an optional parameter “fields” cosmetic
- “responses_list” added an optional parameter “limit” cosmetic
- “responses_list” added an optional parameter “max_score” cosmetic
- “responses_list” added an optional parameter “min_score” cosmetic
- “responses_list” added an optional parameter “offset” cosmetic
- “responses_list” added an optional parameter “sort” cosmetic
- “responses_list” added an optional parameter “status” cosmetic
- “runs_create” added an optional parameter “judge_temperature” cosmetic
- “runs_create” added an optional parameter “max_tokens” cosmetic
- “runs_create” added an optional parameter “temperature” cosmetic
- “runs_update” added an optional parameter “judge_temperature” cosmetic
- “runs_update” added an optional parameter “max_tokens” cosmetic
- “runs_update” added an optional parameter “temperature” cosmetic
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://completionkit.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=completionkit.com | CN=WE1,O=Google Trust Services,C=US | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 8c895e8b03c0565313adae43e3e790ee |
| SANs: completionkit.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of completionkit.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| completionkit.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31556952; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://completionkit.com/mcp | Verified | 200 | |
| http (plaintext) | http://completionkit.com/mcp | HTTPS enforced | 301 | https://completionkit.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agreements_create ~103
Upsert an agreement for (run, response, metric, created_by). Verdict is one of agree, disagree, borderline. corrected_score (1..5) is required when verdict is 'disagree'.
| Name | Type | Req | Description |
|---|---|---|---|
| corrected_score | number | – | – |
| created_by | string | – | – |
| metric_id | integer | yes | – |
| note | string | – | – |
| response_id | integer | yes | – |
| run_id | integer | yes | – |
| verdict | string | yes | – |
No output schema declared.
No examples provided.
agreements_list ~58
List agreements. Filter by run_id, response_id, metric_id, or created_by.
| Name | Type | Req | Description |
|---|---|---|---|
| created_by | string | – | – |
| metric_id | integer | – | – |
| response_id | integer | – | – |
| run_id | integer | – | – |
No output schema declared.
No examples provided.
datasets_create ~124
Create a dataset with CSV data. First row is the header. Two column names are recognized specially: "expected_output" is each row's answer key (ground truth) given to the judge and to checks that compare against the row's expected value, and "actual_output" is a pre-made output to score in a prompt-less run. Both are overridable per run (expected_column / output_column). Every column is also available to the prompt as a variable.
| Name | Type | Req | Description |
|---|---|---|---|
| csv_data | string | yes | – |
| name | string | yes | – |
| tag_names | array | – | – |
No output schema declared.
No examples provided.
datasets_create_from_url ~145
Create a dataset by downloading CSV from a URL instead of inlining it. Use this for large datasets: pass a public http(s) URL and the server fetches the CSV directly, so the data never has to pass through the tool-call arguments. The URL is SSRF-checked and the download is capped at 10MB. First row is the header; the "expected_output" (answer key) and "actual_output" (pre-made output) columns are recognized specially, overridable per run.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| tag_names | array | – | – |
| url | string | yes | Public http(s) URL of the CSV file to download. |
No output schema declared.
No examples provided.
datasets_delete ~19
Delete a dataset
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
datasets_get ~21
Get a dataset by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
datasets_list ~12
List all datasets
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
datasets_update ~42
Update a dataset
| Name | Type | Req | Description |
|---|---|---|---|
| csv_data | string | – | – |
| id | integer | yes | – |
| name | string | – | – |
| tag_names | array | – | – |
No output schema declared.
No examples provided.
judges_compare ~78
Compare two versions of one metric's agreement stats side by side. Requires metric_id, metric_version_a_id, and metric_version_b_id (both versions must belong to that metric). Unavailable for check metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| metric_id | integer | yes | – |
| metric_version_a_id | integer | yes | – |
| metric_version_b_id | integer | yes | – |
No output schema declared.
No examples provided.
judges_replay ~115
Create a scoring run for the current judge over a dataset's existing outputs (wraps runs_create with prompt_id omitted and output_column supplied). This only sets up the run; call runs_generate to actually re-judge the outputs so you can compare against human verdicts.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | integer | yes | – |
| judge_model | string | yes | – |
| metric_id | integer | yes | – |
| name | string | yes | – |
| output_column | string | – | Dataset column with the existing outputs to grade. Defaults to actual_output. |
No output schema declared.
No examples provided.
metric_groups_create ~44
Create a metric group
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| metric_ids | array | – | – |
| name | string | yes | – |
| tag_names | array | – | – |
No output schema declared.
No examples provided.
metric_groups_delete ~21
Delete a metric group
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
metric_groups_get ~23
Get a metric group by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
metric_groups_list ~14
List all metric groups
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
metric_groups_update ~51
Update a metric group
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| id | integer | yes | – |
| metric_ids | array | – | – |
| name | string | – | – |
| tag_names | array | – | – |
No output schema declared.
No examples provided.
metric_versions_dismiss ~60
Destroy a draft MetricVersion (use for either source: 'edit' or source: 'suggestion'). Published versions are refused — to demote a published version, publish a different one as current instead.
| Name | Type | Req | Description |
|---|---|---|---|
| metric_version_id | integer | yes | – |
No output schema declared.
No examples provided.
metric_versions_list ~50
List every MetricVersion (drafts + published) for a metric, newest first. Each row carries version_number, state, source, current flag, and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| metric_id | integer | yes | – |
No output schema declared.
No examples provided.
metric_versions_publish ~80
Publish a MetricVersion as the live version of its metric. Works for both 'draft → published' and 'revert to an older published version → current'. Transactionally flips current, demotes peers, and writes the version's instruction + rubric_bands back onto the metric so the judge grades against it.
| Name | Type | Req | Description |
|---|---|---|---|
| metric_version_id | integer | yes | – |
No output schema declared.
No examples provided.
metrics_create ~178
Create a metric with evaluation criteria. For a deterministic check set metric_type:"check" and check_config. Per-kind required keys: value (contains/not_contains/equals), pattern (regex), json_path+expected (json_path_equals), min and/or max (length_bounds); valid_json takes no extra keys. target_path is required when target is json_path. For contains, not_contains, and equals, set compare_to:"expected" to grade against each row's own expected_output (ground truth) instead of a constant value (drop value); add expected_path to dig into the expected value when it is JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| check_config | object | – | – |
| instruction | string | – | – |
| metric_type | string | – | – |
| name | string | yes | – |
| rubric_bands | array | – | – |
| tag_names | array | – | – |
No output schema declared.
No examples provided.
metrics_delete ~19
Delete a metric
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
metrics_get ~21
Get a metric by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
metrics_list ~12
List all metrics
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
metrics_suggest_variants ~134
Ask the model to rewrite the metric's judge instruction in N variants targeted at the recent disagreements. Each variant is saved as a draft MetricVersion with source="suggestion". Returns the persisted drafts. Stripe-metering hooks fire via ActiveSupport::Notifications under completion_kit.judge_suggestion.generated.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many variants to request (default 1, max 3). One focused rewrite beats five reworded copies. |
| metric_id | integer | yes | – |
| model | string | – | Override the model used to generate variants. Defaults to the configured judge model or an available judging model. |
No output schema declared.
No examples provided.
metrics_update ~182
Update a metric. For a deterministic check set metric_type:"check" and check_config. Per-kind required keys: value (contains/not_contains/equals), pattern (regex), json_path+expected (json_path_equals), min and/or max (length_bounds); valid_json takes no extra keys. target_path is required when target is json_path. For contains, not_contains, and equals, set compare_to:"expected" to grade against each row's own expected_output (ground truth) instead of a constant value (drop value); add expected_path to dig into the expected value when it is JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| check_config | object | – | – |
| id | integer | yes | – |
| instruction | string | – | – |
| metric_type | string | – | – |
| name | string | – | – |
| rubric_bands | array | – | – |
| tag_names | array | – | – |
No output schema declared.
No examples provided.
promptfoo_import ~92
Import a promptfooconfig.yaml. Creates a prompt, a dataset from the test vars, and metrics from the assert blocks (llm-rubric/g-eval become judge metrics; contains/equals/regex/is-json become deterministic check metrics). Returns a summary of what mapped and what was skipped and why; nothing is dropped silently.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | yes | The full promptfooconfig.yaml contents. |
No output schema declared.
No examples provided.
prompts_create ~50
Create a prompt
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| llm_model | string | yes | – |
| name | string | yes | – |
| tag_names | array | – | – |
| template | string | yes | – |
No output schema declared.
No examples provided.
prompts_delete ~19
Delete a prompt
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
prompts_get ~23
Get a prompt by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Prompt ID |
No output schema declared.
No examples provided.
prompts_list ~12
List all prompts
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prompts_publish ~26
Publish a prompt version, making it the current version
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
prompts_suggest_improvement ~94
Suggest an improved version of a prompt, grounded in a run's test results and judge feedback. Analyzes the run's responses, scores, and reviews, then returns reasoning plus a rewritten template (preserving {{variables}}) and persists it as a Suggestion. Requires a run that has a prompt (not a scoring-only run).
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | integer | yes | The run whose results ground the improvement. |
No output schema declared.
No examples provided.
prompts_update ~113
Update a prompt. If the prompt already has runs, this creates a new DRAFT version (current=false) rather than editing in place or publishing — promote it with prompts_publish — so an agent's edits don't go live without a gate. If it has no runs, it is updated in place.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| id | integer | yes | – |
| llm_model | string | – | – |
| name | string | – | – |
| tag_names | array | – | – |
| template | string | – | – |
No output schema declared.
No examples provided.
provider_credentials_create ~45
Create a provider credential
| Name | Type | Req | Description |
|---|---|---|---|
| api_endpoint | string | – | – |
| api_key | string | yes | – |
| api_version | string | – | – |
| provider | string | yes | – |
No output schema declared.
No examples provided.
provider_credentials_delete ~21
Delete a provider credential
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
provider_credentials_get ~29
Get a provider credential by ID (API key is not exposed)
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
provider_credentials_list ~20
List all provider credentials (API keys are not exposed)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
provider_credentials_update ~52
Update a provider credential
| Name | Type | Req | Description |
|---|---|---|---|
| api_endpoint | string | – | – |
| api_key | string | – | – |
| api_version | string | – | – |
| id | integer | yes | – |
| provider | string | – | – |
No output schema declared.
No examples provided.
responses_get ~28
Get a specific response
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
| run_id | integer | yes | – |
No output schema declared.
No examples provided.
responses_list ~303
List responses for a run, in row order. Returns {total, limit, offset, returned, responses}. Defaults to 50 rows because full payloads are large: use "fields" to drop the bodies, "min_score"/"max_score" to isolate low scorers, and sort "score_asc" to read the worst rows first. For per-metric averages of the whole run use runs_get instead of aggregating here.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Only return these keys, keeping the payload small. Response keys: id, run_id, input_data, response_text, expected_output, created_at, score, reviewed, reviews, status, attempts, row_index, error. Pre… |
| limit | integer | – | Rows to return; defaults to 50, capped at 500. |
| max_score | number | – | Only rows whose average judge score is at most this. Use with sort "score_asc" for failure-mode analysis. |
| min_score | number | – | Only rows whose average judge score is at least this. |
| offset | integer | – | Rows to skip before returning results. |
| run_id | integer | yes | – |
| sort | string | – | Row order; defaults to "id". |
| status | string | – | Filter by row status: pending, retrying, succeeded or failed. |
No output schema declared.
No examples provided.
runs_create ~382
Create a run. Omit prompt_id and provide output_column to score existing outputs by grading a pre-existing dataset column instead of generating new ones.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | integer | – | – |
| expected_column | string | – | Dataset column holding each row's answer key / ground truth, graded by checks with compare_to "expected" and passed to the judge; defaults to "expected_output". |
| judge_model | string | – | – |
| judge_temperature | number | – | Sampling temperature for the judge, 0 to 1. Defaults to 0 so re-judging the same output gives the same score. Raise it only to measure judge variance on purpose; any value above 0 makes the run's sco… |
| max_tokens | integer | – | Cap on generated tokens per row. Leave unset to use the provider client's default, which is what silently truncates long outputs and makes the judge score malformed JSON. Set it to whatever the promp… |
| metric_group_id | integer | – | Attach the metrics belonging to this metric group (its current metric_ids). Ignored when metric_ids is also given. |
| metric_ids | array | – | – |
| name | string | yes | – |
| output_column | string | – | Dataset column to grade when prompt_id is omitted; defaults to "actual_output". |
| prompt_id | integer | – | – |
| tag_names | array | – | – |
| temperature | number | – | Sampling temperature for generation, 0 to 1. Leave it unset, which is the default, and no temperature is sent at all, so the model applies its own. Most current frontier models refuse the parameter o… |
No output schema declared.
No examples provided.
runs_delete ~19
Delete a run
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
runs_generate ~52
Start a run. Required for every run, including score-only runs (no prompt): generates responses with the prompt when there is one, otherwise copies the graded dataset column and grades it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
runs_get ~72
Get a run by ID, including "metric_averages": a per-metric breakdown with each metric's average score (or pass rate for checks), how many rows it graded, and how many scored low. Use this to find the metric dragging a prompt down without listing responses.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
runs_list ~12
List all runs
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
runs_regrade ~45
Re-grade a run's existing responses with its currently attached metrics, without regenerating. Use after attaching or editing metrics on an already-generated run.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
runs_rerun ~54
Create and start a fresh copy of a run with the same prompt, dataset, metrics, and settings. Use when the judge changed and you want a clean run instead of mixing versions.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
runs_retry_failures ~44
Re-run only the failed responses of a run, optionally limited to specific response ids via "only".
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
| only | array | – | – |
No output schema declared.
No examples provided.
runs_update ~308
Update a run
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | integer | – | – |
| expected_column | string | – | – |
| id | integer | yes | – |
| judge_model | string | – | – |
| judge_temperature | number | – | Sampling temperature for the judge, 0 to 1. Defaults to 0 so re-judging the same output gives the same score. Raise it only to measure judge variance on purpose; any value above 0 makes the run's sco… |
| max_tokens | integer | – | Cap on generated tokens per row. Leave unset to use the provider client's default, which is what silently truncates long outputs and makes the judge score malformed JSON. Set it to whatever the promp… |
| metric_group_id | integer | – | Replace the run's metrics with those belonging to this metric group. Ignored when metric_ids is also given. |
| metric_ids | array | – | – |
| name | string | – | – |
| output_column | string | – | – |
| tag_names | array | – | – |
| temperature | number | – | Sampling temperature for generation, 0 to 1. Leave it unset, which is the default, and no temperature is sent at all, so the model applies its own. Most current frontier models refuse the parameter o… |
No output schema declared.
No examples provided.
tags_create ~25
Create a tag. Color is auto-assigned.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
tags_delete ~34
Delete a tag. Removes the tag from every linked metric, prompt, run, and dataset.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
What is the CompletionKit MCP server?
CompletionKit is an MCP server listed in the public MCP registry as com.completionkit/evals. Prompt evals over MCP: run a prompt on your dataset, score each output 1-5 with an LLM judge. This page covers its hosted endpoint (https://completionkit.com/mcp).
Is the CompletionKit MCP server safe to use?
CompletionKit scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CompletionKit MCP server expose?
CompletionKit exposes 54 tools: prompts_list, prompts_get, prompts_create, prompts_update, prompts_delete, and 49 more. Their descriptions and schemas cost roughly 3,722 tokens of context every time the server is loaded.
Does the CompletionKit MCP server require authentication?
Yes. CompletionKit asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the CompletionKit MCP server still maintained?
CompletionKit is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.