Shield Kya vs Scopeblind Gateway
A side-by-side look at the Shield Kya and Scopeblind Gateway MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Shield Kya for security work as a local process; choose Scopeblind Gateway for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Shield Kya when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
KYA_API_KEY, KYA_OFFLINE, KYA_DIFF_PREVIEW, KYA_GATE. - You want tools like
kya.policy_evaluate, kya.session_ingest, kya.request_approval.
Choose Scopeblind Gateway when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
INTERNAL_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 55/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | KYA_API_KEYKYA_OFFLINEKYA_DIFF_PREVIEWKYA_GATE | INTERNAL_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 11 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Shield Kya | View Scopeblind Gateway |
Tools & capabilities
Shield Kya tools 3
kya.policy_evaluateALLOW` \kya.session_ingestObserve / raise-only riskkya.request_approvalOpen a human Hold. Does not execute the side effect
Scopeblind Gateway tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Shield Kya
{
"mcpServers": {
"shield-kya": {
"command": "npx",
"args": [
"-y",
"@shield-agent/kya@latest"
],
"env": {
"KYA_API_KEY": "YOUR_KYA_API_KEY_HERE",
"KYA_OFFLINE": "YOUR_KYA_OFFLINE_HERE",
"KYA_DIFF_PREVIEW": "YOUR_KYA_DIFF_PREVIEW_HERE",
"KYA_GATE": "YOUR_KYA_GATE_HERE"
}
}
}
}
Scopeblind Gateway
{
"mcpServers": {
"tomjwxf-scopeblind-gateway": {
"command": "npx",
"args": [
"-y",
"@scopeblind/passport"
],
"env": {
"INTERNAL_API_KEY": "YOUR_INTERNAL_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Shield Kya is categorized under Security and uses a local stdio subprocess. Scopeblind Gateway belongs to Security and uses a local stdio subprocess. Pick Shield Kya for security work and Scopeblind Gateway for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Shield Kya has no declared pricing — check the project's own site. Scopeblind Gateway is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add shield-kya and tomjwxf-scopeblind-gateway as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Shield Kya has a quality signal of 55/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Scopeblind Gateway has 53/100 (Good) with 4 views, 0 installs and 11 GitHub stars.