io.github.LKennedyShare/supplier-payment-verifier

Est-ce que io.github.LKennedyShare/supplier-payment-verifier est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.LKennedyShare/supplier-payment-verifier » 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 8 outils

• check_company≈ 347 tokens

  Looks up an Irish company by CRO number in the Companies Registration Office open data. PASSED only if the company status is NORMAL; dissolved, liquidated or unknown companies FAIL. Returns the registered name. Use a CRO company number, not a company name or VAT number. Source uncertainty returns UNAVAILABLE, not a pass. Use check_vat for VIES registration, verify_supplier_payment for claimed-name/identity reconciliation, or decide_supplier_payment for a complete signed invoice decision. No invoice is approved here. Free: 10 attempts per UTC day per IP, shared REST/MCP; failures count. Then 0.01 USDC with explicit approval.

  Paramètres, retour & exemple (1)

  Paramètres

  • request · ? · requis
    Check an Irish company status (CRO): supply this structured object using the nested schema, not a JSON-encoded string.

  Exemple d'appel

  {"name": "check_company", "arguments": {"request": "texte"}}

  Exemple de retour

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

• check_iban≈ 324 tokens

  Cheapest call. Validates an IBAN (ISO 13616 mod-97 checksum, length and country) before you pay it. Returns PASSED or FAILED with a reason code. Irish (IE) IBANs pass by default. Use only for bank-account identifier syntax/country checks, not account ownership, bank Confirmation of Payee or supplier identity. Use check_vat for VAT registration, check_company for CRO status, and decide_supplier_payment for the complete signed invoice decision. No bank transfer occurs. Free: 10 attempts per UTC day per IP, shared REST/MCP; failures count. Then 0.005 USDC with explicit approval.

  Paramètres, retour & exemple (1)

  Paramètres

  • request · ? · requis
    Validate an IBAN: supply this structured object using the nested schema, not a JSON-encoded string.

  Exemple d'appel

  {"name": "check_iban", "arguments": {"request": "texte"}}

  Exemple de retour

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

• check_three_way_match≈ 1218 tokens

  Checks that a purchase order, goods receipt and invoice agree on supplier, currency, amount, line items, unit prices and quantities received. Stateless; you attach the documents. Checks caller-supplied documents, not independently verified ERP records. Returns PASSED or FAILED and a reason code; no CRO/VIES lookup, signature validation or bank transfer is performed by this tool. Use decide_supplier_payment when document matching must be combined with supplier identity, VAT, payee and signature checks. Requires an explicitly approved service fee.

  Paramètres, retour & exemple (1)

  Paramètres

  • request · ? · requis
    3-way match PO, goods receipt and invoice: supply this structured object using the nested schema, not a JSON-encoded string.

  Exemple d'appel

  {"name": "check_three_way_match", "arguments": {"request": "texte"}}

  Exemple de retour

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

• check_vat≈ 335 tokens

  Validates the Irish VAT number format and check letter, then confirms registration live with EU VIES. Returns PASSED, FAILED or UNAVAILABLE (VIES outage) with a reason code and available consultation/audit evidence. Use for one VAT number, not company-name matching or invoice approval. check_company checks CRO status; verify_supplier_payment reconciles claimed supplier identity and VAT; decide_supplier_payment runs the full signed invoice workflow. An outage is uncertainty, not invalid registration; do not auto-pay to retry. Free: 10 attempts per UTC day per IP, shared REST/MCP; failures count. Then 0.01 USDC with explicit approval.

  Paramètres, retour & exemple (1)

  Paramètres

  • request · ? · requis
    Check an Irish VAT number: supply this structured object using the nested schema, not a JSON-encoded string.

  Exemple d'appel

  {"name": "check_vat", "arguments": {"request": "texte"}}

  Exemple de retour

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

• decide_supplier_payment≈ 1721 tokens

  Flagship. Independent third-party decision for an Irish supplier invoice. Runs five gates (CRO status NORMAL, EU VIES VAT, payee-name and IBAN check, PO/GRN/invoice 3-way match, RSA signature) and returns exactly one of EXECUTE_PAYMENT, REJECT_PAYMENT or FLAG_FOR_HUMAN_REVIEW with per-check results, reason codes and a confidence score. The legacy CONFIRMATION_OF_PAYEE result means a payee-name comparison with the CRO legal name and IBAN validation, not bank Confirmation of Payee. ERP_THREE_WAY_MATCH compares caller-supplied documents, not independently verified ERP records. Decides only; never moves money. Register a signing key first via /v1/agent-keys. Use this for the complete signed invoice/PO/GRN workflow, not verify_supplier_payment's separate identity/VAT contract or get_verification retrieval. Provider uncertainty requires review, not execution; retain independent payment approval. Supply a stable transaction_id for retries and never automatically repay.

  Paramètres, retour & exemple (1)

  Paramètres

  • payment_request · ? · requis
    Decide: pay this supplier invoice or not: supply this structured object using the nested schema, not a JSON-encoded string.

  Exemple d'appel

  {"name": "decide_supplier_payment", "arguments": {"payment_request": "texte"}}

  Exemple de retour

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

• get_verification≈ 326 tokens

  Read an existing identity/VAT verification created by verify_supplier_payment (POST /v1/verifications). Supply its returned verification_id UUID, not a request_id, transaction_id, invoice number or A2A task ID. Returns the stored RELEASE/REVIEW/BLOCK/INSUFFICIENT_EVIDENCE result without rerunning registry checks. The same authenticated tenant must own the result: use the original paying wallet for x402, or an authorized bearer token with verification.read scope. Missing or other-tenant IDs return not found. This does not retrieve decide_supplier_payment decisions and does not create a verification. Retrieval has its own service fee; inspect terms and obtain spending approval before paying. Do not retry payment automatically or infer invoice-payment authorization from a stored advisory result.

  Paramètres, retour & exemple (1)

  Paramètres

  • verification_id · string · requis
    UUID returned as verification_id by verify_supplier_payment or POST /v1/verifications. Use a result owned by the same tenant/original paying wallet; do not supply request_id, transaction_id, an invoice number or an A2A task ID.

  Exemple d'appel

  {"name": "get_verification", "arguments": {"verification_id": "texte"}}

  Exemple de retour

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

• register_signing_key≈ 292 tokens

  Registers an RSA public key (2048-bit or larger, PEM) used to sign payment-decision requests. Keys are immutable per tenant; rotate by registering a new key_id. Returns key_id and registered=true. Use before decide_supplier_payment and use the same tenant/paying wallet for registration and decision. This is not a supplier check, API-key creation or payment authorization. Keep the RSA private key local; a conflicting existing key_id returns a conflict. Inspect and approve the registration fee before calling.

  Paramètres, retour & exemple (2)

  Paramètres

  • key_id · string · requis
    Caller-chosen RSA public-key identifier, unique within your tenant. Reuse it in signature.key_id; rotate with a new ID.
  • public_key_pem · string · requis
    PEM-encoded RSA public key, at least 2048 bits. Never send a private key, wallet key or certificate.

  Exemple d'appel

  {"name": "register_signing_key", "arguments": {"key_id": "texte", "public_key_pem": "texte"}}

  Exemple de retour

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

• verify_supplier_payment≈ 1832 tokens

  Use for supplier identity and VAT reconciliation, not the full signed five-gate invoice decision. Reconciles the claimed legal name, company registration number and VAT number against the Irish Companies Registration Office (IE) and the EU VIES VAT service, and returns an advisory RELEASE, REVIEW, BLOCK or INSUFFICIENT_EVIDENCE decision with per-check results and reason codes plus verification_id. Use decide_supplier_payment for the signed invoice/PO/GRN workflow, individual check tools for one check, and get_verification only to retrieve this stored result. This creates a verification and may call external sources; it never executes or authorises a bank payment. Requires explicit x402 service-fee approval or an authorized bearer token; do not automatically retry paid calls.

  Paramètres, retour & exemple (11)

  Paramètres

  • callback · ? · optionnel
  • evidence · ? · optionnel
  • metadata · ? · optionnel
  • supplier · ? · requis
    Claimed supplier identity and Irish identifiers to reconcile with CRO/VIES; not the signed invoice-decision supplier object.
  • policy_id · string · requis
    Verification policy identifier; always eu-b2b-payment-v1.
  • request_id · string · requis
    Caller-generated unique request UUID used for idempotency. This is not the returned verification_id used for retrieval.
  • transaction · ? · optionnel
  • requested_at · ? · optionnel
  • schema_version · string · requis
    Request schema version; always the literal string 1.0.
  • customer_assertions · ? · optionnel
  • payment_destination · ? · optionnel

  Exemple d'appel

  {"name": "verify_supplier_payment", "arguments": {"supplier": "texte", "policy_id": "texte", "request_id": "texte", "schema_version": "texte"}}

  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://supplier-payment-verifier-production.up.railway.app/mcp/