Remote MCP · Endpoint

Invoice Duplicate Recovery MCP server

No. Invoice Duplicate Recovery answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp-factory.bowling-anthony.workers.dev/invoice-duplicate-recovery/mcp

The last check completed an MCP handshake.

Registry name
com.mcpscores/invoice-duplicate-recovery
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
149 ms
Tools exposed
1 tool
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
Computes exact overpayments across caller-supplied approved invoices, payments, and recorded cred...
Website
https://mcp-factory.bowling-anthony.workers.dev/invoice-duplicate-recovery
Listing
From the official MCP registry (active).
Recent checks of Invoice Duplicate Recovery
CheckedResultHandshake
2 hours agoHandshake completed149 ms
1 day agoHandshake completed82 ms
3 days agoHandshake completed155 ms
3 days agoHandshake completed119 ms
4 days agoHandshake completed101 ms
5 days agoHandshake completed102 ms
7 days agoFailed - the request timed out—
10 days agoHandshake completed158 ms
12 days agoHandshake completed99 ms
15 days agoHandshake completed119 ms
17 days agoHandshake completed126 ms
19 days agoHandshake completed325 ms
21 days agoHandshake completed158 ms
23 days agoHandshake completed345 ms
25 days agoHandshake completed80 ms
26 days agoHandshake completed101 ms
28 days agoHandshake completed283 ms
29 days agoHandshake completed118 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 29.

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 Invoice Duplicate Recovery and makes no claim about it beyond what these checks measured.