Json
Server Details
JSON tools MCP.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-json
- GitHub Stars
- 0
- Server Listing
- mcp-json
TDQS
Scored across 34 tools
The descriptions do a good job explicitly stating when to prefer one tool over another (e.g. ask_pipeworx vs ask_pipeworx_grounded vs deep_research), but the set still contains many overlapping query/research entry points (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions, validate_claim) that all answer variations of 'answer a question from data.' The beta variant is explicitly noted as currently identical to ask_pipeworx, making it a near-duplicate.
Every tool name uses consistent snake_case, with clear family prefixes (ask_pipeworx_*, polymarket_*, validate_*, *_json) that form readable, predictable groups. There is no camelCase/snake_case mixing or chaotic style variation.
34 tools is well above the 25+ 'too many' threshold for a single coherent surface. While the server spans many domains (research, entity resolution, prediction markets, subscriptions, memory, JSON utilities), the volume is heavy and several tools are overlapping near-duplicates rather than distinct capabilities.
Coverage is broad and mostly closed-loop: memory has full CRUD (remember/recall/forget), subscriptions have create/list/cancel/alert-feed, prediction markets span discovery, arbitrage, fill-risk, and cross-venue spreads, and research/entity/validation are well covered. Minor gaps exist (e.g. no explicit update/replace for stored memory beyond forget+remember), but nothing critical is missing.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
Related MCP Connectors
JSON Schema validation MCP.
Related MCP Servers
- MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for validating JSON against JSON Schema and repairing malformed/invalid JSON.2 npm1-
- FlicenseNot gradedqualityDmaintenanceMCP server that provides tools to read JSON files and query data using jsonPath expressions.-
- 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
Glama MCP Gateway
Add one secure layer between your agents and this server.