In-depth architectural comparison of the MCP Maigret and Assay MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Maigret
Security · Local stdio
Quality: 64/100 (Good) | Auth: No auth required
Assay
Security · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose MCP Maigret if you need specialized Security tools running via a local process. Choose Assay if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Maigret when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: MAIGRET_REPORTS_DIR.
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Deterministic, fail-closed policy enforcement for MCP tool calls, Offline-verifiable, tamper-evident evidence bundles of decisions and observations, Kernel-level IPv4/TCP egress enforcement via eBPF/LSM and Landlock on Linux.
MCP server for maigret, a powerful OSINT tool that collects user account information from various public sources. This server provides tools for searching usernames across social networks and analyzing URLs.
Policy-as-code gate for MCP. A fail-closed proxy that denies risky tool calls before they run, produces offline-verifiable evidence bundles of what executed, and enforces IPv4/TCP egress in-kernel via eBPF/LSM and Landlock on Linux. Deterministic and offline-first.
Category & Scope
Tools & Capabilities Breakdown
MCP Maigret Tools (7)
search_username
username
format
use_all_sites
tags
parse_url
url
Assay Tools (6)
Deterministic, fail-closed policy enforcement for MCP tool calls
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
MCP Maigret is categorized under Security and uses a local stdio subprocess. In contrast, Assay belongs to Security using local stdio subprocess. Select MCP Maigret when you need capabilities focused on security and Assay when you require tools for security.