_ registry / mcp streamable-http · checked 1h ago

aidataparser

https://aidataparser.com

Registry code: 1ac81ccb5843b3fc

api record

AIDataParser extracts schema-guaranteed JSON from PDFs, images, and raw text. START HERE: call try_parse with a short 4000-character text excerpt to run a real extraction with NO API key, no email and no signup (3 calls per caller per day) — that is the fastest way to see whether the output fits. No API key yet? Call create_api_key with the user's email first — it returns a live adp_live_ key with 50 free credits, no card, and you then set it on this server as `Authorization: Bearer <key>`. With a key: call parse_document with a `url` or `base64` document, or parse_text with a `text` string;…

endpoint
https://aidataparser.com/v1/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is aidataparser live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is aidataparser free to use?
Yes — the hub reached it with no key and no payment.
What tools does aidataparser have?
9 tools: try_parse, create_api_key, parse_document, infer_schema, validate, parse_text, check_credits, buy_credits, ….
Is aidataparser safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.9%

90 days 99.5%· all time 99.5%

latency
997ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 584 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
topic
documents & files extraction & ocr
used for
  • extract json from a pdf or image
  • parse messy text into structured data
  • infer a json schema from a sample document
  • validate json against a schema
takes → gives
documents, images, text → data
tools
7 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
1 open 8 never probed 1 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_schemas reads open 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • try_parse reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "text"
  ],
  "properties": {
    "text": {
      "type": "string",
      "description": "The raw text to extract structured data from, up to 4000 characters. Send a representative excerpt rather than a whole corpus."
    },
    "schema": {
      "type": "object",
      "description": "Optional JSON Schema describing the exact output shape you want. When provided, the returned `data` conforms to it."
    },
    "schema_id": {
      "type": "string",
      "description": "Optional named template to use instead of a hand-written schema, e.g. \"invoice\", \"receipt\", \"resume\". Call list_schemas for the full set. Ignored when `schema` is provided."
    },
    "instructions": {
      "type": "string",
      "description": "Optional natural-language guidance for what to extract."
    }
  }
}
    arguments 24 lines
  • create_api_key changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "description": "The user's email address. The account and its free credits belong to this address; an address that already has an account is refused rather than issued a second key."
    }
  }
}
    arguments 12 lines
  • parse_document reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Public http(s) URL of the PDF or image to parse."
    },
    "base64": {
      "type": "string",
      "description": "Base64-encoded document bytes (alternative to `url`). Provide `media_type` alongside it."
    },
    "redact": {
      "type": "boolean",
      "description": "When true, PII (emails, SSNs, card numbers, phones, etc.) is masked in the output before it leaves the server."
    },
    "schema": {
      "type": "object",
      "description": "Optional JSON Schema describing the exact output shape you want. When provided, the returned `data` conforms to it."
    },
    "schema_id": {
      "type": "string",
      "description": "Optional named template to use instead of a hand-written schema, e.g. \"invoice\", \"receipt\", \"resume\". Call the list_schemas tool for the full set. Ignored when `schema` is provided."
    },
    "media_type": {
      "type": "string",
      "description": "MIME type for `base64` input, e.g. application/pdf, image/png, image/jpeg."
    },
    "instructions": {
      "type": "string",
      "description": "Optional natural-language guidance for what to extract."
    }
  }
}
    arguments 33 lines
  • infer_schema reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "text"
  ],
  "properties": {
    "text": {
      "type": "string",
      "description": "A single representative sample of the document type, as text."
    },
    "doc_type": {
      "type": "string",
      "description": "Optional hint for what kind of document this is, e.g. \"purchase order\", \"lab report\"."
    },
    "instructions": {
      "type": "string",
      "description": "Optional guidance on which fields matter or how to shape the schema."
    }
  }
}
    arguments 20 lines
  • validate reads unknown 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "data"
  ],
  "properties": {
    "data": {
      "description": "The JSON value to validate."
    },
    "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."
    }
  }
}
    arguments 19 lines
  • parse_text reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "text"
  ],
  "properties": {
    "text": {
      "type": "string",
      "description": "The raw text to extract structured data from."
    },
    "redact": {
      "type": "boolean",
      "description": "When true, PII (emails, SSNs, card numbers, phones, etc.) is masked in the output before it leaves the server."
    },
    "schema": {
      "type": "object",
      "description": "Optional JSON Schema describing the exact output shape you want. When provided, the returned `data` conforms to it."
    },
    "schema_id": {
      "type": "string",
      "description": "Optional named template to use instead of a hand-written schema, e.g. \"invoice\", \"receipt\", \"resume\". Call the list_schemas tool for the full set. Ignored when `schema` is provided."
    },
    "instructions": {
      "type": "string",
      "description": "Optional natural-language guidance for what to extract."
    }
  }
}
    arguments 28 lines
  • check_credits reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • buy_credits unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "pack": {
      "enum": [
        "starter",
        "growth",
        "scale"
      ],
      "type": "string",
      "description": "Which pack. Defaults to starter."
    },
    "email": {
      "type": "string",
      "description": "The user's email. Required only when no API key is set on this server; ignored when one is."
    }
  }
}
    arguments 18 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1ac81ccb5843b3fc.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1ac81ccb5843b3fc/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1ac81ccb5843b3fc/badge.svg)](https://brick.blue/agent/1ac81ccb5843b3fc?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.