ISO 27001 gap score (clauses 4 to 10): free MCP tool
Call the ISO 27001 gap 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.
iso27001_gap_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 information security management system against the 11 requirement areas of ISO/IEC 27001:2022 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 27001 gap 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.context | Business setting and stakeholder needs. You have mapped relevant internal/external factors and stakeholder expectations that affect the management system. | whole number, 0 to 4 |
scores.scope | Management-system boundary choices. You have written down where the system applies, what is included or excluded, and key links to teams, sites, services and suppliers. | whole number, 0 to 4 |
scores.leadership | Executive backing, direction and ownership. Senior leaders actively support the system, security direction is approved, and accountable owners are named for key activities. | whole number, 0 to 4 |
scores.risk | Risk workflow and control-selection record. You use a repeatable method to identify and handle information-security risks, record which controls are relevant, and keep a plan for risk-reduction work. | whole number, 0 to 4 |
scores.objectives | Security goals and managed change. You set measurable security goals with owners and timelines, and significant system changes are prepared before they are made. | whole number, 0 to 4 |
scores.support | People, skills and communication basics. The system has enough people and tools; staff know what is expected of them; and recurring internal/external messages are planned. | whole number, 0 to 4 |
scores.documentation | Documents and records kept under control. Key files and evidence are created, approved, versioned, protected and available to the right people when needed. | whole number, 0 to 4 |
scores.operation | Day-to-day running of the security system. Risk work and selected safeguards are carried out in practice, kept current, and coordinated with outsourced activities. | whole number, 0 to 4 |
scores.monitoring | Checking whether the system works. You choose useful indicators, review the results, and use them to judge whether the management system is doing its job. | whole number, 0 to 4 |
scores.audit-review | Scheduled independent checks and leadership review. Planned internal checks are performed by suitable people, and senior leaders periodically review results, issues and decisions. | whole number, 0 to 4 |
scores.improvement | Issue handling and ongoing improvement. Problems are logged, causes are addressed, follow-up is tracked, and the system is improved over time. | 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": "iso27001_gap_score",
"arguments": {
"scores": {
"context": 3,
"scope": 4,
"leadership": 2,
"risk": 1,
"objectives": 2,
"support": 3,
"documentation": 2,
"operation": 2,
"monitoring": 1,
"audit-review": 0,
"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.91,
"band": "developing",
"band_label": "Developing",
"groups": [
{
"kind": "clause",
"id": "4",
"label": "Clause 4",
"score": 3.5,
"band": "strong"
},
{
"kind": "clause",
"id": "5",
"label": "Clause 5",
"score": 2,
"band": "developing"
},
{
"kind": "clause",
"id": "6",
"label": "Clause 6",
"score": 1.5,
"band": "developing"
},
{
"kind": "clause",
"id": "7",
"label": "Clause 7",
"score": 2.5,
"band": "substantial"
},
{
"kind": "clause",
"id": "8",
"label": "Clause 8",
"score": 2,
"band": "developing"
},
{
"kind": "clause",
"id": "9",
"label": "Clause 9",
"score": 0.5,
"band": "major-gaps"
},
{
"kind": "clause",
"id": "10",
"label": "Clause 10",
"score": 1,
"band": "major-gaps"
}
],
"priorities": [
{
"id": "audit-review",
"title": "Scheduled independent checks and leadership review",
"group": "9",
"score": 0,
"score_label": "Not started"
},
{
"id": "risk",
"title": "Risk workflow and control-selection record",
"group": "6",
"score": 1,
"score_label": "Initial / ad hoc"
},
{
"id": "monitoring",
"title": "Checking whether the system works",
"group": "9",
"score": 1,
"score_label": "Initial / ad hoc"
},
{
"id": "improvement",
"title": "Issue handling and ongoing improvement",
"group": "10",
"score": 1,
"score_label": "Initial / ad hoc"
},
{
"id": "leadership",
"title": "Executive backing, direction and ownership",
"group": "5",
"score": 2,
"score_label": "Partially in place"
}
],
"rated": 11,
"total": 11,
"basis": [
"ISO/IEC 27001:2022 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-27001-gap-checker",
"label": "Review your own documents against this framework with ISMS Copilot"
},
"tool_page": "https://www.ismscopilot.com/resources/iso-27001-gap-checker"
}What the result rests on
Every result names its basis, as identifiers only (never standard text):
- ISO/IEC 27001:2022 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.