convez.ai
MCP ServerSegurançaIntermediário
qinisolabs

Qiniso — Verificação Determinística de Fatos

qinisolabs/qiniso

Valida fatos estruturados de agentes IA contra checksums e dados reais, não palpites.

Ver no GitHub
InicialPluginScore · de 0 a 100

MCP server que valida estruturadamente IBANs, VAT, endereços de cripto, domínios, IDs nacionais e outros identificadores contra checksums e dados curados, sem alucinações. Complementa guardrails de segurança e forma com verificação contra o mundo real.

Instalação

$npx convez-ai qinisolabs/qiniso

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
1
Forks
0
Acompanhando
0
Saúde
37%
Último commit
há 5 meses
Versão
v0.5.0
Issues abertas
1
Contribuidores
1

Casos de uso

  • Verificação de IBANs e números de pagamento antes de emissão
  • Validação de IDs fiscais (VAT, CPF, CNPJ) e nacionais
  • Checagem de endereços de cripto e carteiras digitais
  • Garantia de integridade de domínios, emails e URLs
  • Conformidade de ISBNs, VINs e códigos de barra

Veredito

Ferramenta sólida e necessária que resolve um problema real: LLMs erram ~91% das vezes em validação de identificadores. Qiniso traz determinismo onde guardrails comuns falham. Bem arquitetado, sem dependências externas desnecessárias, pronto para produção.

README

A tradução para o português deste README ainda está na fila.

Qiniso

The deterministic fact-verification layer for AI agents.

Verified, trustworthy data tools for AI agents. "Qiniso" means "truth" in Zulu.

Website · npm · MCP endpoint · MCP Registry


Agents confidently emit IBANs, phone numbers, domains, VAT numbers and crypto addresses that are subtly — and silently — wrong. Qiniso checks the structured facts an agent produces against checksums and curated authoritative data, so a bad value is caught instead of trusted.

It's the deterministic complement to the guardrail stack: security guardrails check whether output is safe, structure guardrails check it's well-formed, and hallucination guardrails ask another LLM if it's faithful to the prompt. None of them check whether a structured fact is actually correct against the real world — because that needs computation or curated data, not another model's opinion. That's Qiniso.

On arbitrary identifiers, a frontier LLM validates them wrong ~91% of the time, cold and silently. Qiniso: 0%.

Add it to Claude

Settings → Connectors → Add custom connector, and paste — no login, no key:

https://qiniso.qinisolabs.workers.dev/mcp

Stateless, reads no user data, requires no secrets.

Use it as a library

Every check is also a typed function — no MCP required:

npm i @qinisolabs/qiniso
import { validateIban, validateVat } from "@qinisolabs/qiniso";

validateIban("GB82 WEST 1234 5698 7654 32");
// { valid: true, country: "United Kingdom", ... }

What it verifies — 56 tools across 8 domains

DomainTools
IdentifiersIBAN, payment card (Luhn + brand), ISBN-13, VIN, GTIN/UPC/EAN barcodes (+ GS1 country)
Web / networkTLD & domain (IANA root zone), IP, UUID, URL, email
FinanceISIN, CUSIP, SEDOL, LEI, US ABA routing
CryptoEthereum (EIP-55), Bitcoin (Base58Check / Bech32) addresses
National & tax IDsBrazil CPF/CNPJ, South Africa ID, Spain DNI/NIE, India Aadhaar, Italy, Poland, Netherlands, Belgium, Nordics, Portugal, Turkey, China, Germany Steuer-IdNr, France NIR, Switzerland AHV, Mexico CURP, Croatia OIB, Romania CNP, Bulgaria EGN, Estonia, Czech/Slovak rodné číslo, EU/UK VAT
AcademicISBN-10, ISSN, ORCID
LocalePhone (global), date parsing, currency, holidays (~200 countries), UK VAT-by-date
AddressesUK/US address parsing

Each tool wraps an authoritative method — a published checksum standard, an audited library (libphonenumber-js, jsvat, date-holidays, @noble/hashes), or curated reference data (the IANA root zone, UK VAT history).

What it is not

  • Not a live-data provider. It verifies facts you give it; it does not return the current time, weather, or live exchange rates.
  • Not a credential sink. It never asks for secrets or API keys. (For JWT signature verification, use a library in your own runtime so the secret never leaves your machine.)
  • Not a registration check. It validates a VAT number's checksum, not whether it is live-registered (VIES); it confirms a domain's TLD is real, not that the domain is registered.

Architecture

A TypeScript monorepo. Each domain is a typed library in packages/*; the qiniso umbrella aggregates them and exposes one MCP server over three transports — stdio (local / npx), Streamable HTTP (self-host), and a Cloudflare Worker (the hosted edge endpoint). The same core powers the importable library.

npm install
npm run build
npm test

License

Apache-2.0

Ver o original no GitHub

Bom para

Relacionados