Correctover

com.correctoverPublished by correctover.comv1.2.3Updated Oct 27, 2026

MCP runtime security. 22µs validation, 97% self-healing. Detects RCE, SSRF, credential hijacking.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Correctover is a local MCP runtime security server that validates tool calls and detects RCE, SSRF and credential hijacking.

What you can do
  • The registry lists no tools, so capabilities come from the description only.
  • It positions itself as security for the MCP runtime, checking activity as an assistant uses tools.
  • It advertises fast validation (22µs) and a 97% self-healing rate.
  • It claims to detect remote code execution, server-side request forgery and credential hijacking.
When to use it
Worth considering if you run MCP servers locally and want an extra validation layer over tool calls, especially where code execution, outbound requests or credentials are involved. The description gives no setup or integration detail, so evaluate it against your own threat model first.
Requirements
Runs as a local process over stdio, installed from the npm package correctover-mcp-server, so Node.js is needed. No authentication, environment variables or headers are declared. Desktop only; not available as a web executable.
Before you install
The description makes strong performance and detection claims (22µs validation, 97% self-healing) with no README, tool list or documentation to verify them. No tools are listed, so what it actually inspects or changes is unclear. Treat it as unverified until you review the package yourself.

Installation

In SourceWeft

  1. Open Correctover in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.2.3LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

  • License10 pts

    Declare a license in the repository or the registry entry.