Is the Pipeworx Io Jsonschema MCP server down?

mcp-registry/io.github.pipeworx-io/jsonschema · v0.1.0

Also listed as glama/pipeworx-io/mcp-jsonschema

As of 2026-10-24 18:51 UTC, the Pipeworx Io Jsonschema MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

JSON Schema validation MCP.

claude mcp add --transport http pipeworx-io-jsonschema-mcp-server https://gateway.pipeworx.io/jsonschema/mcp

{
  "mcpServers": {
    "pipeworx-io-jsonschema-mcp-server": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/jsonschema/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: A (91/100)

What to fix (3)

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.pipeworx-io%2Fjsonschema/fixes

{
  "name": "validate_json_schema",
  "description": "Validate a JSON value against a JSON Schema (draft-07 subset: type, required, properties, additionalProperties, items, enum, const, min/max, minLength/maxLength, pattern, minItems/maxItems, uniqueItems, format). Returns {valid, errors:[{path,message}]}. Keyless, offline.",
  "inputSchema": {
    "type": "object",
    "examples": [
      {
        "data": {
          "age": 30,
          "name": "John Doe",
          "email": "[email protected]"
        },
        "schema": {
          "type": "object",
          "required": [
            "name",
            "age"
          ],
          "properties": {
            "age": {
              "type": "number",
              "minimum": 0
            },
            "name": {
              "type": "string"
            },
            "email": {
              "type": "string",
              "format": "email"
            }
          }
        }
      },
      {
        "data": [
          1,
          2,
          3,
          4,
          5
        ],
        "schema": {
          "type": "array",
          "items": {
            "type": "number"
          },
          "maxItems": 10,
          "minItems": 1
        }
      }
    ],
    "required": [
      "data",
      "schema"
    ],
    "properties": {
      "data": {
        "description": "The JSON value to validate (any type).",
        "type": "string"
      },
      "schema": {
        "type": "object",
        "description": "The JSON Schema to validate against."
      }
    }
  },
  "annotations": {
    "cost": {
      "all": 1
    },
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "Validate Json Schema"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.pipeworx-io/jsonschema"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.pipeworx-io/jsonschema"}) over MCP.

Passed

• Every tool and parameter is described.
• Every tool declares whether it is read-only or destructive.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.

Largest tool definitions

• company_facts ~1,192 tokens
• subscribe ~963 tokens
• polymarket_edges ~904 tokens
• research_row ~575 tokens
• ask_pipeworx ~525 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.pipeworx-io%2Fjsonschema.svg)](https://glimind.com/server/mcp-registry%2Fio.github.pipeworx-io%2Fjsonschema?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.pipeworx-io%2Fjsonschema?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.pipeworx-io%2Fjsonschema.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.pipeworx-io%2Fjsonschema.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.pipeworx-io%2Fjsonschema?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9192839dd2a33e55…, first seen 2026-10-21, included at leaf 37987 of 75,854. Version history · verify what your client received.

Tools (42)

• ai_visibility_check
• archive_compare
• archive_evidence
• ask_pipeworx
• ask_pipeworx_beta
• ask_pipeworx_grounded
• bet_research
• classify_row
• company_facts
• company_register_search
• compare_entities
• deep_research
• discover_tools
• entity_profile
• forget
• generate_llms_txt
• kalshi_weather_edge
• list_subscriptions
• pipeworx_feedback
• pipeworx_trending
• polymarket_arbitrage
• polymarket_edge_tracker
• polymarket_edges
• polymarket_fill_risk
• polymarket_kalshi_spread
• recall
• recent_alerts
• recent_changes
• release_calendar_markets
• remember
• research_row
• resolution_audit
• resolution_diff
• resolve_entity
• scan_competitor_ai_presence
• scan_dependency
• search_within
• subscribe
• suggest_questions
• unsubscribe
• validate_claim
• validate_json_schema

Compare: most reliable ml servers · most reliable web servers · most reliable retrieval servers · most reliable other servers · most reliable knowledge servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Pipeworx Io Jsonschema MCP server down right now?

As of 2026-10-24 18:51 UTC, the Pipeworx Io Jsonschema MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Pipeworx Io Jsonschema MCP server provide?

Pipeworx Io Jsonschema MCP server advertises 42 tools, including ai_visibility_check, archive_compare, archive_evidence, ask_pipeworx, ask_pipeworx_beta.

How do I install Pipeworx Io Jsonschema MCP server?

Point your MCP client at this streamable-http endpoint: https://gateway.pipeworx.io/jsonschema/mcp

Is the Pipeworx Io Jsonschema MCP server safe to connect to an AI agent?

Glimind scanned all 42 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Pipeworx Io Jsonschema MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.