Qiniso
OfficialRelated Servers
Alternatives to Qiniso
- AlicenseAqualityCmaintenanceVerified ICD-10-CM code lookup & validation for AI agents — official descriptions, not guesses.395 npm1Apache 2.0
Related Servers
- AlicenseAqualityDmaintenanceVerified validation of structured identifiers — IBAN, payment cards, ISBN-13 and VIN — for AI agents. Runs the real checksum algorithms (mod-97, Luhn, mod-10, ISO 3779) instead of letting the model guess, and returns structured results with clear errors.438 npmApache 2.0
- AlicenseAqualityDmaintenanceVerified locale data for AI agents: dates, phone numbers, currency formatting, VAT/sales-tax by date, public holidays, and addresses (UK & US). Returns checked answers and flags impossible inputs instead of guessing.7Apache 2.0
- AlicenseCqualityDmaintenanceProvides deterministic data parsing and enrichment for AI agents, including bank statements, trade history, EDI, PDFs to structured markdown, and atomic enrichment for amounts, dates, and addresses, with strict schema enforcement to prevent hallucinations.3729 npm2ISC

MadTaco MCP Serverofficial
AlicenseAqualityDmaintenanceProvides verification and utility APIs for AI agents to validate tax IDs, screen sanctions, verify companies, and inspect domains using prepaid USD credits, with no charge for failed checks.1364 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to perform identity verification, KYC/KYB, PEP & sanctions screening, bank statement analysis, and workflow automation via the Model Context Protocol.MIT
- FlicenseNot gradedqualityAmaintenanceVerifiable document intelligence for AI agents. Extract, summarize, claim-check, and notarize PDFs & URLs with cryptographic proofs, cross-document search, and on-chain attestation via Base L2.-
TDQS
Scored across 56 tools
Each tool validates a distinct identifier type, and the descriptions use explicit cross-references (e.g. validate_isbn10 directs to validate_isbn) to prevent misselection. Some overlap exists among validate_tld, validate_domain, validate_url, and validate_email, but their scope is clearly delineated. Overall the tool boundaries are mostly unambiguous.
The dominant pattern is validate_<identifier>, applied consistently across nearly 50 of 56 tools. The six utility tools (parse_date, format_currency, is_holiday, next_holiday, tax_rate, parse_address) break the pure verb_noun pattern, creating a minor inconsistency. The naming style is otherwise uniform with lowercase underscores.
With 56 tools, this server greatly exceeds the 25-tool threshold that signals an oversized surface. Even though each validator is narrowly focused, the large number will slow agent navigation and increase the risk of selecting the wrong tool. The surface could be consolidated, e.g. by grouping country-specific national IDs into a single parameterized validator.
The validator surface is exceptionally broad, covering GS1 codes, financial identifiers, crypto addresses, and national IDs from dozens of countries, plus date, currency, holiday, and address helpers. Common identifiers like US SSN, UK NI number, or Canadian SIN are missing, but these are minor gaps given the extensive coverage. The tools work together without dead ends, returning valid/false with explanatory details.