Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Korpi API

NPM · @KORPIAI/API-MCP

MCP server for the Korpi API: every top AI video, image and text model behind one key and one bill.

Available components

+4 this week 71 Trust /100

Last scanned (9 hours ago)

Scores higher than 41% of npm servers

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency6
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 509 tokens (~101/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 76% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +4
    • Stability: unverified → 0.27 ▲ functional
  • 16 Oct 26 61

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed npm/@korpiai/api-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~412 tokens

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 →

Tool Tokens
generate_image ~76

Generate a paid image (charged per image from the API balance; see list_models). Returns the image URL when done.

NameTypeReqDescription
aspect_ratiostring––
image_urlsarray–Optional https reference images.
modelstring–Image model id from list_models.
promptstringyesWhat the image shows.

No output schema declared.

No examples provided.

generate_text ~93

Run a paid chat completion (charged per request from the API balance; see list_models). Pass a prompt, or a full messages array.

NameTypeReqDescription
max_tokensinteger––
messagesarray––
modelstring–Text model id from list_models.
promptstring–User message. Ignored when messages is set.
systemstring–Optional system message used with prompt.

No output schema declared.

No examples provided.

generate_video ~137

Start a paid video generation (charged per second from the API balance; see list_models). Returns a job id. Poll get_job_status until status is completed or failed. Do not resubmit after a timeout: the first job may already be running.

NameTypeReqDescription
aspect_ratiostring––
durationinteger–Length in seconds.
image_urlstring–Optional https URL of a start image.
modelstring–Video model id from list_models.
promptstringyesWhat happens in the video.
wait_secondsinteger–Wait up to this many seconds for the video to finish before returning.

No output schema declared.

No examples provided.

get_job_status ~52

Check a video job started with generate_video. Returns status (queued, in_progress, completed or failed) and the video URL once completed. Free.

NameTypeReqDescription
idstringyesJob id returned by generate_video.

No output schema declared.

No examples provided.

list_models ~54

List the Korpi API models with their ids, type (video, image or text), options and current per-use price in USD. Free; no key needed.

NameTypeReqDescription
typestring–Only return models of this type.

No output schema declared.

No examples provided.

Install

How do I install the Korpi API MCP server?

Korpi API runs locally as an npm package, launched with npx -y @korpiai/api-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @korpiai/api-mcp

# add to Claude Code
claude mcp add reksely-korpi-api-mcp -- npx -y @korpiai/api-mcp
Common questions

What is the Korpi API MCP server?

Korpi API is an MCP server listed in the public MCP registry as io.github.Reksely/korpi-api-mcp. MCP server for the Korpi API: every top AI video, image and text model behind one key and one bill. This page covers its npm package (@korpiai/api-mcp).

Is the Korpi API MCP server safe to use?

Korpi API scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Korpi API MCP server expose?

Korpi API exposes 5 tools: list_models, generate_video, generate_image, generate_text, get_job_status. Their descriptions and schemas cost roughly 412 tokens of context every time the server is loaded.

Is the Korpi API MCP server still maintained?

Korpi API is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Korpi API MCP server?

VerifyMCP ran 15 checks on Korpi API, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Korpi API: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.