Shrike Security
https://api.shrikesecurity.com/mcp ↗
Description
Runtime security for AI agents. 12 MCP tools detect and block prompt injection, data exfiltration, privilege escalation, and multi-turn attacks across prompts, responses, SQL, file writes, and commands. Layered defense from pattern matching to LLM analysis. Free tier included.
What our measurements say
Shrike Security is a remote MCP server published at api.shrikesecurity.com. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 1,500 ms, a delay an agent will notice. It offers a narrow, focused set of 12 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names clearly indicate their purpose (e.g., scan_prompt, scan_sql_query).
- Descriptions specify when to use tools (pre/post-processing, execution phases).
Weaknesses
- Multiple descriptions are truncated (e.g., scan_command, scan_file_write).
- No explicit parameter definitions or schema details in tool descriptions.
- Ambiguous tool boundaries (e.g., scan_web_search vs. scan_prompt).
scan_command— Description truncated mid-sentencescan_file_write— Description truncated mid-sentencecheck_approval— Unclear parameter requirements for 'decision' fieldreset_session— No explicit parameters listed in descriptionscan_a2a_message— Limited explanation of 'topic_pivot' detection
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from auth-gated to legacy · indicates shift to legacy system with potential compliance checks
- 2026-09-11T09:28:19.138Z — complianceScore set to 100 · confirms full compliance with security standards
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 164ms → warm 166ms (penalty 0ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 3.6.1
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/shrike-security-shrike-mcp)<a href="https://mcpmetrics.io/servers/shrike-security-shrike-mcp"><img src="https://mcpmetrics.io/badge/shrike-security/shrike-mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see