Corrections

Last updated: June 2026

MCP Verdict maintains a public correction log. When we publish something wrong, we fix it, note the change, and log it here. This page is the record.

How to report an error

Email contact@mcpverdict.com with the subject line “Correction.” Include:

The URL of the page with the error. The specific claim you believe is wrong. Your source or evidence — a link to the repository, documentation, changelog, or other primary source that contradicts what we published.

Corrections are prioritized over all other inquiries. If the error is confirmed, the fix is typically published within 48 hours.

What happens when an error is confirmed

The content is updated with the correct information. A correction notice is added to the affected page noting what was changed and when. The correction is added to the log below. The person who reported the error is credited if they want to be.

Substantive corrections — factual errors, changed verdicts, revised rankings, incorrect security information — always get a correction notice and a log entry. Minor corrections — typos, broken links, formatting — are fixed directly without a formal notice.

What counts as a substantive correction

A factual claim that was wrong (incorrect token cost, wrong authentication method, inaccurate maintenance status). A verdict or ranking that changed because the underlying facts were wrong. A security note that was missing or inaccurate. A setup instruction that produces an error or fails to work as described. An attribution error (wrong source, wrong date, wrong version).

Correction log

No corrections have been issued yet. This log will be updated as corrections are published.