Kadent Scan

so.kadentPublished by kadent.soOfficial publisherv1.0.0Updated Oct 24, 2026

Free, read-only security scanner for remote MCP servers, before you connect them.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

A free, read-only security scanner that lets an assistant inspect a remote MCP server's tools and risk profile before you connect it.

What you can do
Scan a remote MCP server: performs an ordinary MCP handshake, lists its tools and rates each tool's capabilities such as private-data access, untrusted content, network egress and destructive actions, flagging prompt-injection risks.
When to use it
Use it when you are considering connecting an unfamiliar remote MCP server and want a quick read-only assessment of what its tools can do before trusting it.
Requirements
A remote endpoint at mcp.kadent.so over streamable HTTP; no authentication, environment variables or headers are declared. The target server must be reachable remotely.
Before you install
The scan connects to the third-party server you name, so that server sees the handshake. Results are a capability rating, not a guarantee of safety; treat them as one input before connecting.

Installation

In SourceWeft

  1. Open Kadent Scan in the dashboard and add it to a workspace.
  2. 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/so.kadent%2Fkadent-scan/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "kadent-scan": {
      "type": "http",
      "url": "https://mcp.kadent.so/scan/mcp"
    }
  }
}

Tools

1

scan_mcp_server

Scan an MCP server for security risks

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-injection patterns in tool descriptions, and reports whether the lethal trifecta is reachable. Scan only servers you run or are entitled to connect to.

Parametersurlrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% 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
  • 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.