Remote MCP · Endpoint

Dutify MCP server

No. Dutify answered an MCP handshake 3 days ago.

UpLast checked 3 days ago

Server URL

https://mcp.dutify.ai/

The last check completed an MCP handshake.

Registry name
io.github.dutifyai/dutify
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
60 ms
Tools exposed
191 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Whole Dutify suite in one server: Hub call recordings, projects, Codexum wiki, Roadmarq requests.
Listing
From the official MCP registry (active).
Recent checks of Dutify
CheckedResultHandshake
3 days agoHandshake completed60 ms
7 days agoHandshake completed53 ms
16 days agoHandshake completed79 ms
17 days agoHandshake completed72 ms
18 days agoHandshake completed76 ms
19 days agoHandshake completed130 ms
21 days agoHandshake completed62 ms
21 days agoHandshake completed104 ms
22 days agoHandshake completed46 ms
24 days agoHandshake completed112 ms
26 days agoHandshake completed39 ms
28 days agoHandshake completed65 ms

The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.

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