Is the Shibley Aidataparser MCP server down?

mcp-registry/io.github.shibley/aidataparser · v1.0.0

As of 2026-10-26 18:11 UTC, the Shibley Aidataparser MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.

Extract schema-guaranteed JSON from PDFs, images and messy text. 50 free credits, no card.

claude mcp add --transport http shibley-aidataparser-mcp-server https://aidataparser.com/v1/mcp

{
  "mcpServers": {
    "shibley-aidataparser-mcp-server": {
      "type": "http",
      "url": "https://aidataparser.com/v1/mcp"
    }
  }
}

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

Agent-readiness: A (93/100)

What to fix (2)

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.shibley%2Faidataparser/fixes

{
  "name": "validate",
  "description": "Check whether a JSON object conforms to a JSON `schema` (or a built-in `schema_id` template) and get back a valid flag plus per-field errors. Use this to verify data you already hold — a prior parse result, your own output, or an upstream feed — before acting on it or spending a credit. Deterministic, free, and needs no API key.",
  "inputSchema": {
    "type": "object",
    "required": [
      "data"
    ],
    "properties": {
      "data": {
        "description": "The JSON value to validate.",
        "type": "string"
      },
      "schema": {
        "type": "object",
        "description": "JSON Schema to validate against. Takes precedence over schema_id."
      },
      "schema_id": {
        "type": "string",
        "description": "Built-in template id to validate against instead of a hand-written schema (invoice, receipt, resume, etc.). Call list_schemas for the full set."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "Validate JSON against a 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.shibley/aidataparser"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.shibley/aidataparser"}) 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).
• Compact tool list (~2,142 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.98% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• parse_document ~390 tokens
• parse_text ~363 tokens
• try_parse ~351 tokens
• infer_schema ~233 tokens
• buy_credits ~226 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.shibley%2Faidataparser.svg)](https://glimind.com/server/mcp-registry%2Fio.github.shibley%2Faidataparser?ref=badge)

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

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.shibley%2Faidataparser.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.shibley%2Faidataparser?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:b95796c65d4671e3…, first seen 2026-10-17, included at leaf 14263 of 74,630. Version history · verify what your client received.

Tools (9)

• buy_credits
• check_credits
• create_api_key
• infer_schema
• list_schemas
• parse_document
• parse_text
• try_parse
• validate

Compare: most reliable payments servers · most reliable other servers · most reliable security servers · most reliable data 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 Shibley Aidataparser MCP server down right now?

As of 2026-10-26 18:11 UTC, the Shibley Aidataparser MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.

How many tools does Shibley Aidataparser MCP server provide?

Shibley Aidataparser MCP server advertises 9 tools, including buy_credits, check_credits, create_api_key, infer_schema, list_schemas.

How do I install Shibley Aidataparser MCP server?

Point your MCP client at this streamable-http endpoint: https://aidataparser.com/v1/mcp

Is the Shibley Aidataparser MCP server safe to connect to an AI agent?

Glimind scanned all 9 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 Shibley Aidataparser 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.