OpenUptime

MCP server checker

Check a remote MCP server: whether it answers initialize, which transport and protocol version it uses, and which tools it lists.

MCP 服务器检测

检测远程 MCP 服务器:是否响应 initialize、使用哪种传输方式和协议版本,以及列出了哪些工具。

Sends initialize and tools/list, at most 10 seconds in all, without credentials. No tool is called. Only public http and https addresses on the default ports.发送 initialize 和 tools/list,总共最多 10 秒,不带凭据,不调用任何工具。只支持默认端口上的公网 http 和 https 地址。

What the checker shows

  • Verdict: Working, asks for authentication, timed out, not an MCP server, or the error that stopped it.
  • Transport: Streamable HTTP or the older HTTP+SSE, and the protocol version the server agreed to.
  • Tools: The name and description of each tool the server lists, up to 100.
  • Time: How long the whole exchange took.

When the check fails

  • 401 or 403: The server needs a token. Check it from an MCP monitor, which can send the header or sign in with OAuth.
  • Not an MCP server: Try the path the server's docs give, often /mcp, or /sse for older servers.
  • Timed out: The server took more than 10 seconds, often while starting up on a serverless host.
  • No tools: The server answered but lists none. Check its configuration or the account it runs as.

Know when your MCP server breaks agents

Agents fail quietly when a server goes down, starts asking for a new token or renames a tool. An OpenUptime MCP monitor runs the same exchange on a schedule, can require tools to exist and can alert you when a tool's schema changes.

Questions

What does the checker do?

It connects to the address as an MCP client would: it sends initialize over Streamable HTTP, falling back to the older HTTP+SSE transport, then lists the server's tools. It does not call any tool.

My server needs a token. Can I check it here?

No; this page sends no credentials and reports that the server asks for them. An MCP monitor in OpenUptime can send a bearer token or another header, or sign in with OAuth client credentials or a refresh token.

What does "not an MCP server" mean?

The address answered over HTTP, but not with an MCP initialize result. The path is often wrong: many servers listen on /mcp, and older ones on /sse.

Which protocol versions are supported?

The checker offers the current MCP protocol version and accepts the earlier ones a server may answer with. The version the server agreed to is shown in the result.

Can OpenUptime alert me when a tool disappears or changes?

Yes. An MCP monitor lists the tools on every check, can require some of them to exist and can call one tool and check its result. With schema monitoring on, it compares each tool's schema with the first good check, and a breaking change can fail the check or only be recorded, as you choose.

检测结果包含什么

  • 结论: 正常、要求认证、超时、不是 MCP 服务器,或导致失败的错误。
  • 传输方式: Streamable HTTP 或较早的 HTTP+SSE,以及服务器协商的协议版本。
  • 工具: 服务器列出的每个工具的名称和说明,最多 100 个。
  • 耗时: 整个交互所用的时间。

检测失败时

  • 401 或 403: 服务器需要令牌。请用 MCP 监控检测,它可以发送请求头或通过 OAuth 登录。
  • 不是 MCP 服务器: 试试服务器文档给出的路径,通常是 /mcp,较早的服务器是 /sse。
  • 超时: 服务器用了超过 10 秒,常见于 Serverless 平台冷启动时。
  • 没有工具: 服务器有响应但没有列出工具。检查它的配置或运行时使用的账号。

MCP 服务器影响智能体时第一时间知道

服务器宕机、开始要求新令牌或改了工具名时,智能体会悄无声息地失败。OpenUptime 的 MCP 监控会按计划进行同样的交互,可以要求某些工具必须存在,也可以在工具 Schema 变化时提醒你。

常见问题

这个工具做了什么?

它像 MCP 客户端一样连接这个地址:通过 Streamable HTTP 发送 initialize,不行时退回到旧的 HTTP+SSE 传输方式,然后列出服务器的工具。它不会调用任何工具。

我的服务器需要令牌,能在这里检测吗?

不能。这个页面不发送任何凭据,只会告诉你服务器要求认证。OpenUptime 的 MCP 监控可以发送 Bearer 令牌或其他请求头,也可以用 OAuth 客户端凭据或刷新令牌登录。

“不是 MCP 服务器”是什么意思?

这个地址有 HTTP 响应,但返回的不是 MCP 的 initialize 结果。通常是路径不对:很多服务器监听 /mcp,较早的监听 /sse。

支持哪些协议版本?

检测工具会提供当前的 MCP 协议版本,也接受服务器返回的较早版本。服务器最终协商的版本会显示在结果里。

工具消失或变化时,OpenUptime 能提醒我吗?

可以。MCP 监控每次检测都会列出工具,可以要求某些工具必须存在,还能调用某个工具并检查结果。开启 Schema 监控后,它会把每个工具的 Schema 与第一次成功的检测对比,破坏性变化可以设为让检测失败,也可以只做记录。