About this integration
Reliability + security proxy for MCP: runtime tool-security and a compliance-mapped audit trail.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- unknown
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.6.1
- Package
- mcp-bastion
- Last compatibility test
- Not independently tested
Connect your agent
mcp-bastionDocumented gateway behavior only. Each upstream must be reviewed separately, and no upstream server or endpoint was executed.
Capabilities: MCP gateway, upstream health and reconnect, tool security and audit
Connected profiles
Additional details
io.github.Gowthaman90/mcp-bastion
Source ↗ · Checked 2026-09-170.6.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17mcp-bastion
Source ↗ · Checked 2026-09-191.0.2
Source ↗ · Checked 2026-09-19The client spawns Bastion over stdio; its documented configuration enables periodic upstream health checks and automatic reconnect.
Source ↗ · Checked 2026-09-19Authentication is determined by each configured upstream: HTTP servers can receive arbitrary authorization headers, while local stdio servers retain their own prerequisites. That variability does not fit a single native auth class.
Source ↗ · Checked 2026-09-19The reviewed connection launches mcp-bastion by npx with a required local configuration file; stdio is the default downstream and upstream transport.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19