Server data from the Official MCP Registry
Read-only AI Adoption Controls Framework: controls, Level 3 criteria, standards cross-references
About
Read-only AI Adoption Controls Framework: controls, Level 3 criteria, standards cross-references
Remote endpoints: streamable-http: https://aacf.adriansaxton.com/mcp
Security Report
Valid MCP server (1 strong, 2 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
8 tools verified · Open access · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Found in Source Code
Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.
How to Connect
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"com-adriansaxton-aacf": {
"url": "https://aacf.adriansaxton.com/mcp"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
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 |
|---|---|
get_framework_info | Version, scale, overlays, owner roles, lifecycle stages, the standards cross-referenced, how to cite |
list_domains | Every domain and the controls in it |
get_control | One control in full, with its Level 3 criteria and cross-references |
search_controls | Controls by words, domain, overlay, owner role or lifecycle stage |
get_mapping | Which controls cover an item of a standard, for example ISO/IEC 42001 6.1.2 |
get_standard_coverage | Every cross-referenced item of one standard |
get_assessment_questions | Questions, evidence and applicable criteria for a self-assessment, one domain at a time |
get_scoring_rules | 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.
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.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
