Mmcp.market

Shield Kya MCP server

by The-Pixel-Boys·io.github.The-Pixel-Boys/shield-kya·v0.1.29
No reviews yet

KYA MCP gate: evaluate, ingest, request approval. Sole PEP is Shield.

B77/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
Growing

1 stars1.3k downloads/wk

Reviews

Write one

Nobody has reviewed Shield Kya yet.

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

Shield Kya tools (3)

write = sends, deletes, buys or posts

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

  • kya.policy_evaluate

    Evaluate ALLOW | DENY | REQUIRE_APPROVE for an agent action at the tool boundary. Sole PEP is Shield KYA; missing APPROVED means no irreversible side effect.

  • kya.request_approval

    Open a human approval request for a high-stakes side effect. Does not execute the side effect.

  • kya.session_ingest

    Ingest an AgentEvent-compatible session observation for raise-only risk. Risk may only raise severity, never auto-ALLOW.

Public scan report

scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it

1 medium
  • Code scan96 source files scanned20/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 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Findings (1)

  • mediumeval / new Function usedexec.eval
    .cursor-plugin/plugin.json: …ription": "Know Your Agent: fail-closed eval (ALLOW | DENY | REQUIRE_APPROVE), dual-pl…
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the Shield Kya repository's README, as published. We do not edit it. Read it on GitHub

@shield-agent/kya

Gate agent tool calls (Allow / Review / Deny) before they write or deploy. Local activity receipt included. Free forever under MIT.

npm i -g @shield-agent/kya@latest && kya start

Requires Node.js 24+. Restart Cursor / Claude Code / Codex once so MCP loads. Hosted desk: shield-agent.com.

CLI and local MCP gate for Shield’s Know Your Agent path.

If an agent can change a real system, it has to ask Shield first. You register the agent, wrap the tool, and get Allow, Review, or Deny. Review waits for a person. This package does not scan your network. Agents that never call evaluate stay invisible on purpose.

Walkthrough: how you use it.

npx @shield-agent/kya@latest --help

Requires Node.js 24+ (engines.node: >=24). On an older Node the CLI offers to install 24 for you (via volta / fnm / nvm / brew), reinstall itself, and finish the command — declining just prints a warning and continues.

It works with any host that speaks MCP or OpenAPI. Vertical packs are optional. Shield is the only policy decision point: this gate never auto-approves an irreversible side effect.

If KYAAPIKEY is empty against an authenticated plane, network commands exit non-zero. eval-tool, wrap, and invoke exit 0 on ALLOW, 4 on REQUIRE_APPROVE, and 1 on DENY or unknown, so a line like eval-tool && write cannot skip the gate.

--offline runs sample evaluate without a paid cloud (useful for DENY and REQUIREAPPROVE demos). Creating an agent is itself a tool: offline, kya.agent.register comes back REQUIREAPPROVE. Allow, break-glass, and approve mint modes live on the control plane.

One liner

npm i -g @shield-agent/kya@latest && kya start

Run it in your project directory. (From a clone of this repo, ./scripts/install-local.sh replaces the npm install.)

That inits .kya/, wires local MCP (.mcp.json, mcp.json, .cursor/mcp.json → kya serve-mcp --stdio), also wires user-level configs for every installed host it detects (~/.claude.json, ~/.kimi-code/, ~/.grok/, ~/.cursor/, …), and opens the live activity report. The report runs in the background — you get your terminal back; kya stop stops it, kya receipt --open reopens it. Cursor, Kiro, Qwen, Amp, Droid, Cline, and Grok pick the server up live with no restart (Kimi: just a new session); Claude Code, Codex, OpenCode, Gemini, Copilot CLI, and Kilo CLI load it on next launch — claude --resume keeps your conversation.

<!-- Local path kept in package for offline viewers: assets/activity-receipt.png -->

kya start --no-open   # wire only
kya start --force     # rewrite MCP blocks
# Receipt change previews (clipped + redacted): on by default for writes
# KYA_DIFF_PREVIEW=0 to disable

One command per host

Shortened. The full README is on GitHub.

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

Install directly

Runs npx -y @shield-agent/kya on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add shield-kya -- npx -y @shield-agent/kya
Add to Cursor

Shield Kya: common questions

Is Shield Kya MCP server safe?
Mostly: it is graded B (77/100). Read the Shield Kya safety report
How do I install Shield Kya?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Shield Kya need an API key?
Yes. The registry entry asks for KYA_API_KEY.
Is Shield Kya maintained?
The last commit was 3 days ago (2026-09-17). The latest release is v0.1.29.

More from The-Pixel-Boys →