extraer-datos-ine
Related Servers
Alternatives to extraer-datos-ine
No user-submitted related servers found.
Related Servers
AlicenseAqualityDmaintenanceEnables document parsing into structured, confidence-scored fields via the scan tool, working with any MCP host like Claude Desktop or Cursor.192 npmMIT- FlicenseNot gradedqualityDmaintenanceAn AI-powered MCP server that extracts structured data from Indian identity documents (Aadhaar, Passport, PAN, Driving License) using OCR, enabling Claude Desktop to read and process document images locally.-

flexorch-mcpofficial
AlicenseAqualityAmaintenanceEnables Claude and other MCP-compatible agents to process documents, extract structured data, detect PII, and export LLM-ready datasets through natural language tool calls.863 PyPI1MIT- AlicenseAqualityCmaintenanceEnables MCP clients like Claude Code to extract text from images, screenshots, and scanned documents via PaddleOCR PP-OCRv6.1BSD 3-Clause
- FlicenseAqualityDmaintenanceExtracts text content from PDFs and images using Mistral's OCR API, enabling OCR capabilities in MCP-compatible clients like Cursor and Claude Desktop.18-
- AlicenseNot gradedqualityCmaintenanceEnables document text recognition and extraction from images and PDFs using Claude Vision, including support for scanned documents and structured output, without requiring local OCR engines.MIT
TDQS
Scored across 3 tools
The three tools cover clearly distinct actions: extracting data from an INE image (extraer_ine), checking account balance (consultar_saldo), and generating a remote capture link (crear_enlace_captura). No overlap exists between reading a local file, querying a balance, and creating a link, so an agent can select unambiguously.
All three names follow a consistent Spanish verb_noun pattern (extraer_ine, consultar_saldo, crear_enlace_captura) with uniform snake_case casing. The convention is predictable and readable throughout.
Three tools is thin for a service that clearly has more surface area (destinations, extraction history, batch jobs). While each tool earns its place, the set feels minimal relative to the apparent scope implied by the descriptions (webhook/email/Telegram destinations, links, tokens).
The core lifecycle is covered: create a capture link, extract data, and check token balance. However, there is no tool to manage or list destination_ids, view extraction history, or handle batch processing, which are referenced but not exposed as operations.