JSON Contracts vs RugSnare
A side-by-side look at the JSON Contracts and RugSnare MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose JSON Contracts for legal work as a local process; choose RugSnare for legal as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose JSON Contracts when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
JSON_CONTRACTS_DIR. - You want tools like
list_contracts, read_contract, get_json_contract.
Choose RugSnare when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 57/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | JSON_CONTRACTS_DIR | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 4 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View JSON Contracts | View RugSnare |
Tools & capabilities
JSON Contracts tools 8
list_contractsList currently loaded JSON contracts.read_contractRead a loaded JSON contract.get_json_contractReturn schema, rules, examples, instructions, and input so the agent/model can produce JSON.get_edit_contractReturn schema, rules, current JSON, edit instructions, and input so the agent/model can edit existing JSON.validate_jsonValidate agent-produced JSON against a contract schema.get_repair_contractReturn schema, rules, previous invalid JSON, validation errors, and repair instructions.statusReturn json-contracts MCP server status and loaded contract metadata.reload_contractsRescan the JSON contracts directory and reload valid contracts.
RugSnare 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.
JSON Contracts
{
"mcpServers": {
"json-contracts": {
"command": "npx",
"args": [
"-y",
"json-contracts@latest"
],
"env": {
"JSON_CONTRACTS_DIR": "YOUR_JSON_CONTRACTS_DIR_HERE"
}
}
}
}
RugSnare
{
"mcpServers": {
"rugsnare": {
"command": "npx",
"args": [
"-y",
"rugsnare"
]
}
}
}
Frequently asked questions
JSON Contracts is categorized under Legal and uses a local stdio subprocess. RugSnare belongs to Legal and uses a local stdio subprocess. Pick JSON Contracts for legal work and RugSnare for legal.
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.
JSON Contracts has no declared pricing — check the project's own site. RugSnare 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 json-contracts and rugsnare as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, JSON Contracts has a quality signal of 57/100 (Good) with 3 views, 0 installs and 1 GitHub stars. RugSnare has 45/100 (Fair) with 1 views, 0 installs and 4 GitHub stars.