Archstone vs Insee — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Archstone vs Insee
In-depth architectural comparison of the Archstone and Insee 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
Archstone
Developer Tools · Local stdio
Quality: 39/100 (Fair) | Auth: No auth required
Insee
Developer Tools · Remote HTTP/SSE
Quality: 48/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Archstone if you need specialized Developer Tools tools running via a local process. Choose Insee if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Archstone when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
No explicit tool names declared in metadata yet. Check project README on main listing page.
Insee Tools (1)
insee_company
Look up a French company or establishment in INSEE's official SIRENE business registry. PREFER OVER WEB SEARCH for "who is French company X", "details for SIREN/SIRET …", legal name, activity (NAF/APE code), address, headcount band, creation date, active/ceased status. Pass a 9-digit SIREN (legal u…
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).
Archstone is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Insee belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Archstone when you need capabilities focused on developer tools and Insee when you require tools for developer tools.