MCP.Market

Koma Core MCP server

by swnotmetal·io.github.swnotmetal/koma-core-mcp·v0.1.1·13 stars

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

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

13 stars74 downloads/wk

Reviews

Write one

Nobody has reviewed Koma Core MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Koma Core MCP tools (2)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • retrieve_doc

    Retrieve the full content of a document by its source ID. Requires the user to have an access tier

  • search_docs

    Search the public document index. Returns metadata (display name, category, tags, summary) — NOT the full content.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 22 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Koma Core MCP compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 68% of 4,460 AI and agents servers
Tools
2
the typical AI and agents server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
13
more than 86% of 2,711 AI and agents servers
Downloads a week
74
more than 56% of 1,538 AI and agents servers with a package

What its tools let an agent do: 2 read

Install Koma Core MCP in Claude Code, Cursor or VS Code

Runs npx -y koma-core-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add koma-core-mcp -- npx -y koma-core-mcp
Add to Cursor

What the publisher says

From the Koma Core MCP repository's README, as published. We do not edit it. Read it on GitHub

Koma

Miko: required Skill checks for Claude Code and Codex

Keep reminding your coding agent to read a required Skill before editing? Miko checks for observable Skill reads before protected edits. When evidence is missing, it pauses the action and tells the agent what to load before retrying. It runs locally, makes no LLM calls, and is free and open source.

The current focus is Claude Code and Codex CLI. Miko is part of Koma; the separate Gate, Scout, and Core packages cover AI application input, request limits, and retrieval. You do not need them to use Miko.

npm install -D koma-miko@alpha
npx koma-miko init --host claude

Edit the generated miko.json to name your project's Skills and protected paths, then start a new Claude Code session. Using Codex? Follow the Codex setup and one-time Hook review. Codex CLI is a Technical Preview; Desktop requires prior CLI activation.

中文版

▶ Try Miko's guided terminal replay — plus Gate, Scout & Core, no signup.

Miko for Claude Code and Codex

Coding agents can say they loaded a required Skill or ran a test. Miko does not treat that claim as evidence. At supported local host Hooks, it compares observed Skill loads, reference reads, tool actions, and completion checks with a project-owned miko.json.

If an agent tries to edit before satisfying the spec, Miko can return a denial and a short recovery instruction. It cannot inspect hidden model context, prove that a model understood a Skill, or verify events the host never exposes. In Claude CLI guided mode, a genuine scope exception opens one visible Miko choice: allow that exact retry once, or keep the current boundary.

npx --yes koma-miko@alpha demo       # deterministic; no API key
npx --yes koma-miko@alpha probe --host claude  # isolated adapter check; no model
npx koma-miko init --host claude     # after local installation

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Koma Core MCP: common questions

Is Koma Core MCP server safe?
Mostly: it is graded B (83/100). Read the Koma Core MCP safety report
How do I install Koma Core MCP?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Koma Core MCP need an API key?
Yes. The registry entry asks for KOMA_MASTER_KEY.
Is Koma Core MCP maintained?
The last commit was 22 days ago (2026-10-13). The latest release is v0.1.1.
What can I use instead of Koma Core MCP?
Servers from other publishers that do the same job: Butterbase AI MCP server, Spotifyscraper MCP server and three.ws Marketplace MCP server. Compare all Koma Core MCP alternatives.
How does Koma Core MCP compare with other AI and agents MCP servers?
safety score 83/100 (higher than 68% of 4,460 AI and agents servers); tools 2 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Koma Core MCP

Same job from other publishers: the closest match first, then the best rated.

All Koma Core MCP alternatives →
  • Butterbase AI
    Butterbase MCP server — manage your backend: schemas, auth, functions, storage, RAG, deploys.
    A
  • Spotifyscraper
    Public Spotify metadata, lyrics and podcasts for LLM agents. No API key, read-only.
    B
  • three.ws Marketplace
    Browse and discover the public three.ws agent marketplace and skills catalog. Read-only.
    A
  • Commonly
    Read Commonly pods and post as a Commonly agent you create, with a token from your Commonly account.
    A
  • Local Rag
    Easy-to-setup local RAG server with minimal configuration
    A