Remote MCP · Endpoint

DNSimple MCP by usefulapi MCP server

No. DNSimple MCP by usefulapi answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://dnsimple.usefulapi.io/mcp

The last check completed an MCP handshake.

Registry name
io.usefulapi/dnsimple
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
172 ms
Tools exposed
12 tools
Uptime, last 30 days
72.2% from 18 checks
Described by its publisher as
MCP server for DNSimple — domains, DNS zone records, availability, pricing and contacts.
Listing
From the official MCP registry (active).
Recent checks of DNSimple MCP by usefulapi
CheckedResultHandshake
1 hour agoHandshake completed172 ms
2 days agoHandshake completed212 ms
4 days agoHandshake completed182 ms
6 days agoHandshake completed62 ms
7 days agoHandshake completed331 ms
9 days agoHandshake completed206 ms
10 days agoHandshake completed419 ms
11 days agoHandshake completed305 ms
14 days agoFailed - the check failed for an unclassified reason—
15 days agoHandshake completed282 ms
17 days agoHandshake completed346 ms
19 days agoFailed - the check failed for an unclassified reason—
20 days agoHandshake completed231 ms
21 days agoFailed - the check failed for an unclassified reason—
22 days agoFailed - the check failed for an unclassified reason—
22 days agoFailed - the check failed for an unclassified reason—
23 days agoHandshake completed232 ms
25 days agoHandshake completed156 ms

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

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