Supplier Payment Decision Agent (Ireland) MCP server
io.github.LKennedyShare/supplier-payment-verifierLKennedySharestreamable-httpv0.6.0Scanned
Free daily IBAN, VIES VAT and CRO checks; paid invoice decisions. x402. Never moves invoice money.
8 tools: 2 do something that can't be undone, 4 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
6 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Supplier Payment Decision Agent (Ireland) MCP server can do
The Supplier Payment Decision Agent (Ireland) MCP server is published by the GitHub account LKennedyShare. It has 8 tools. It can do things that cannot be undone, such as sending, paying or publishing (verify_supplier_payment and decide_supplier_payment) and create or change data (4 tools: check_iban, check_company, check_three_way_match and register_signing_key), but cannot delete data. 2 tools only read.
1 tool brings in text other people can write (get_verification).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 3, 2026, version 0.6.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Can't be undone 2Claude Code: ask
decide_supplier_paymentFlagship.No findings
Why it is in this group
- The name "decide_supplier_payment" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
verify_supplier_paymentUse for supplier identity and VAT reconciliation, not the full signed five-gate invoice decision.No findings
Why it is in this group
- The name "verify_supplier_payment" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Changes things 4Claude Code: ask
check_companyLooks up an Irish company by CRO number in the Companies Registration Office open data.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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: 1 attempts per UTC day per IP, shared REST/MCP; failures count. Then 0.01 USDC with explicit approval.
check_ibanCheapest call.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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: 1 attempts per UTC day per IP, shared REST/MCP; failures count. Then 0.005 USDC with explicit approval.
check_three_way_matchChecks that a purchase order, goods receipt and invoice agree on supplier, currency, amount, line items, unit prices and quantities received.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
register_signing_keyRegisters an RSA public key (2048-bit or larger, PEM) used to sign payment-decision requests.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 2Show 2 read-only tools
check_vatValidates the Irish VAT number format and check letter, then confirms registration live with EU VIES.No findings
Why it is in this group
- The description's first verb is "validate": a word for reading.
Description, as the server wrote it 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: 1 attempts per UTC day per IP, shared REST/MCP; failures count. Then 0.01 USDC with explicit approval.
get_verificationRead an existing identity/VAT verification created by verify_supplier_payment (POST /v1/verifications).Reads text others writeNo findings
Why it is in this group
- The name "get_verification" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "read" and "post": it reads posts, which other people can write.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:59 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 404
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 404.
Posture changes
- Nov 6, 2026
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 6 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 6 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 6 to 0
- Protocol version: 2025-06-18 to none
Tools3 changed.~3 changedView diff
- Changed:check_companyChanges thingsdescription
- Changed:check_ibanChanges thingsdescription
- Changed:check_vatOnly readsdescription
Install
Pinned to version 0.6.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http supplier-payment-verifier https://supplier-payment-verifier-production.up.railway.app/mcp/claude mcp add --transport http supplier-payment-verifier https://supplier-payment-verifier-production.up.railway.app/mcp/Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__supplier-payment-verifier__get_verification",
"mcp__supplier-payment-verifier__check_vat"
],
"ask": [
"mcp__supplier-payment-verifier__verify_supplier_payment",
"mcp__supplier-payment-verifier__check_iban",
"mcp__supplier-payment-verifier__check_company",
"mcp__supplier-payment-verifier__check_three_way_match",
"mcp__supplier-payment-verifier__decide_supplier_payment",
"mcp__supplier-payment-verifier__register_signing_key"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as supplier-payment-verifier. Review it before you use it.
Capability tags behind 1 rule
- mcp__supplier-payment-verifier__get_verification untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.LKennedyShare/supplier-payment-verifier/verify?hash=8db632b83f346f746c7736f5a3f25b14232eb6c3956462d9812bc6a1350f19b1" | jq -e '.changed == false'Pinned hash 8db632b83f34, from Nov 3, 2026, 08:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.LKennedyShare/supplier-payment-verifier/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.LKennedyShare/supplier-payment-verifier)Source: MCP Registry. Synced Oct 21, 2026, 18:17 UTC.
Supplier Payment Decision Agent (Ireland) MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Supplier Payment Decision Agent (Ireland) MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Supplier Payment Decision Agent (Ireland) MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Supplier Payment Decision Agent (Ireland) MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: verify_supplier_payment and decide_supplier_payment.
What tools does the Supplier Payment Decision Agent (Ireland) MCP server have?
- 8 tools: 2 irreversible, 4 write, 2 read. verify_supplier_payment, decide_supplier_payment, check_iban, check_company, check_three_way_match, register_signing_key, get_verification and check_vat.
Does the Supplier Payment Decision Agent (Ireland) MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Supplier Payment Decision Agent (Ireland) MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Supplier Payment Decision Agent (Ireland) MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 3, 2026. Every change is on this page and in its Atom feed.