Shield Kya runs on your own machine — the client starts it, so there is no endpoint to ping. 1 179 installs a week from npm. Last commit 5 Nov 2026.
Audit trail and traceability for AI agents. MCP gate: evaluate, ingest, request approval.
What the code does
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
// Directory forms end with `(\/|$)`: normalizePath drops a trailing slash, and `cp x ~/Library/LaunchAgents/` writes inside.
const child = spawn(process.execPath, [cli, "serve-mcp", "--stdio"], {
proc = subprocess.run(
"https://hooks.slack.com/services/[redacted]",
# Pipelines mounts the repository at /opt/atlassian/pipelines/agent/build. # Run as root so the pipe can write KYA reports back to the workspace. USER root
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add shield-kya -e 'KYA_BASE_URL=<KYA_BASE_URL>' -e 'KYA_API_KEY=<KYA_API_KEY>' -- npx -y @shield-agent/kya{
"mcpServers": {
"shield-kya": {
"command": "npx",
"args": [
"-y",
"@shield-agent/kya"
],
"env": {
"KYA_API_KEY": "<KYA_API_KEY>",
"KYA_BASE_URL": "<KYA_BASE_URL>"
}
}
}
}[mcp_servers.shield-kya]
command = "npx"
args = ["-y", "@shield-agent/kya"]
env = { KYA_BASE_URL = "<KYA_BASE_URL>", KYA_API_KEY = "<KYA_API_KEY>" }{
"mcpServers": {
"shield-kya": {
"command": "npx",
"args": [
"-y",
"@shield-agent/kya"
],
"env": {
"KYA_API_KEY": "<KYA_API_KEY>",
"KYA_BASE_URL": "<KYA_BASE_URL>"
}
}
}
}{
"servers": {
"shield-kya": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@shield-agent/kya"
],
"env": {
"KYA_API_KEY": "<KYA_API_KEY>",
"KYA_BASE_URL": "<KYA_BASE_URL>"
}
}
}
}Put your own values in place of
<KYA_BASE_URL> (Control plane origin (e.g. http://127.0.0.1:8090 or hosted URL)), <KYA_API_KEY> (API key for the control plane (required when auth is on)).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
KYA_HOST (Dual-plane host tag: ide (authoring) or runtime (production)), KYA_AGENT_ID (Registered agent principal id).
Alternatives to Shield Kya
same job, measured the same waySpec-driven development for AI coding agents: live requirements, stories and traceability over MCP
Runtime authority for AI agents: credential mediation, spend cap, approval gates, audit log.
Polarion ALM MCP server for requirements, LiveDocs, work items, traceability and test management.
Pre-execution gate for AI-agent tool calls. Touch ID approval. Tamper-evident audit log.
Build and monitor LLM apps on Orq.ai: AI gateway, agents, prompts, evals, traces.
Read local agent-run JSONL traces through MCP for failures, approvals, and run comparisons.
Kibi requirements, traceability, and proof MCP. Install as a project dev dependency.
Trace, evaluate, and optimize your LLM, RAG, and agent apps with Noveum observability.
Shield Kya — questions
Answers built from our own checks of this server.