Remote MCP · Endpoint

DTMFRAME MCP server

No. DTMFRAME answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://dtmframe.com/mcp/

The last check completed an MCP handshake.

Registry name
com.dtmframe/dtmframe
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
521 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Japan music-production prices: plugins, DAWs, audio gear. Shop comparison, sales and end dates.
Listing
From the official MCP registry (active).
Recent checks of DTMFRAME
CheckedResultHandshake
1 hour agoHandshake completed521 ms
2 days agoHandshake completed527 ms
4 days agoHandshake completed517 ms
6 days agoHandshake completed517 ms
7 days agoHandshake completed518 ms
9 days agoHandshake completed512 ms
10 days agoHandshake completed517 ms
11 days agoHandshake completed537 ms
14 days agoHandshake completed505 ms
15 days agoHandshake completed521 ms
17 days agoHandshake completed522 ms
18 days agoHandshake completed520 ms
19 days agoHandshake completed519 ms
20 days agoHandshake completed740 ms
21 days agoHandshake completed531 ms
22 days agoHandshake completed752 ms

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

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