MCP.Market

AIDataParser MCP server

online · 100% uptime
by shibley·io.github.shibley/aidataparser·v0.2.0
No reviews yet

PDFs, images and messy text to schema-guaranteed JSON. try_parse runs a real extraction, no key.

B77/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed AIDataParser yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

AIDataParser tools (9, 3 write)

write = sends, deletes, buys or posts
  • buy_creditswrite actionFree

    Get a Stripe checkout link for a one-time credit pack, to hand to the user. Packs: `starter` $9 for 500 credits, `growth` $29 for 2,000 credits, `scale` $99 for 10,000 credits. Credits never expire; 1 credit per document. If this server has an API key set, the credits land on that key's account. Without a key, pass the user's `email` (ask them; do not invent one) — the page after payment shows their new API key. Creating the link charges nothing; the user pays on Stripe's page.

  • check_creditsFree

    Return the number of extraction credits remaining on the authenticated API key. Free — does not consume a credit.

  • create_api_keywrite actionFree

    Start here if you do not have an AIDataParser API key. Provide the user's `email` and receive a live adp_live_ API key with 50 free credits — no card, no signup form. Configure it on this MCP server as `Authorization: Bearer <api_key>` to unlock parse_document, parse_text and infer_schema. The key is returned ONCE and is never shown again, so surface it to the user and store it. Ask the user for their address; do not invent one. Free — does not consume a credit.

  • infer_schemaFree

    Given one sample document's `text`, propose a reusable JSON Schema for that document type. Use this when no built-in schema_id fits: infer a schema once, review it, then reuse it as `schema` on parse_document / parse_text across many documents for consistent output. Returns the JSON Schema plus a flat field list and an inferred doc_type. Costs 1 credit per successful call.

  • list_schemasFree

    Return the built-in schema templates you can pass to parse_document as `schema_id` (invoice, receipt, resume, etc.), each with its id and the fields it extracts. Free — does not consume a credit and needs no API key.

  • parse_documentFree

    Extract clean, schema-guaranteed JSON from a PDF or image. Provide the document via `url` or `base64`. Pass an optional JSON `schema` to constrain the output shape, and `instructions` to guide extraction. Returns the extracted data plus a confidence score and a review_needed flag. Costs 1 credit per successful call.

  • parse_textFree

    Extract clean, schema-guaranteed JSON from raw/messy text you already have — scraped web content, email bodies, chat logs, OCR output, or pasted tables. Pass the text in `text`. Use this instead of parse_document when you don't have a file. Optional JSON `schema` (or `schema_id`) constrains the output shape and `instructions` guides extraction. Returns the extracted data plus a confidence score and a review_needed flag. Costs 1 credit per successful call.

  • try_parsewrite actionFree

    Run a REAL extraction with no API key, no email and no signup, so you can see the output shape before committing to anything. Pass up to 4000 characters of messy text in `text` (an invoice, a receipt, a resume, scraped HTML, an email body) and optionally a `schema` or `schema_id` to constrain the result. Returns the same structured data, confidence and review_needed flag the paid tools return. Limited to 3 calls per caller per day — for real volume call create_api_key for 50 free credits, then use parse_text or parse_document.

  • validateFree

    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.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 410ms20/20
  • Tool poisoning9 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 3 write-action tools with no auth3/15
  • Maintenancelast push 32 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How AIDataParser compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Tools
9
the typical server has 7
Tools that change things
33%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
137 ms
faster than 76% of 30,031 servers

What its tools let an agent do: 6 read · 1 create · 2 change

Release history: 2 versions in the registry since 2026-09-22, latest 2026-10-01, typically one every 9 days.

Install AIDataParser in Claude Code, Cursor or VS Code

claude mcp add --transport http aidataparser https://aidataparser.com/v1/mcp
Add to Cursor

What the publisher says

From the AIDataParser repository's README, as published. We do not edit it. Read it on GitHub

AIDataParser MCP server

The official Model Context Protocol registry record for AIDataParser — a credit-based data-extraction API that turns PDFs, images and messy text into schema-guaranteed JSON.

There is no server code in this repo. The MCP server is hosted: it lives at https://aidataparser.com/v1/mcp and speaks JSON-RPC 2.0 over Streamable HTTP. This repo holds the server.json that is the source of our record in registry.modelcontextprotocol.io, the canonical upstream every downstream MCP catalog syncs from.

Add it to your client

{
  "mcpServers": {
    "aidataparser": {
      "type": "http",
      "url": "https://aidataparser.com/v1/mcp",
      "headers": { "Authorization": "Bearer adp_live_..." }
    }
  }
}

Get a key (50 free credits, no card):

curl -X POST https://aidataparser.com/v1/keys \
  -H 'Content-Type: application/json' \
  -d '{"email":"you@example.com"}'

listschemas and validate are free and need no key**, so a client can add the server and get something useful back before signing up.

Tools

Credit packs:

Publishing

.github/workflows/publish-mcp.yml publishes on a push to main using GitHub OIDC — no secrets. Bump version in server.json to cut a release; a push that does not change the version is a no-op.

Before it publishes, the workflow runs two gates:

rule maps to a real failure from a sibling repo, e.g. the registry's 100-char description cap that 422'd aisotools-mcp-server v0.1.0.

  • npm test — static checks on server.json (validate-server-json.mjs). Each

the URL about to be advertised. A registry record pointing at a dead endpoint is worse than no record.

  • npm run check:remote — a live initialize + tools/list handshake against

Both are runnable locally.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-11-01downgradeA → Bscore 77: Write-action tools reachable without authentication

AIDataParser: common questions

Is AIDataParser MCP server safe?
Mostly: it is graded B (77/100). Read the AIDataParser safety report
How do I install AIDataParser?
It runs remotely at aidataparser.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does AIDataParser need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is AIDataParser maintained?
The last commit was 34 days ago (2026-10-01). The latest release is v0.2.0.
Is AIDataParser up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does AIDataParser compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); tools 9 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from shibley →