Remote MCP · Endpoint

com.datavrn/schedule-iii MCP server

No. com.datavrn/schedule-iii answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://app.datavrn.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.datavrn/schedule-iii
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
432 ms
Tools exposed
68 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Deterministic Schedule III statements for Indian companies: trial balance in, Excel workbook out.
Website
https://app.datavrn.com/agents
Listing
From the official MCP registry (active).
Recent checks of com.datavrn/schedule-iii
CheckedResultHandshake
2 hours agoHandshake completed432 ms
1 day agoHandshake completed1.97 s
3 days agoHandshake completed376 ms
3 days agoHandshake completed400 ms
4 days agoHandshake completed1.37 s
5 days agoHandshake completed550 ms
7 days agoHandshake completed372 ms
10 days agoHandshake completed336 ms
12 days agoHandshake completed291 ms
15 days agoHandshake completed336 ms
17 days agoHandshake completed377 ms
19 days agoHandshake completed340 ms
21 days agoHandshake completed665 ms
23 days agoHandshake completed383 ms
25 days agoHandshake completed284 ms
26 days agoHandshake completed327 ms
28 days agoHandshake completed291 ms
29 days agoHandshake completed329 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 com.datavrn/schedule-iii and makes no claim about it beyond what these checks measured.