# io.github.Shrike-Security/shrike-mcp

AI agent security scanner — prompt injection detection, SQL injection, PII isolation, threat intel.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.1.1
- **Author:** io.github.Shrike-Security
- **License:** Unknown
- **npm:** shrike-mcp
- **Source:** https://github.com/Shrike-Security/shrike-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 114 days — stale; the grade is a claim about the present made from dated evidence

## Security scan

- **Status:** clean
- **Scanned:** 2026-06-13T09:18:43.633Z
- **Version scanned:** 3.7.1
- **CVEs:** none found by OSV at scan time

## Tools

15 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `scan_a2a_message`
- `scan_agent_card`
- `check_approval`
- `scan_command`
- `scan_file_write`
- `shrike_scan`
- `security-audit`
- `content`
- `report_bypass`
- `scan_prompt`
- `scan_response`
- `reset_session`
- `scan_sql_query`
- `get_threat_intel`
- `scan_web_search`

## Install

**Verdict: review** — Installable, but 2 things to check first: The last scan is 114 days old — the evidence behind this verdict is dated.
**Cautions** (coverage gaps and advisories — never blocking)
- The last scan is 114 days old — the evidence behind this verdict is dated.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"shrike\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"shrike-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs commands; runs on your machine.
- Floor 46, ceiling 74 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.Shrike-Security%2Fshrike-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.Shrike-Security%2Fshrike-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.Shrike-Security%2Fshrike-mcp
- HTML page: https://forgeregistry.com/registry/io.github.Shrike-Security%2Fshrike-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.