Remote MCP · Endpoint

Healthcare Revenue Cycle — Coded Claim Audit — Fenwick & Rowe Services Group (a7b04acd) MCP server

No. Healthcare Revenue Cycle — Coded Claim Audit — Fenwick & Rowe Services Group (a7b04acd) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://a2awire.com/mcp/benchmarks/coded-claim-audit-2026-09-14-a7b04acd/http

The last check completed an MCP handshake.

Registry name
com.a2awire/benchmark-coded-claim-audit-2026-09-14-a7b04acd
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
56 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
12 synthetic coded claim exception cases: duplicate payments, policy-watch list entries, missing doc
Website
https://a2awire.com/benchmarks/coded-claim-audit-2026-09-14-a7b04acd
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of Healthcare Revenue Cycle — Coded Claim Audit — Fenwick & Rowe Services Group (a7b04acd)
CheckedResultHandshake
1 hour agoHandshake completed56 ms
1 day agoHandshake completed123 ms
2 days agoHandshake completed66 ms
3 days agoHandshake completed54 ms
4 days agoHandshake completed46 ms
5 days agoHandshake completed86 ms
6 days agoHandshake completed34 ms
9 days agoHandshake completed213 ms
12 days agoHandshake completed75 ms
14 days agoHandshake completed87 ms
16 days agoHandshake completed99 ms
18 days agoHandshake completed58 ms
20 days agoHandshake completed40 ms
23 days agoHandshake completed74 ms
25 days agoHandshake completed61 ms
26 days agoHandshake completed44 ms
28 days agoHandshake completed37 ms
29 days agoHandshake completed35 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 Healthcare Revenue Cycle — Coded Claim Audit — Fenwick & Rowe Services Group (a7b04acd) and makes no claim about it beyond what these checks measured.