Free, read-only security scanner for remote MCP servers, before you connect them.
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.kadent.so/scan/mcp1 tool · 92msscan_mcp_serverRuns a free, read-only security scan of a remote MCP server before you connect it. Performs an ordinary MCP handshake (never anything more invasive), lists the server's tools, rates each one's capabilities (private-data access, untrusted content, network egress, destructive actions), flags prompt-i…Runs a free, read-only security scan of a remote MCP server before you connect it. Performs an ordinary MCP handshake (never anything more invasive), lists the server's tools, rates each one's capabilities (private-data access, untrusted content, network egress, destructive actions), flags prompt-i…
| Parameter | Type | Description |
|---|---|---|
| url* | string | The https:// URL of the remote MCP server to scan |
1 of 1 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.
Free, read-only security scanner for remote MCP servers, before you connect them.
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.