Mcpsentry

security MCP Server

FastAPI → MCP bridge with built-in security audit + runtime prompt-injection guardrail. One line to expose to Claude/ChatGPT/Gemini, one line to verify it's safe, one line to block injection at runtime.

Verified
securitysecurity
2 views0 stars0 forksMIT

Why This Matters

Discovered via github-topic:model-context-protocol and last synced 4mo ago.

Verified
Source
github-topic:model-context-protocol
Stars
0
Last synced
4mo ago
Install
Check source

Install

Install instructions not detected yet

Check the source repository for the latest setup steps.

View source instructions
9
Tools
0
Resources
0
Prompts
Standard I/O
Transport

Available Tools (9)

02_full_schema_description

0

04_separate_server

0

Risk

What happens

08_auth_token_passthrough

0

01_basic_usage_example

0

fastapi_mcp

FastMCP `from_fastapi()`

Example

🔴 Crit

2

0

spec-based

If you don't care about auditing what you expose or what comes back through it, `fastapi_mcp` and `FastMCP` are fine. If you do, **MCPSentry is the only one that fails your build when you got it wrong — and your runtime when something looks off.** --- ## Runtime guardrails (v0.3) The audit happens once, at startup. **The guardrail runs on every single `tools/call` request** while the server is alive. It scans the call's `arguments` (recursively, in dicts and lists) against a curated catalogue of prompt-injection patterns: