Remote MCP · Endpoint

com.dropwatchhq/payer-api-directory MCP server

No. com.dropwatchhq/payer-api-directory answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://clearinghouse.dropwatchhq.com/mcp

The last check completed an MCP handshake.

Registry name
com.dropwatchhq/payer-api-directory
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
50 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Directory of US clearinghouse/payer APIs (Availity, Optum, Waystar) with pricing & access signals.
Website
https://clearinghouse.dropwatchhq.com/
Listing
From the official MCP registry (active).
Recent checks of com.dropwatchhq/payer-api-directory
CheckedResultHandshake
1 hour agoHandshake completed50 ms
2 days agoHandshake completed66 ms
4 days agoHandshake completed46 ms
5 days agoHandshake completed51 ms
7 days agoHandshake completed53 ms
8 days agoHandshake completed296 ms
9 days agoHandshake completed62 ms
12 days agoHandshake completed36 ms
13 days agoHandshake completed60 ms
15 days agoHandshake completed61 ms
16 days agoHandshake completed97 ms
17 days agoHandshake completed44 ms
18 days agoHandshake completed38 ms
19 days agoHandshake completed51 ms
20 days agoHandshake completed60 ms
21 days agoHandshake completed75 ms
22 days agoHandshake completed43 ms

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

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 com.dropwatchhq/payer-api-directory and makes no claim about it beyond what these checks measured.