Remote MCP · Endpoint

Supplier Identity and VAT Verification MCP server

No. Supplier Identity and VAT Verification answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://supplier-payment-verifier-production.up.railway.app/mcp/

The last check completed an MCP handshake.

Registry name
io.github.LKennedyShare/supplier-payment-verifier
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
27 ms
Tools exposed
2 tools
Uptime, last 30 days
1 check from 1 check
Described by its publisher as
Verify a supplier's identity and VAT via Irish CRO and EU VIES before paying. Pay per call, x402.
Listing
From the official MCP registry (active).
Recent checks of Supplier Identity and VAT Verification
CheckedResultHandshake
1 day agoHandshake completed27 ms

The last 1 check. Full history is kept for 30 days; the all-time counter stands at 1 responding of 1.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Supplier Identity and VAT Verification and makes no claim about it beyond what these checks measured.