C2padisclosure MCP vs Inforcer
A side-by-side look at the C2padisclosure MCP and Inforcer MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose C2padisclosure MCP for security work over a hosted endpoint; choose Inforcer for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose C2padisclosure MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
Choose Inforcer when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
INFORCER_REGION, INFORCER_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 36/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | INFORCER_REGIONINFORCER_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View C2padisclosure MCP | View Inforcer |
Tools & capabilities
C2padisclosure MCP tools
No tool names declared yet. Check the project README from the listing page.
Inforcer 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.
C2padisclosure MCP
{
"mcpServers": {
"c2padisclosure-mcp": {
"url": "https://c2padisclosure.clauxel.com/mcp"
}
}
}
Inforcer
{
"mcpServers": {
"inforcer-2": {
"command": "npx",
"args": [
"-y",
"github:WYRE-AI/inforcer-mcp"
],
"env": {
"INFORCER_REGION": "YOUR_INFORCER_REGION_HERE",
"INFORCER_API_KEY": "YOUR_INFORCER_API_KEY_HERE"
}
}
}
}
Frequently asked questions
C2padisclosure MCP is categorized under Security and uses a remote HTTP/SSE transport. Inforcer belongs to Security and uses a local stdio subprocess. Pick C2padisclosure MCP for security work and Inforcer for security.
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.
C2padisclosure MCP has no declared pricing — check the project's own site. Inforcer has no declared pricing — check the project's own site. 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 c2padisclosure-mcp and inforcer-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, C2padisclosure MCP has a quality signal of 36/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Inforcer has 40/100 (Fair) with 2 views, 0 installs and 1 GitHub stars.