# Editorial policy

URL: https://mcpservercybersecurity.com/editorial-policy/
Updated: 2026-11-16

Every fact on MCP Server Security carries a source URL and a read date, and a vendor's claim is written as the vendor's. Scores follow weights committed before any evidence. Guides contain risks, detection, configuration and fixes only, with no exploit code, payloads or bypass steps. Changes follow a sourced fact or a reported error.

## How are facts sourced?

Facts come from primary pages: the MCP specification, OWASP, GitHub and CVE records, cloud and client documentation, and the vendor's own pages and release notes. Each stored fact keeps the quoted passage, the URL, the read date and its kind: vendor, third-party, observed or none found.

Where evidence is missing the page says none found on the read date. It does not infer a capability from silence.

## How are vendor claims handled?

A vendor's claim is attributed, for example Zenity says or per Microsoft's documentation. A claim alone earns at most 7 of 10 on any criterion, and a higher score needs a second source such as third-party reporting or something observed in public documentation or code.

Each vendor's strength is stated fairly, and each page lists the gaps the documentation shows.

## What will the guides not contain?

Guides describe risks, how to detect them, configuration and fixes. They carry no exploit code, no prompt-injection payloads and no steps to bypass a control.

## When do pages change?

A score changes only when a sourced fact changes, and the change is logged with the fact. Weights and criteria stay fixed after the first score. Corrections are described on the corrections page.

## Related pages

- [Method](/method/)
- [Corrections](/corrections/)
- [The ranking](/ranking/)
- [FAQ](/faq/)
