Remote MCP · Endpoint

MinutesMaster MCP server

No — it is up, but it requires credentials. MinutesMaster answered 4 days ago with an authentication challenge rather than a session.

Auth requiredLast checked 4 days ago

Server URL

https://api.minutesmaster.ai/mcp

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
ai.minutesmaster/minutesmaster
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Behind credentials
Uptime, last 30 days
1 check from 1 check
Described by its publisher as
Meeting transcripts & AI minutes for your agent: search, read, send meeting bots, import.
Listing
From the official MCP registry (active).
Recent checks of MinutesMaster
CheckedResultHandshake
4 days agoCredentials required—

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

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