AACF MCP Server
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
AACF MCP server
A public, read-only Model Context Protocol server for the AI Adoption Controls Framework (AACF). Point any MCP-capable AI assistant at it to look up controls, criteria and cross-references, for example "which controls cover ISO/IEC 42001 clause 6.1.2". It serves the published release data and stores nothing.
Work in progress: the server is built and tested locally; it is not deployed yet.
Tools
Tool | What it answers |
| Version, scale, overlays, owner roles, lifecycle stages, the standards cross-referenced, how to cite |
| Every domain and the controls in it |
| One control in full, with its Level 3 criteria and cross-references |
| Controls by words, domain, overlay, owner role or lifecycle stage |
| Which controls cover an item of a standard, for example ISO/IEC 42001 6.1.2 |
| Every cross-referenced item of one standard |
| Questions, evidence and applicable criteria for a self-assessment, one domain at a time |
| The assessor rulebook |
The self_assessment prompt guides your assistant through an assessment. Your answers stay in your conversation:
no tool accepts them, and the server stores nothing.
Cross-references are coverage, not a compliance finding.
Related MCP server: turva-mcp
How the data gets in
npm run vendor -- v1.2.1copies one tagged AACF release (data/aacf.json,data/aacf.schema.json,framework/rulebook.md) intovendor/aacf/and records a SHA-256 for each file invendor/aacf/RELEASE.json.npm run build:datachecks the files against those hashes and against the release's own JSON Schema, refuses any data shape other than schema major version 1, checks every cross-reference, dependency and owner, and writes a compact, pre-indexedsrc/data/aacf.generated.jsonfor the server to read.npm testchecks that nothing is lost or changed on the way: every control field, every cross-reference in both directions, and the coverage counts.
To move to a new AACF release, vendor its tag, rebuild and run the tests.
Server and tests
src/index.ts is the Cloudflare Worker: the MCP endpoint is /mcp, built on the official MCP TypeScript SDK through
createMcpHandler. It speaks the 2026-07-28 protocol and still serves 2025 Streamable HTTP clients. Requests that
carry an Origin header must come from the AACF website; requests without one (MCP clients calling from their own
servers) are accepted.
npm test builds the data, bundles the Worker and runs a real MCP client against it in both protocol versions:
every tool and the prompt must be listed and must answer, and the HTTP rules (route, methods, Origin, Host and
the 2026-07-28 header checks) are tested directly. npm run typecheck runs TypeScript.
Wrangler, used to run and deploy the Worker, needs Node.js 22.12 or later (.node-version pins 22).
Deployment
Cloudflare Workers Builds deploys the main branch: build command npm run build:data, deploy command
npx wrangler deploy (the default). The Worker name in Cloudflare must be aacf-mcp, matching wrangler.jsonc.
MCP Registry
Listed in the official MCP Registry as com.adriansaxton/aacf, from
server.json (remote only, Streamable HTTP). Its version follows the AACF release the server serves, so a new AACF
release means bumping it and publishing again with mcp-publisher publish. The namespace is proved by a DNS TXT record
on adriansaxton.com.
Licences
The code in this repository is under the MIT licence (LICENSE). The framework content in vendor/aacf/ and
everything the server returns from it is the AI Adoption Controls Framework by Adrian Saxton, licensed under
CC BY-SA 4.0. Cite it with the DOI 10.5281/zenodo.24171718.
The AACF name and logo are not openly licensed.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only MCP for AI usage profiles, leaderboards, stats, and docs; no writes or private data.
Read-only MCP server for RZ AI Labs — query its services, workshops, and contact info.
Read-only MCP server that answers questions about turva.dev from its published data. Five tools return JSON: the service catalog with prices, contact and operator details, engagement principles and dated agent-readiness and security evidence with verification links. Connect over Streamable HTTP. You need no API key. The server does not scan other websites or run audits.
Read-only MCP server exposing a user ORANO library to their own AI agent.
Related MCP Servers
- FlicenseAqualityDmaintenanceAn unofficial MCP server that exposes public FedRAMP 20x documentation as deterministic, citable lookup tools for AI assistants, with every response citing the exact upstream source.7-
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server that answers questions about turva.dev from its published data. Five tools return JSON: the service catalog with prices, contact and operator details, engagement principles and dated agent-readiness and security evidence with verification links. Connect over Streamable HTTP. You need no API key. The server does not scan other websites or run audits.MIT
- FlicenseAqualityDmaintenanceA static, read-only MCP server that exposes a database knowledge base (schema, relationships, workflows, and reasoning patterns) so Claude Code / Copilot can reason about a database without a live connection.10-
- AlicenseAqualityDmaintenanceRead-only MCP server providing AI access to verifiable web, GitHub, and local sources, plus a managed fantasy entity catalog, with strong security and provenance tracking.101MIT