ISO 42001 readiness score (clauses 4 to 10): free MCP tool
Call the ISO 42001 readiness score (clauses 4 to 10) from your AI as a free MCP tool, no account: the inputs, a worked request and response, and how to add the server.
iso42001_readiness_score is one of the 20 free GRC tools from ISMS Copilot that any AI client can call over MCP: no account, no model, one call.
Scores a self-assessment of an AI management system against 14 requirement areas of ISO/IEC 42001:2023 clauses 4 to 10: overall score and band, a score per clause, and the weakest areas to work on first. A self-assessment aid, not an audit or a certification. Send a 0 to 4 rating for every area (0 = Not started, 1 = Initial / ad hoc, 2 = Partially in place, 3 = Largely in place, 4 = Embedded & reviewed); with any area missing the tool returns the open areas instead of a score. Returns general information from a fixed rule set; confirm against the official text.
This page is about calling the tool from an AI client: the request, the response and the setup. For the same tool on the web, with the background on the rules it applies, open the ISO 42001 readiness score (clauses 4 to 10) page.
Inputs
The tool's input schema, as tools/list returns it, field by field.
| Field | What it is | Allowed values |
|---|---|---|
scores | One rating per area, 0 to 4: 0 = Not started, 1 = Initial / ad hoc, 2 = Partially in place, 3 = Largely in place, 4 = Embedded & reviewed. Every area needs a rating before a score is computed. | object (fields below) |
scores.ai-context | Your AI setting and who is affected. You have identified the internal and external factors, and the expectations of affected parties, that are specific to developing or using your AI systems, including your role (provider, deployer) in each case. | whole number, 0 to 4 |
scores.ai-scope | What your AI management system covers. You have written down which AI systems, activities, teams, and locations the system applies to, and what is deliberately left out. | whole number, 0 to 4 |
scores.ai-leadership-policy | Leadership commitment and approved AI direction. Top management actively backs the system and has approved a written direction setting the organization's responsible-AI principles. | whole number, 0 to 4 |
scores.ai-roles | Who owns AI governance and oversight. Accountable owners are named for AI governance, risk, and human oversight of AI systems, with authority clearly assigned. | whole number, 0 to 4 |
scores.ai-risk | Identifying and treating AI risks. You have a repeatable way to find, analyse, and act on the risks your AI systems pose, with a written plan tied to your objectives. | whole number, 0 to 4 |
scores.ai-impact-assessment | Weighing your AI's effects on people and society. You judge the potential consequences of your AI systems for individuals, groups, and society, and record how you weigh and address them. | whole number, 0 to 4 |
scores.ai-objectives | AI goals and managing change safely. You set measurable goals for the system and make changes to AI systems in a controlled, planned way. | whole number, 0 to 4 |
scores.ai-resources-competence | People, skills, and awareness. The people, skills, and awareness needed to run the system and oversee AI responsibly are in place, with training where needed. | whole number, 0 to 4 |
scores.ai-documented-info | Records and evidence you keep. Policies, procedures, decisions, and evidence for the system are created, version-controlled, and retained. | whole number, 0 to 4 |
scores.ai-lifecycle | Controlled AI development and operation. Your AI systems move through controlled stages: requirements, design, verification and validation, release, and ongoing monitoring in production. | whole number, 0 to 4 |
scores.ai-data-governance | Managing the data behind your AI. You manage the data used to build and run AI systems for quality, provenance, and appropriate preparation, and document those choices. | whole number, 0 to 4 |
scores.ai-third-party | Suppliers and externally-sourced AI. You manage the AI-related risks introduced by suppliers, providers, and other third parties, with responsibilities allocated across the value chain. | whole number, 0 to 4 |
scores.ai-monitoring | Checking whether it is working. You track how the system performs, run internal checks, and hold leadership reviews to judge whether it is effective. | whole number, 0 to 4 |
scores.ai-improvement | Fixing problems and improving over time. You correct things that go wrong, address their causes, and improve the system based on what you learn. | whole number, 0 to 4 |
If an answer is missing
The tool never guesses an answer. A call with any field left out returns status: "needs_answers" and the open questions, each with its id, its text and its allowed values, and no result. Your AI can ask you those questions and call again.
Worked example
This request and response come from the tool itself: the catalog runs the tool's handler on this example input, and this page is generated from that catalog.
Request
A tools/call request, as your client sends it:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "iso42001_readiness_score",
"arguments": {
"scores": {
"ai-context": 2,
"ai-scope": 3,
"ai-leadership-policy": 2,
"ai-roles": 1,
"ai-risk": 1,
"ai-impact-assessment": 0,
"ai-objectives": 2,
"ai-resources-competence": 2,
"ai-documented-info": 3,
"ai-lifecycle": 2,
"ai-data-governance": 1,
"ai-third-party": 2,
"ai-monitoring": 1,
"ai-improvement": 1
}
}
}
}Response
The structuredContent of the result. The result's text content says the same in plain words, with the disclaimer.
{
"status": "result",
"overall": 1.64,
"band": "developing",
"band_label": "Developing",
"groups": [
{
"kind": "clause",
"id": "4",
"label": "Clause 4",
"score": 2.5,
"band": "substantial"
},
{
"kind": "clause",
"id": "5",
"label": "Clause 5",
"score": 1.5,
"band": "developing"
},
{
"kind": "clause",
"id": "6",
"label": "Clause 6",
"score": 1,
"band": "major-gaps"
},
{
"kind": "clause",
"id": "7",
"label": "Clause 7",
"score": 2.5,
"band": "substantial"
},
{
"kind": "clause",
"id": "8",
"label": "Clause 8",
"score": 1.67,
"band": "developing"
},
{
"kind": "clause",
"id": "9",
"label": "Clause 9",
"score": 1,
"band": "major-gaps"
},
{
"kind": "clause",
"id": "10",
"label": "Clause 10",
"score": 1,
"band": "major-gaps"
}
],
"priorities": [
{
"id": "ai-impact-assessment",
"title": "Weighing your AI's effects on people and society",
"group": "6",
"score": 0,
"score_label": "Not started"
},
{
"id": "ai-roles",
"title": "Who owns AI governance and oversight",
"group": "5",
"score": 1,
"score_label": "Initial / ad hoc"
},
{
"id": "ai-risk",
"title": "Identifying and treating AI risks",
"group": "6",
"score": 1,
"score_label": "Initial / ad hoc"
},
{
"id": "ai-data-governance",
"title": "Managing the data behind your AI",
"group": "8",
"score": 1,
"score_label": "Initial / ad hoc"
},
{
"id": "ai-monitoring",
"title": "Checking whether it is working",
"group": "9",
"score": 1,
"score_label": "Initial / ad hoc"
}
],
"rated": 14,
"total": 14,
"basis": [
"ISO/IEC 42001:2023 clauses 4 to 10"
],
"sources_checked_on": [],
"disclaimer": "General information from a fixed rule set, not legal advice. Check the result against the official text and with a qualified professional before you act on it.",
"more": {
"url": "https://www.ismscopilot.com/mcp?ref=mcp-tool-iso-42001-readiness-checker",
"label": "Review your own documents against this framework with ISMS Copilot"
},
"tool_page": "https://www.ismscopilot.com/resources/iso-42001-readiness-checker"
}What the result rests on
Every result names its basis, as identifiers only (never standard text):
- ISO/IEC 42001:2023 clauses 4 to 10
Add the server
claude mcp add --scope user --transport http ismscopilot-free-tools 'https://www.ismscopilot.com/api/public/tools/mcp'That is Claude Code. For claude.ai, Claude Desktop, ChatGPT, Cursor, Codex and any other client, see Add the server to your client. No sign-in, no token.
Limits
General information from a fixed rule set, not legal advice. Check the result against the official text and with a qualified professional before you act on it.
Your inputs are never logged or stored by our code. We count calls per tool (the tool name, whether it produced a result and when, nothing else). Our host keeps standard request logs (time, path, status, client address) for a short period. Do not send personal data: no tool needs any.
A fixed rule cannot read your own policies, registers or contracts. For a review of your own documents, connect ISMS Copilot, the GRC expert your AI calls.