io.github.vaquarkhan/mcp-bastion

MCPcommunity
v1.0.11io.github.vaquarkhanUnknownUpdated 7mo agonpmGitHub

Security middleware for MCP. Blocks prompt injection, PII leakage, and resource exhaustion.

Enterprise-Grade Security Middleware for the Model Context Protocol Releases are published to npm, PyPI, and prebuilt Docker images on GitHub Container Registry (, ) — pull/run details in DOCKER.md — via GitHub Actions on tag push. Documentation: structured paths for policy and LLM integration live in docs/README.md and docs/index.md. Community: open a GitHub Issue for bugs or gaps, a Discussion…

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 →
5GitHub stars
1Forks
7mo agoLast update
Package
Authorio.github.vaquarkhan
LicenseUnknown
Version1.0.11
Sourcemcp-registry
npm@mcp-bastion/core
GitHubvaquarkhan/MCP-Bastion
SBOMCycloneDX 1.6 ↓
Trust Status
F
10/100Untrusted
✓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 · not run+0/30
→ Our scan didn't complete — a retry is queued. Nothing to fix on your side.
—Static analysis · clean+0/20
→ Our scan didn't complete — a retry is queued. Nothing to fix on your side.
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scanScan failedvunknown · 1mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

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

Tools

Source never read1mo ago

This entry has been scanned, but the run carries no source-extraction result — either it predates tool-surface extraction or it failed before reaching that stage. A rescan is what would fill this in; the blank says nothing about the package.

About

Enterprise-Grade Security Middleware for the Model Context Protocol Releases are published to npm, PyPI, and prebuilt Docker images on GitHub Container Registry (, ) — pull/run details in DOCKER.md — via GitHub Actions on tag push. Documentation: structured paths for policy and LLM integration live in docs/README.md and docs/index.md. Community: open a GitHub Issue for bugs or gaps, a Discussion for integration questions (if enabled on the repo), or a PR for docs and examples—those help every…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

The last scan of this package failed, so no dependency tree was resolved.