Remote MCP · Endpoint
com.eformogi/records-vault MCP server
No. com.eformogi/records-vault answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://eformogi.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- com.eformogi/records-vault
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 255 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- The family's agent reads the record, drafts the filing from verified rules, asks for a signature.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 255 ms |
| 18 hours ago | Handshake completed | 202 ms |
| 2 days ago | Handshake completed | 243 ms |
| 3 days ago | Handshake completed | 453 ms |
| 4 days ago | Handshake completed | 164 ms |
| 5 days ago | Handshake completed | 465 ms |
| 6 days ago | Handshake completed | 335 ms |
| 7 days ago | Handshake completed | 361 ms |
| 10 days ago | Handshake completed | 833 ms |
| 13 days ago | Handshake completed | 252 ms |
| 15 days ago | Handshake completed | 183 ms |
| 17 days ago | Handshake completed | 222 ms |
| 19 days ago | Handshake completed | 812 ms |
| 21 days ago | Handshake completed | 200 ms |
| 23 days ago | Handshake completed | 155 ms |
| 25 days ago | Handshake completed | 304 ms |
| 27 days ago | Handshake completed | 159 ms |
| 28 days ago | Handshake completed | 594 ms |
| 29 days ago | Handshake completed | 431 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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.
Listing data comes from the official MCP registry. Glide is not affiliated with com.eformogi/records-vault and makes no claim about it beyond what these checks measured.