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.

Koma Core MCP

NPM · KOMA-CORE-MCP · SCANNED AUG 17

Protected RAG storage — agents discover public metadata, content only by access token.

Available components

70 Trust /100
Trust breakdown (6 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 →

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
  • 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 180 tokens (~90/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · koma-core-mcp

# add to Claude Code
claude mcp add swnotmetal-koma-core-mcp -- npx -y koma-core-mcp
# add to Codex CLI
codex mcp add swnotmetal-koma-core-mcp -- npx -y koma-core-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "swnotmetal-koma-core-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "koma-core-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add swnotmetal-koma-core-mcp --command npx --arg -y --arg koma-core-mcp
# ~/.hermes/config.yaml
mcp_servers:
  swnotmetal-koma-core-mcp:
    command: "npx"
    args: ["-y", "koma-core-mcp"]
// mcp.json
{
  "mcpServers": {
    "swnotmetal-koma-core-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "koma-core-mcp"
      ]
    }
  }
}
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.

  • 15 Aug 26 70

    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 17 Aug 2026 · Analysed npm/koma-core-mcp@0.1.1

Provenance No attestation

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

Result No attestation
Ecosystem npm
Dependencies 4 packages
Packages resolved 4
Tree resolution Complete
MCP tools · 2 exposed · ~180 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.

Tool Tokens
retrieve_doc ~77

Retrieve the full content of a document by its source ID. Requires the user to have an access tier at or above the document's tier (public < premium < enterprise). Access is denied otherwise.

NameTypeReqDescription
sourceIdstringyesThe document source ID (returned by search_docs)
userTierstringyesThe authenticated user's access tier

No output schema declared.

No examples provided.

search_docs ~103

Search the public document index. Returns metadata (display name, category, tags, summary) — NOT the full content. Use retrieve_doc to read the actual content of a document you are authorized to access.

NameTypeReqDescription
categorystringFilter by category (e.g. "docs", "internal")
limitnumberMaximum results to return. Default: 20
tagstringFilter by tag (e.g. "api", "guide")

No output schema declared.

No examples provided.