Remote MCP · Endpoint

Voice Agent Linter MCP server

No. Voice Agent Linter answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.modernmustardseed.com/voice-linter

The last check completed an MCP handshake.

Registry name
com.modernmustardseed/voice-linter
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
53 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Lints a phone voice agent prompt and platform config before real callers reach it.
Listing
From the official MCP registry (active).
Recent checks of Voice Agent Linter
CheckedResultHandshake
1 hour agoHandshake completed53 ms
1 day agoHandshake completed30 ms
2 days agoHandshake completed99 ms
3 days agoHandshake completed171 ms
4 days agoHandshake completed64 ms
5 days agoHandshake completed28 ms
6 days agoHandshake completed73 ms
9 days agoHandshake completed26 ms
11 days agoHandshake completed75 ms
14 days agoHandshake completed81 ms
16 days agoHandshake completed87 ms
18 days agoHandshake completed45 ms
20 days agoHandshake completed70 ms
22 days agoHandshake completed75 ms
24 days agoHandshake completed41 ms

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

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