Remote MCP · Endpoint

Tenor MCP server

No. Tenor answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/tenor/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/tenor
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
97 ms
Tools exposed
51 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
Tenor v2 MCP.
Listing
From the official MCP registry (active).
Recent checks of Tenor
CheckedResultHandshake
1 hour agoHandshake completed97 ms
19 hours agoHandshake completed177 ms
2 days agoHandshake completed148 ms
3 days agoHandshake completed99 ms
4 days agoHandshake completed114 ms
5 days agoHandshake completed185 ms
6 days agoHandshake completed109 ms
8 days agoHandshake completed168 ms
11 days agoHandshake completed67 ms
13 days agoHandshake completed362 ms
15 days agoHandshake completed95 ms
18 days agoHandshake completed84 ms
20 days agoHandshake completed72 ms
22 days agoHandshake completed83 ms
24 days agoHandshake completed73 ms
26 days agoFailed - the request timed out—
27 days agoHandshake completed1.11 s
29 days agoHandshake completed127 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 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.

Listing data comes from the official MCP registry. Glide is not affiliated with Tenor and makes no claim about it beyond what these checks measured.