io.github.ashevilleislove/ardaro-receipt-intelligence

Est-ce que io.github.ashevilleislove/ardaro-receipt-intelligence est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.ashevilleislove/ardaro-receipt-intelligence » 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 5 outils

• analyze_receipt≈ 8736 tokens

  Extract and validate structured expense data from receipt text or a provider-neutral receipt extraction. Use when an agent needs merchant, date, tax, total, line items, confidence, duplicate detection, and arithmetic validation before creating or reconciling an expense. The result is advisory and always requires human review. Paid tool: 0.25 USDC per accepted request. Requires an owner-authorized x402-capable client. Use get_document_example with service='receipt' for a fixed free example.

  Paramètres, retour & exemple (3)

  Paramètres

  • input · ? · requis
    One receipt supplied as bounded OCR text or a provider-neutral structured extraction. Choose exactly one input kind.
  • contract_version · ? · requis
    Required request contract identifier; send this exact version string.
  • existing_fingerprints · array · requis
    Receipt fingerprints already known to the caller for duplicate comparison. Supply lowercase 64-character SHA-256 hex strings, or an empty array when none are available; at most 10,000 entries.

  Exemple d'appel

  {"name": "analyze_receipt", "arguments": {"input": "texte", "contract_version": "texte", "existing_fingerprints": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_document_example≈ 16352 tokens

  Inspect a fixed synthetic request and expected result before integrating or paying. Select service from the enum; no caller document is accepted, processed or stored. Returns service and details containing that service's example. Free; no wallet authorization. Use get_document_service_status for current readiness, prices and retention instead.

  Paramètres, retour & exemple (1)

  Paramètres

  • service · string · requis · receipt | invoice | reconciliation
    receipt: extraction checks; invoice: paid invoice-to-PO quantity allocation; reconciliation: free three-document discrepancy checks without allocation. Choose one service; examples do not process caller documents.

  Exemple d'appel

  {"name": "get_document_example", "arguments": {"service": "receipt"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_document_service_status≈ 2910 tokens

  Check the selected service's current runtime readiness, input limits, pricing and retention before use. Returns service and details; ready=false means the underlying service is unavailable. Free cached runtime read; no external probe, payment, analysis or historical document retrieval. Use get_document_example for a fixed integration sample instead.

  Paramètres, retour & exemple (1)

  Paramètres

  • service · string · requis · receipt | invoice | reconciliation
    receipt: extraction checks; invoice: paid invoice-to-PO quantity allocation; reconciliation: free three-document discrepancy checks without allocation. Choose one service; examples do not process caller documents.

  Exemple d'appel

  {"name": "get_document_service_status", "arguments": {"service": "receipt"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• match_invoice≈ 5995 tokens

  USE THIS WHEN the question is a quantity-allocation question: how much of this PO has been invoiced, whether an invoice is fully, partially, or over billed against the PO, or how much quantity remains. Aggregates split invoice lines against one PO line and returns a status per line - fully_invoiced, partially_invoiced, uninvoiced, or overbilled - plus remaining quantity. Matches by explicit PO line ID or a unique exact product code only, never by description. Inputs: one invoice plus one PO; it does not accept a receipt. DO NOT USE THIS to compare a receipt against an invoice, or for a general list of differences with no allocation question - call reconcile_purchase_documents instead; it is free and does not require calling this tool first or after. Paid: 0.50 USDC per accepted comparison, explicit buyer-authorized x402 payment. Call get_document_service_status with service='invoice' first to confirm current readiness and price. Advisory output only: human review required; no delivery verification, payment execution, prior-invoice history, or accounting writes.

  Paramètres, retour & exemple (3)

  Paramètres

  • invoice · ? · requis
  • purchase_order · ? · requis
  • contract_version · ? · requis

  Exemple d'appel

  {"name": "match_invoice", "arguments": {"invoice": "texte", "purchase_order": "texte", "contract_version": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• reconcile_purchase_documents≈ 3401 tokens

  USE THIS WHEN you have up to three documents (receipt, invoice, purchase order - any subset) and need a discrepancy list: reference, item, quantity, price, or arithmetic mismatches between them. This is the default choice for 'does this receipt match the invoice' or 'do these documents agree' questions. Links use explicit line references, exact product codes, or conservative normalized descriptions. DO NOT USE THIS if the actual question is a quantity-allocation question - how much of a PO has been invoiced, or resolving partial/split invoice lines against PO quantities. This tool does not allocate billed quantities or calculate remaining PO quantities: partial quantities are reported as plain differences, and any many-to-one (split) link is flagged ambiguous_many_to_one rather than resolved. For that, call match_invoice instead (paid, 0.50 USDC) - but you never need to call it before or after this tool; each works standalone. Free, no wallet authorization, no payment metadata accepted. Missing documents or fields are marked needs_review, never inferred. No OCR, retrieval, saved analyses, paid service calls, delivery verification, payment approval, or accounting writes. Human review required.

  Paramètres, retour & exemple (3)

  Paramètres

  • invoice · object · optionnel
    Caller-supplied structured data. Use opaque supplier IDs and decimal strings; omit unknown fields. Receipt kind describes the source document, not verified delivery. Field names align with invoice matching; receipt extraction output must be mapped explicitly.
  • receipt · object · optionnel
    Caller-supplied structured data. Use opaque supplier IDs and decimal strings; omit unknown fields. Receipt kind describes the source document, not verified delivery. Field names align with invoice matching; receipt extraction output must be mapped explicitly.
  • purchase_order · object · optionnel
    Caller-supplied structured data. Use opaque supplier IDs and decimal strings; omit unknown fields. Receipt kind describes the source document, not verified delivery. Field names align with invoice matching; receipt extraction output must be mapped explicitly.

  Exemple d'appel

  {"name": "reconcile_purchase_documents", "arguments": {"invoice": {}, "receipt": {}, "purchase_order": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

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://agents.getardaro.com/mcp/documents