Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/KevinRabun/GDPRShiftLeftMCPWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/kevinrabun/gdprshiftleftmcp/gdprshiftleftmcp)<a href="https://agentmods.dev/mcp/kevinrabun/gdprshiftleftmcp/gdprshiftleftmcp"><img src="https://agentmods.dev/badge/mcp/kevinrabun/gdprshiftleftmcp/gdprshiftleftmcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/kevinrabun/gdprshiftleftmcp/gdprshiftleftmcp"><img src="https://agentmods.dev/badge/mcp/kevinrabun/gdprshiftleftmcp/gdprshiftleftmcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
GDPRShiftLeftMCP scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"GDPRShiftLeftMCP": {
"command": "uvx",
"args": [
"gdpr-shift-left-mcp"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A cf6447828b1a
GDPRShiftLeftMCP is an MCP server published in the GitHub repository KevinRabun/GDPRShiftLeftMCP (2 stars, last pushed 8mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
complyedge
Runtime EU AI Act deny for agent I/O (Article 5, Article 50) — ComplyEdge Python SDK. Runs locally from the complyedge Python package.
uodo-mcp
MCP server for searching and analyzing UODO (Polish Data Protection Authority) decisions. Runs locally from the @thescalablelegalmarketer/uodo-mcp npm package.
lexvibe
LexVibe MCP server — one-step legal compliance for vibe-coded apps: privacy policy, terms of service, cookie consent banner and EU AI Act check from Claude Code, Cursor, Codex, Gemini CLI or any MCP client. Runs locally from the @lexvibe/mcp npm package.
compliance-aiops
Governed compliance-evidence tooling: reads the AIops governance audit trails and produces framework-mapped (HIPAA/PCI-DSS/SOC2/GDPR), hash-chain-sealed evidence bundles with a built-in governance harness (audit, budget, risk tiers). Runs locally from the compliance-aiops Python package.
mcp-nsa
MCP server for Polish administrative court rulings (NSA/WSA) via CBOSA with citations. Runs locally from the @matematicsolutions/mcp-nsa npm package.
legalize-mcp
Unofficial MCP server (not affiliated with legalize-dev) over the legalize-dev law-as-git corpus - national legislation for 32 jurisdictions (21 EU) as version-controlled Markdown with ELI-style citations and verifiable provenance. Runs locally from the legalize-mcp Python package.