# How the MCP Risk Register is built

URL: https://mcpservercybersecurity.com/mcp-risk-register/methodology/
Updated: 2026-11-16

The register lists 42 risks across six dimensions for MCP servers. Every row carries what the risk is, its impact, controls, a severity set by one written rule, and primary sources read on 16 Nov 2026. It is released under CC BY 4.0, and the sections below say how to cite it and report corrections.

## What the register is

The register is a list of 42 risks that affect MCP servers and the clients that run them, grouped into six dimensions: supply chain, authorization, transport and network, tool descriptions and schemas, execution and filesystem, and data exposure and logging. Rows are written for a platform or security engineer whose developers install MCP servers.

A row describes a risk class and its fixes. It carries no exploit code, payloads or bypass steps.

Sources: [MCP Security Best Practices, 2026-07-28 revision](https://modelcontextprotocol.io/specification/2026-07-28/basic/security_best_practices); [OWASP MCP Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/MCP_Security_Cheat_Sheet.html).

## Sources and read date

Every row cites at least one primary source: the MCP specification and its security pages, the OWASP MCP Security Cheat Sheet, GitHub security advisories and CVE records, release notes from the maintainers, or research published by the named lab or vendor. All pages were fetched and read on 16 Nov 2026 (read date 2026-11-16), and only pages that returned HTTP 200 are cited.

Vendor research is described as the vendor's own account. The 2026-07-28 MCP revision is the reference for spec statements; where an older revision differs, the row says so.

Sources: [MCP Security Best Practices, 2026-07-28 revision](https://modelcontextprotocol.io/specification/2026-07-28/basic/security_best_practices); [MCP Authorization, 2026-07-28 revision](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization); [OWASP MCP Top 10](https://owasp.org/www-project-mcp-top-10/).

## Severity rule

Severity follows one rule applied to every row. High: the risk can lead to code execution on a machine, theft of a credential, or access to data or tools without authentication, and it needs no more than normal use of the server (installing it, connecting to it, visiting a web page, or leaving it reachable). Medium: the same kinds of impact, but a precondition is needed, such as a particular configuration, a specific transport, an authenticated caller or a second flaw. Low: the impact is loss of availability or a weakness that matters only alongside another risk.

Applied on 16 Nov 2026 the register has 19 high, 21 medium and 2 low rows. The rule is about the class of risk, not about any single product, and a given deployment may be more or less exposed.

Sources: [MCP Security Best Practices, 2026-07-28 revision](https://modelcontextprotocol.io/specification/2026-07-28/basic/security_best_practices).

## How to cite

Cite as: MCP Risk Register, MCP Server Security, edition of 16 Nov 2026, https://mcpservercybersecurity.com/mcp-risk-register/, licensed CC BY 4.0. Cite a row by its identifier (for example R-08) and the edition date.

## License

The register text and the downloadable CSV and JSON files are released under Creative Commons Attribution 4.0 International (CC BY 4.0). You may copy and adapt them with credit and a link to the license.

## Corrections

If a source has changed, a row is wrong or a risk is missing, use the corrections page on this site. Corrections are dated and listed there, and the register edition date changes when rows change.

## Counts

- 42 items in 6 categories.
- 19 with severity high.
- 21 with severity medium.
- 2 with severity low.

## Related pages

- [The MCP Risk Register](/mcp-risk-register/)
- [MCP Risk Register download](/datasets/mcp-risk-register/)
- [Scoring method](/method/)
- [Supply chain](/mcp-risk-register/supply-chain/)
- [Authorization](/mcp-risk-register/authorization/)
- [Transport and network](/mcp-risk-register/transport-and-network/)
