CompletionKit MCP Server

https://completionkit.com/mcp Remote v0.28.13

Published by completionkit.com — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Prompt evals over MCP: run a prompt on your dataset, score each output 1-5 with an LLM judge.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Live
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Unconstrained URL/host parameter "url" on "datasets_create_from_url"MTC-CAP-007

Tool "datasets_create_from_url" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool datasets_create_from_url · inputSchema.properties.url

Tools 50

Each tool and what it can reach — enumerated from the running server.

  • datasets_create_from_urlingests untrusted input
  • agreements_createno sensitive capability
  • agreements_listno sensitive capability
  • datasets_createno sensitive capability
  • datasets_deleteno sensitive capability
  • datasets_getno sensitive capability
  • datasets_listno sensitive capability
  • datasets_updateno sensitive capability
  • judges_compareno sensitive capability
  • judges_replayno sensitive capability
Show 40 more tools ↓
  • metric_groups_createno sensitive capability
  • metric_groups_deleteno sensitive capability
  • metric_groups_getno sensitive capability
  • metric_groups_listno sensitive capability
  • metric_groups_updateno sensitive capability
  • metric_versions_dismissno sensitive capability
  • metric_versions_listno sensitive capability
  • metric_versions_publishno sensitive capability
  • metrics_createno sensitive capability
  • metrics_deleteno sensitive capability
  • metrics_getno sensitive capability
  • metrics_listno sensitive capability
  • metrics_suggest_variantsno sensitive capability
  • metrics_updateno sensitive capability
  • promptfoo_importno sensitive capability
  • prompts_createno sensitive capability
  • prompts_deleteno sensitive capability
  • prompts_getno sensitive capability
  • prompts_listno sensitive capability
  • prompts_publishno sensitive capability
  • prompts_suggest_improvementno sensitive capability
  • prompts_updateno sensitive capability
  • provider_credentials_createno sensitive capability
  • provider_credentials_deleteno sensitive capability
  • provider_credentials_getno sensitive capability
  • provider_credentials_listno sensitive capability
  • provider_credentials_updateno sensitive capability
  • responses_getno sensitive capability
  • responses_listno sensitive capability
  • runs_createno sensitive capability
  • runs_deleteno sensitive capability
  • runs_generateno sensitive capability
  • runs_getno sensitive capability
  • runs_listno sensitive capability
  • runs_updateno sensitive capability
  • tags_createno sensitive capability
  • tags_deleteno sensitive capability
  • tags_getno sensitive capability
  • tags_listno sensitive capability
  • tags_updateno sensitive capability

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.28.13 latest A 97/100 1 1.12.1 2026-07-28
v0.28.11 A 97/100 1 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/completionkit-com/badge.svg)](https://mcptrustchecker.com/registry/completionkit-com)
HTML
<a href="https://mcptrustchecker.com/registry/completionkit-com"><img src="https://mcptrustchecker.com/registry/completionkit-com/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/completionkit-com/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan https://completionkit.com/mcp --online

Use the free API → How scoring works

More in Data Science & ML