# MCP security controls

This bundle maps dated MCP requirements and OWASP guidance to deployment
controls, verification procedures, and release evidence. It is meant for a
real review: each control says what to test and what artifact should prove the
result.

The matrix targets MCP revision `2026-07-28`. The protocol moves, so check the
source links and revision before carrying the controls into a later release.

## Files

- `mcp-security-controls.json` contains the machine-readable matrix.
- `mcp-security-controls.schema.json` defines its portable shape.
- `validate-controls.ts` applies checks that JSON Schema cannot express.
- `validate-controls_test.ts` covers valid and broken matrix cases.
- `deployment-checklist.md` is the English release checklist.
- `deployment-checklist.ru.md` is the Russian release checklist.

## Run

```bash
deno check validate-controls.ts validate-controls_test.ts
deno test --allow-read=mcp-security-controls.json validate-controls_test.ts
```

The validator uses no network access, environment variables, or third-party
packages. The tests do not contact an MCP server. They verify the matrix
structure and source discipline, not a deployment.

## Source boundary

Each source is marked as a specification, official MCP guidance, or community
guidance. `MUST` and `SHOULD` appear only when the linked MCP source uses that
normative level for the summarized rule. OWASP rows are marked `GUIDANCE`. The
summaries are paraphrases; follow the linked section when wording matters.

## Limits

This is a review aid, not a certification, penetration test, or guarantee of
security. A team still has to threat-model its own tools, identities, data,
network, local process boundary, and downstream APIs. Store evidence without
raw secrets or personal data.

Code, schema, tests, and JSON: MIT. Checklists: CC BY 4.0. See the license
files in this directory.