Check an MCP endpoint resolves: liveness, live tool list, schema drift. Free.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://mcp-uptime.theopslog.workers.dev/mcp4 tools · 477mscheck_mcp_endpointProbe an MCP endpoint right now: is it alive, which transport it speaks, how many tools it exposes, and whether its tool schema changed since the last check. Use before depending on a third-party MCP server.Probe an MCP endpoint right now: is it alive, which transport it speaks, how many tools it exposes, and whether its tool schema changed since the last check. Use before depending on a third-party MCP server.
| Parameter | Type | Description |
|---|---|---|
| url* | string | Public http(s) URL of the MCP endpoint to inspect. |
| include_tools | boolean | Return the full tool list, not just the count. |
get_uptimeUptime history for an MCP endpoint over the last N days (max 30), with incident windows. Reads stored history; does not probe.Uptime history for an MCP endpoint over the last N days (max 30), with incident windows. Reads stored history; does not probe.
| Parameter | Type | Description |
|---|---|---|
| url* | string | Public http(s) URL of the MCP endpoint to inspect. |
| days | integer | Window in days. Default 30. |
get_known_toolsThe tool list last observed at an MCP endpoint, with the timestamp of the most recent schema change. Reads stored history; does not probe.The tool list last observed at an MCP endpoint, with the timestamp of the most recent schema change. Reads stored history; does not probe.
| Parameter | Type | Description |
|---|---|---|
| url* | string | Public http(s) URL of the MCP endpoint to inspect. |
check_schema_driftProbe an MCP endpoint and diff its tool schema against the last stored snapshot: tools added, removed, or whose description/inputSchema changed. Schema drift fails quietly mid-run, which is why it is worth checking.Probe an MCP endpoint and diff its tool schema against the last stored snapshot: tools added, removed, or whose description/inputSchema changed. Schema drift fails quietly mid-run, which is why it is worth checking.
| Parameter | Type | Description |
|---|---|---|
| url* | string | Public http(s) URL of the MCP endpoint to inspect. |
4 of 4 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Check an MCP endpoint resolves: liveness, live tool list, schema drift. Free.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.