A side-by-side look at the AdversaryGate and Inkcheck MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AdversaryGate for developer tools work as a local process; choose Inkcheck for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AdversaryGate when
You need dedicated capabilities in the Developer Tools domain.
No tool names declared yet. Check the project README from the listing page.
Inkcheck 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.
AdversaryGate is categorized under Developer Tools and uses a local stdio subprocess. Inkcheck belongs to Developer Tools and uses a local stdio subprocess. Pick AdversaryGate for developer tools work and Inkcheck for developer tools.
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.
AdversaryGate has no declared pricing — check the project's own site. Inkcheck 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 adversarygate and chaoz23-inkcheck as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AdversaryGate has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 4 GitHub stars. Inkcheck has 55/100 (Good) with 3 views, 0 installs and 3 GitHub stars.