Health monitoring for all your MCP servers
MCP-native health monitoring that speaks the protocol, not just HTTP. Instead of pinging a port, it calls on each server — the same handshake your agent uses — so a green status means the server is actually ready to serve MCP requests. All health history stays local in SQLite; no external monitoring service required. Tool reference | Configuration | Contributing | Troubleshooting Auto-discovery:…
Inferred from the transports this listing declares (stdio). 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 out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
health_check_allNo description publishedThis tool published no description. Forge does not invent one.
get_server_statusNo description publishedThis tool published no description. Forge does not invent one.
list_degradedNo description publishedThis tool published no description. Forge does not invent one.
check_updatesNo description publishedThis tool published no description. Forge does not invent one.
export_dashboardNo description publishedThis tool published no description. Forge does not invent one.
get_historyNo description publishedThis tool published no description. Forge does not invent one.
configure_serverNo description publishedThis tool published no description. Forge does not invent one.
remove_serverprivilegedNo description publishedThis tool published no description. Forge does not invent one.
0 of 8 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.
MCP-native health monitoring that speaks the protocol, not just HTTP. Instead of pinging a port, it calls on each server — the same handshake your agent uses — so a green status means the server is actually ready to serve MCP requests. All health history stays local in SQLite; no external monitoring service required. Tool reference | Configuration | Contributing | Troubleshooting Auto-discovery: Reads your existing MCP config files (Claude Desktop, Cursor, VS Code) with no extra setup.…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.