rubyhash-mcp
Related Servers
Alternatives to rubyhash-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables deep, order-independent comparison of JSON files to detect differences including missing keys, value mismatches, and type differences. Provides detailed reports with path tracking for precise identification of variations between JSON structures.MIT
- AlicenseAqualityCmaintenanceEnables validating JSON/JSONC, getting/setting values with jq-like paths, pretty-printing or minifying, validating against Ajv JSON Schema, and diffing local files or inline strings without network calls.8MIT
- AlicenseAqualityBmaintenanceEnables AI agents to perform exact, reproducible mechanical computation — text diffing, hashing, JSON querying, calendar arithmetic, deadline-bounded regex extraction, CSV parsing, similarity scoring, unit and base conversion — instead of relying on probabilistic guessing. Runs dependency-free, read-only and offline over stdio, with schema validation and hard caps on every operation so no call can hang the client.1539 npmMIT
- AlicenseNot gradedqualityDmaintenanceDeterministic JSON validation and repair for AI agents. Validates, repairs, schema-checks, and diffs JSON so long-running agents don't corrupt their session state with malformed writes.MIT
- AlicenseAqualityBmaintenanceLarge-file-safe JSON MCP server with 10 tools: format, validate, search, JSONPath query, deep diff, and multi-format conversion (CSV/TSV/YAML/TypeScript). Handles JSON of any size without crashing.10MIT
- AlicenseNot gradedqualityBmaintenanceProvides local, privacy-first tools for redacting sensitive data, decoding JWTs, estimating LLM costs, splitting documents for context, checking output fidelity, and hashing text, all without network calls.260 npmMIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one compares two Ruby hashes and returns a diff, the other converts a Ruby hash/array literal to JSON. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun snake_case pattern: ruby_hash_diff and ruby_to_json. The prefix 'ruby_' is shared, and the second part describes the action ('hash_diff' vs 'to_json').
With only 2 tools, the server is minimal but still focused. It feels slightly thin for a general utility server, but for a niche Ruby hash utility it is acceptable and not excessive.
The tools cover diffing and conversion, which are useful but there are obvious gaps such as merging, validation, or formatting. The surface is not severely incomplete but lacks typical CRUD lifecycle coverage.