Contract Guard vs MCP Log Proxy
A side-by-side look at the Contract Guard and MCP Log Proxy MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
Contract GuardDeveloper ToolsDeterministic JSON Schema validation with exact violations and conservative type normalization.39FairAuth: no auth requiredVerdict: choose Contract Guard for developer tools work; choose MCP Log Proxy 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?
CChoose Contract Guard when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
Choose MCP Log Proxy when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Contract Guard | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 39/100 · Fair | 47/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 32 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Contract Guard | View MCP Log Proxy |
Tools & capabilities
Contract Guard tools
No tool names declared yet. Check the project README from the listing page.
MCP Log Proxy 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.
Contract Guard
No confirmed install command for Contract Guard yet — follow the setup steps linked from its listing page rather than a guessed package name.
MCP Log Proxy
{
"mcpServers": {
"emicklei-mcp-log-proxy": {
"command": "npx",
"args": [
"-y",
"@browsermcp/mcp@latest"
]
}
}
}
Frequently asked questions
Contract Guard is categorized under Developer Tools and uses an install path we have not confirmed yet. MCP Log Proxy belongs to Developer Tools and uses a local stdio subprocess. Pick Contract Guard for developer tools work and MCP Log Proxy 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. Contract Guard has no confirmed install command yet — follow its own setup instructions.
Contract Guard is listed as free. Auth: no auth required. MCP Log Proxy 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 contract-guard and emicklei-mcp-log-proxy as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Contract Guard has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP Log Proxy has 47/100 (Fair) with 4 views, 0 installs and 32 GitHub stars.