Skip to main content
Glama

Jsonschema

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

JSON Schema validation 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
Uptime
29.4% over 41 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-jsonschema
GitHub Stars
0
Server Listing
mcp-jsonschema

TDQS

A4.1/5.0

Scored across 32 tools

Disambiguation3/5

Most tools map to distinct resources (memory CRUD, subscriptions, entity resolution, validation), but the flagship routing tools overlap heavily: ask_pipeworx, ask_pipeworx_beta (explicitly identical right now), ask_pipeworx_grounded, and deep_research all funnel questions to the same catalog, and ai_visibility_check vs scan_competitor_ai_presence wrap the same probe. The descriptions do a lot of workarounds to steer callers, but the boundaries require careful reading rather than being self-evident.

Naming Consistency4/5

Names are uniformly snake_case with clean domain prefixes (polymarket_*, ask_pipeworx*, scan_*, validate_*, *_subscriptions), so grouping is predictable. Minor deviation from a strict verb_noun pattern (entity_profile, bet_research, recent_changes) but nothing jarring or mixed-convention.

Tool Count3/5

32 tools is on the heavy side. The underlying scope is genuinely broad (a whole structured-data gateway plus its meta-tools), so many earn their place, but the cluster of near-duplicate routers (ask_pipeworx / _beta / _grounded / deep_research) and overlapping scans suggests the surface could be consolidated without losing capability.

Completeness4/5

Coverage is broad and lifecycle-aware: memory has remember/recall/forget, subscriptions have subscribe/unsubscribe/list_subscriptions/recent_alerts, and research/validation/market tools are well-populated. Gaps are minor (e.g. no explicit update for stored memory, subscription management is thin on editing params), but core workflows have no dead ends.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
      • changedInput schema / properties / type / enum
        Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
      • changedInput schema / properties / value / description
        Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  2. 1 tool update
    • Changedresolve_entity1 field changed
      • changedInput schema / properties / value / description
        Previous value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources