Lets an assistant run live HTTP health checks on an MCP server and list recent scan results from the official registry.
What you can do
The check_mcp_server tool diagnoses whether an MCP server passes directory health checks by running five real HTTP probes: modern initialize, legacy initialize, anonymous tools/list, unauthorized tools/call, and WWW-Authenticate/resource_metadata. It returns findings together with suggested fixes. The list_scan_results tool lists the most recent scan results across MCP servers taken from the official registry, with verdicts and issue counts.
When to use it
Useful when publishing or maintaining an MCP server and you want to confirm it is reachable and passes directory health checks before listing it. Also handy for reviewing recent registry-wide scan verdicts and issue counts.
Requirements
A remote streamable HTTP endpoint at mcp-health.rowb.app; no packages, authentication, environment variables or headers are declared. Network access to the endpoint and to the servers being probed is needed.
Before you install
The server performs live HTTP probes against MCP servers, including an unauthorized tools/call attempt, so only point it at servers you are authorized to test. Scan results come from the official registry and reflect third-party servers.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/app.rowb.mcp-health%2Fprobe/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Diagnose whether an MCP server passes directory health checks. Runs five real HTTP probes (modern initialize, legacy initialize, anonymous tools/list, unauthorized tools/call, WWW-Authenticate/resource_metadata) and returns findings with fixes.
Parametersurlrequired
list_scan_results
List the most recent scan results across MCP servers taken from the official registry, with verdicts and issue counts.
Parameterslimitverdict
Version history
1
v1.0.0LatestSep 26, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.