shrike-mcp

Name: shrike-mcp
Author: Shrike Security

MCPcommunity

v4.0.2Shrike SecurityApache-2.0Updated 5d agonpm GitHub

MCP server for action governance on AI agents — 14 tools that govern tool calls, SQL queries, file writes, shell commands, and agent-to-agent messages server-side, before execution. Allow / approve / block. Session correlation. Works with Claude Desktop,

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

125Downloads/wk

2GitHub stars

2Forks

5d agoLast update

Package

AuthorShrike Security

LicenseApache-2.0

Version4.0.2

Sourcenpm+mcp-registry

npmshrike-mcp

GitHubShrike-Security/shrike-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface17 tools · 3 privileged

Security scan✓ Cleanv4.0.2 · todayHow well does this scan work?

EvalsNone

IndexedSep 1, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

17 tools · 3 privileged

Statically extracted from the published packagev4.0.2 · 1h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

scan_a2a_messageNo description published

This tool published no description. Forge does not invent one.

scan_agent_cardNo description published

This tool published no description. Forge does not invent one.

check_approvalNo description published

This tool published no description. Forge does not invent one.

scan_commandprivilegedNo description published

This tool published no description. Forge does not invent one.

scan_file_writeprivilegedNo description published

This tool published no description. Forge does not invent one.

shrike_scanNo description published

This tool published no description. Forge does not invent one.

security-auditProtective check on user input — verifies it is safe to act on before you do, then returns a clear allow / redact / block recommendation. Catches prompt injection, PII, and toxicity that could compromise your output.

Protective check on user input — verifies it is safe to act on before you do, then returns a clear allow / redact / block recommendation. Catches prompt injection, PII, and toxicity that could compromise your output.

No input schema was published for this tool.

contentThe text content to audit

The text content to audit

No input schema was published for this tool.

report_bypassNo description published

This tool published no description. Forge does not invent one.

scan_promptNo description published

This tool published no description. Forge does not invent one.

scan_declare_scopeNo description published

This tool published no description. Forge does not invent one.

scan_mcp_schemaNo description published

This tool published no description. Forge does not invent one.

scan_responseNo description published

This tool published no description. Forge does not invent one.

reset_sessionNo description published

This tool published no description. Forge does not invent one.

session_statusNo description published

This tool published no description. Forge does not invent one.

scan_sql_queryprivilegedNo description published

This tool published no description. Forge does not invent one.

scan_web_searchNo description published

This tool published no description. Forge does not invent one.

2 of 17 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Keywords

action-governanceai-agentsagent-governanceagent-securitymcpmcp-servermodel-context-protocolmodelcontextprotocolclaude-desktopcursorwindsurfclinetool-call-gatingai-governanceai-securityprompt-injectionsession-correlation

Alternatives

Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-05 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

express5.2.1+6 not drawn22 dependencies
- qs6.16.0+2 not drawn
- depd2.0.0
- etag1.8.1
- once1.4.0+1 not drawn
- send1.2.1+2 not drawn9 dependencies
  - debug4.4.3+1 not drawn
  - encodeurl2.0.0
  - escape-html1.0.3
  - etag1.8.1shown above
  - fresh2.0.0
  - http-errors2.0.1incomplete+2 not drawn1 dependency
    depd2.0.0shown above
  - mime-types3.0.2+1 not drawn
  - on-finished2.4.1incomplete
  - statuses2.0.2
- vary1.1.2
- debug4.4.3shown above+1 not drawn
- fresh2.0.0shown above
- cookie0.7.2
- router2.2.0+2 not drawn3 dependencies
  - debug4.4.3shown above+1 not drawn
  - depd2.0.0shown above
  - parseurl1.3.3
- accepts2.0.0+1 not drawn1 dependency
  - mime-types3.0.2shown above+1 not drawn
- type-is2.1.0+2 not drawn1 dependency
  - mime-types3.0.2shown above+1 not drawn
- parseurl1.3.3shown above
- statuses2.0.2shown above
- encodeurl2.0.0shown above
- mime-types3.0.2shown above+1 not drawn
- proxy-addr2.0.7+2 not drawn
- body-parser2.3.0+4 not drawn5 dependencies
  - qs6.16.0shown above+2 not drawn
  - debug4.4.3shown above+1 not drawn
  - type-is2.1.0shown above+2 not drawn
  - http-errors2.0.1incompleteshown above+2 not drawn
  - on-finished2.4.1incompleteshown above
- escape-html1.0.3shown above
- http-errors2.0.1incompleteshown above+2 not drawn
- on-finished2.4.1incompleteshown above
- content-type1.0.5
@modelcontextprotocol/sdk1.30.0+15 not drawn2 dependencies
- express5.2.1shown above+6 not drawn
- content-type1.0.5shown above

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

38 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 38

setprototypeof ~1.2.0 — required by http-errors@2.0.1package cap reached
statuses ~2.0.2 — required by http-errors@2.0.1package cap reached
toidentifier ~1.0.1 — required by http-errors@2.0.1package cap reached
ee-first 1.1.1 — required by on-finished@2.4.1package cap reached
debug ^4.4.0 — required by finalhandler@2.1.1package cap reached
encodeurl ^2.0.0 — required by finalhandler@2.1.1package cap reached
escape-html ^1.0.3 — required by finalhandler@2.1.1package cap reached
on-finished ^2.4.1 — required by finalhandler@2.1.1package cap reached
parseurl ^1.3.3 — required by finalhandler@2.1.1package cap reached
statuses ^2.0.1 — required by finalhandler@2.1.1package cap reached
encodeurl ^2.0.0 — required by serve-static@2.2.1package cap reached
escape-html ^1.0.3 — required by serve-static@2.2.1package cap reached

+26 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

shrike-mcp

Tools

Tools exposed

Dependency tree

Declared but not resolved

Topics

Related in security