io.github.OjasKord/document-integrity-validator-mcp

Est-ce que io.github.OjasKord/document-integrity-validator-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.OjasKord/document-integrity-validator-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 2 outils

• check_document≈ 974 tokens

  Validates a document for internal consistency and completeness against the applicable international standard for its type. Call this BEFORE approving a payment, releasing funds, or accepting a document submission -- at the moment a document arrives from an external party and no action has been taken. Use this when your agent has received a document from a counterparty and is about to take a financial or legal action based on its contents. Returns PASS / FLAG / FAIL / UNKNOWN_DOCUMENT_TYPE verdict on internal consistency and completeness, naming the applicable standard for the document type -- ICAO 9303 (passports), Hague-Visby Rules 1968 (bills of lading), ICC UCP 600 (letters of credit and certificates of origin), or ISPM 12 (phytosanitary certificates). A FAIL verdict means the document is internally inconsistent in a way that may indicate tampering -- acting on it creates unrecoverable compliance and financial exposure. Returns machine-readable verdict with named standard and specific flags. When you have 2-20 related documents (e.g. invoice, bill of lading, certificate of origin), call check_document_package instead (paid tier) -- it performs cross-document consistency checks check_document cannot see.

  Paramètres, retour & exemple (4)

  Paramètres

  • document_text · string · optionnel
    Extracted text content from the document. Provide this or document_image or both.
  • document_image · string · optionnel
    Base64 encoded document image. Accepts raw base64 or a data URL (data:image/jpeg;base64,...). Supported types: JPEG, PNG, GIF, WEBP.
  • document_type_hint · string · optionnel
    What the calling agent believes the document type is, e.g. "bill_of_lading", "passport", "certificate_of_origin". Optional -- the validator identifies the type independently.
  • issuing_jurisdiction · string · optionnel
    Country or issuing body, e.g. "Singapore", "ICAO", "United Kingdom". Narrows jurisdiction-specific standard selection.

  Exemple d'appel

  {"name": "check_document", "arguments": {"document_text": "texte", "document_image": "texte", "document_type_hint": "texte", "issuing_jurisdiction": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"flags": [], "reason": "texte", "verdict": "PASS", "checked_at": "texte", "confidence": "HIGH", "_disclaimer": "texte", "hold_reason": "texte", "retry_after": 1, "verdict_ttl": 1, "agent_action": "PROCEED", "analysis_type": "texte", "_upgrade_notice": "texte"}}

• check_document_package≈ 1072 tokens

  Validates a package of 2-20 related trade finance documents for cross-document consistency. Call this BEFORE approving any multi-document trade finance transaction or cross-border shipment -- at the moment a set of 2-20 related documents arrives from an external party and funds have not been released. Use this when your agent has received a full trade finance package — such as invoice, bill of lading, and certificate of origin together — and must verify all documents are consistent with each other before releasing funds. Returns PASS/FLAG/FAIL verdict per document with mismatch details. Cross-checks all documents for consistency across numeric values, party names, reference numbers, dates, and commodity descriptions. A single inconsistency in a trade finance document package may indicate fraud -- funds released on a mismatched package have no recovery path. Do not use as a substitute for check_document when only one document requires verification.

  Paramètres, retour & exemple (1)

  Paramètres

  • documents · array · requis
    Array of 2 to 20 related documents to assess individually and cross-check against each other. Each document must have a unique label.

  Exemple d'appel

  {"name": "check_document_package", "arguments": {"documents": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"verdict": "PASS", "documents": [], "checked_at": "texte", "confidence": "HIGH", "_disclaimer": "texte", "verdict_ttl": 1, "agent_action": "PROCEED", "analysis_type": "texte", "calls_remaining": "texte", "package_verdict": "texte", "data_source_status": "full", "package_agent_action": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://document-integrity-validator-mcp-production.up.railway.app/mcp