Zenable

app.zenablePublished by zenable.appOfficial publisherv2.0.0Updated Oct 24, 2026

Zenable cleans up sloppy AI code and prevents vulnerabilities with deterministic guardrails

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Zenable is a remote MCP server that applies deterministic guardrails to clean up sloppy AI-generated code and prevent vulnerabilities.

What you can do
  • No tool list is published, so capabilities are known only from the short description.
  • The server is presented as a way to check and clean up AI-written code.
  • It applies deterministic guardrails intended to catch sloppy code and prevent vulnerabilities.
  • It runs as a hosted remote endpoint rather than a local package.
When to use it
Worth considering when an assistant generates or edits code and you want an automated, rule-based check for quality problems and security vulnerabilities before the code is used.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. OAuth authentication is required, so you need a Zenable account or authorization to sign in. No environment variables or headers are declared.
Before you install
The server requires OAuth sign-in, so your account identity is shared with the provider. Code submitted for checking is sent to a third-party hosted service. No tool list or documentation is published, so what it can read or change in your code cannot be verified in advance.

Installation

In SourceWeft

  1. Open Zenable in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.zenable%2Fzenable/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "zenable": {
      "type": "http",
      "url": "https://mcp.zenable.app/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

67% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

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