Remote MCP · Endpoint

Borrower Operations — Loan Application Review — Fenwick & Rowe Operations (61b5d8c8) MCP server

No. Borrower Operations — Loan Application Review — Fenwick & Rowe Operations (61b5d8c8) answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://a2awire.com/mcp/benchmarks/loan-application-review-2026-09-11-61b5d8c8/http

The last check completed an MCP handshake.

Registry name
com.a2awire/benchmark-loan-application-review-2026-09-11-61b5d8c8
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
248 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
12 synthetic loan application exception cases: duplicate payments, policy-watch list entries, missin
Website
https://a2awire.com/benchmarks/loan-application-review-2026-09-11-61b5d8c8
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of Borrower Operations — Loan Application Review — Fenwick & Rowe Operations (61b5d8c8)
CheckedResultHandshake
2 hours agoHandshake completed248 ms
2 days agoHandshake completed48 ms
4 days agoHandshake completed44 ms
6 days agoHandshake completed36 ms
7 days agoHandshake completed86 ms
8 days agoHandshake completed38 ms
9 days agoHandshake completed261 ms
12 days agoHandshake completed424 ms
14 days agoHandshake completed310 ms
15 days agoHandshake completed161 ms
17 days agoHandshake completed420 ms
18 days agoHandshake completed142 ms
19 days agoHandshake completed234 ms
20 days agoHandshake completed3.09 s
20 days agoHandshake completed143 ms
22 days agoHandshake completed303 ms
23 days agoHandshake completed186 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 Borrower Operations — Loan Application Review — Fenwick & Rowe Operations (61b5d8c8) and makes no claim about it beyond what these checks measured.