Gibs MCP vs Hermetics RGPD
A side-by-side look at the Gibs MCP and Hermetics RGPD MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
H
Hermetics RGPDLegal · Remote HTTP/SSEEU data protection law for AI agents: GDPR, AI Act, EDPB, CJEU and national law, with status.39FairAuth: no auth requiredVerdict: choose Gibs MCP for legal work as a local process; choose Hermetics RGPD for legal over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Gibs MCP when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
GIBS_API_KEY. - You want tools like
classify_ai_system, check_compliance, health_check.
HChoose Hermetics RGPD when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | H Hermetics RGPD | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 49/100 · Fair | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | GIBS_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | — |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Gibs MCP | View Hermetics RGPD |
Tools & capabilities
Gibs MCP tools 3
classify_ai_systemClassify an AI system under AI Act risk levels (unacceptable, high-risk, limited, minimal) with full legal reasoning.check_complianceAsk any regulatory compliance question and get a structured answer with article-level citations.health_checkCheck if the compliance API is available. No parameters required.
Hermetics RGPD tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Gibs MCP
{
"mcpServers": {
"buildsyncinc-gibs-mcp": {
"command": "uvx",
"args": [
"gibs"
],
"env": {
"GIBS_API_KEY": "YOUR_GIBS_API_KEY_HERE"
}
}
}
}
Hermetics RGPD
{
"mcpServers": {
"hermetics-rgpd": {
"url": "https://hermetics.fr/mcp"
}
}
}
Frequently asked questions
Gibs MCP is categorized under Legal and uses a local stdio subprocess. Hermetics RGPD belongs to Legal and uses a remote HTTP/SSE transport. Pick Gibs MCP for legal work and Hermetics RGPD for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Gibs MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Hermetics RGPD is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add buildsyncinc-gibs-mcp and hermetics-rgpd as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gibs MCP has a quality signal of 49/100 (Fair) with 3 views, 0 installs and 7 GitHub stars. Hermetics RGPD has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.