Remote MCP · Endpoint

com.datavrn/schedule-iii MCP server

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

UpLast checked 9 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
665 ms
Tools exposed
67 tools
Uptime, last 30 days
100% from 17 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
9 hours agoHandshake completed665 ms
2 days agoHandshake completed383 ms
4 days agoHandshake completed284 ms
5 days agoHandshake completed327 ms
7 days agoHandshake completed291 ms
8 days agoHandshake completed329 ms
9 days agoHandshake completed419 ms
12 days agoHandshake completed372 ms
13 days agoHandshake completed325 ms
15 days agoHandshake completed310 ms
16 days agoHandshake completed437 ms
17 days agoHandshake completed315 ms
19 days agoHandshake completed378 ms
19 days agoHandshake completed307 ms
20 days agoHandshake completed495 ms
21 days agoHandshake completed538 ms
22 days agoHandshake completed1.02 s

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.datavrn/schedule-iii and makes no claim about it beyond what these checks measured.