io.github.SwikingSWE/conformy
NPM · @CONFORMY/MCP-SERVER · SCANNED SEP 25
EU AI Act & NIS2 compliance — classify AI systems, check obligations, draft docs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 124 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1933 tokens (~113/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.SwikingSWE/conformy MCP server?
io.github.SwikingSWE/conformy runs locally as an npm package, launched with npx -y @conformy/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @conformy/mcp-server
claude mcp add swikingswe-conformy -- npx -y @conformy/mcp-server
{
"mcpServers": {
"swikingswe-conformy": {
"command": "npx",
"args": [
"-y",
"@conformy/mcp-server"
]
}
}
} {
"servers": {
"swikingswe-conformy": {
"command": "npx",
"args": [
"-y",
"@conformy/mcp-server"
]
}
}
} codex mcp add swikingswe-conformy -- npx -y @conformy/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"swikingswe-conformy": {
"type": "local",
"command": [
"npx",
"-y",
"@conformy/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add swikingswe-conformy --command npx --arg -y --arg @conformy/mcp-server
mcp_servers:
swikingswe-conformy:
command: "npx"
args: ["-y", "@conformy/mcp-server"] {
"McpServers": {
"swikingswe-conformy": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@conformy/mcp-server"
]
}
}
} assistant mcp add swikingswe-conformy -t stdio -c npx -a -y @conformy/mcp-server
{
"mcpServers": {
"swikingswe-conformy": {
"command": "npx",
"args": [
"-y",
"@conformy/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/@conformy/mcp-server@0.3.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_credits Check Credit Balance ~34
Check how many document generation credits remain on your Conformy account. Requires an API key (CONFORMY_API_KEY).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_deadline Check EU AI Act Deadline ~54
Check how many days remain until EU AI Act enforcement deadlines. Shows all key dates including the high-risk deadline (August 2, 2026) and the all-systems deadline (August 2, 2027).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_nis2_obligations Check NIS2 Obligations ~59
Quick reference for NIS2 obligations by entity level. Shows the 10 risk management measures (Article 21), incident reporting timelines (Article 23), and supervision regime.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_level | string | yes | Entity classification level |
No output schema declared.
No examples provided.
classify_ai_system Classify AI System (EU AI Act) ~243
Classify an AI system under the EU AI Act. Determines risk level (prohibited, high-risk, limited, minimal), checks against Article 5 prohibited practices, maps to Annex III categories, lists required documentation, and provides the compliance deadline. Use this when building, deploying, or reviewing AI features to check regulatory obligations.
| Name | Type | Req | Description |
|---|---|---|---|
| annex_iii_category | string | – | High-risk category under Annex III, if known. See list_annex_iii_categories for descriptions. |
| language | string | – | Response language: 'sv' (Swedish) or 'en' (English). Default: 'en' |
| performs_profiling | boolean | – | Does the system profile natural persons based on personal data? |
| prohibited_practices | object | – | Article 5 prohibited practice checks. If any are true, the system is classified as prohibited. |
| role | string | yes | Your role: 'provider' if you build/develop/train the AI system, 'deployer' if you use/deploy it in your organisation |
| system_description | string | yes | Description of the AI system — what it does, how it works, what decisions it makes or influences |
No output schema declared.
No examples provided.
classify_nis2_entity Classify NIS2 Entity ~302
Classify an organization under the NIS2 Directive (EU 2022/2555) / Swedish Cybersäkerhetslagen. Determines if the organization is an essential entity, important entity, or not in scope based on sector, size, and special designations. Returns required documents, reporting obligations, supervision regime, and maximum fines.
| Name | Type | Req | Description |
|---|---|---|---|
| annual_turnover_eur | number | yes | Annual turnover in EUR millions (e.g. 50 for €50M) |
| balance_sheet_eur | number | yes | Balance sheet total in EUR millions (e.g. 43 for €43M) |
| employee_count | integer | yes | Number of employees in the organization |
| is_public_administration | boolean | – | Is the organization a central government body? |
| is_qualified_trust_service_provider | boolean | – | Is the organization a qualified trust service provider under eIDAS? |
| language | string | – | Response language: 'sv' (Swedish) or 'en' (English). Default: 'en' |
| organization_description | string | yes | Description of the organization and its activities |
| provides_dns_services | boolean | – | Does the organization provide DNS resolution services? |
| provides_tld_registration | boolean | – | Does the organization manage a TLD name registry? |
| sector | string | yes | NIS2 sector from Annex I or Annex II. Use 'None' if unsure. Use list_nis2_sectors to see all options. |
No output schema declared.
No examples provided.
create_document Create Document ~159
Create a new compliance document with answers and optionally start AI generation. First use `get_document_template` to see what questions are needed, then provide answers as a flat object mapping question IDs to answer strings.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | Flat object mapping question IDs to answer strings, e.g. { general_purpose: 'Our system...', general_provider: 'Acme Corp' } |
| auto_generate | boolean | – | Automatically start AI generation after creating the document (default: true) |
| document_type | string | yes | Document type (matches backend enum) |
| language | string | – | Document language |
| role | string | – | Role context |
| title | string | yes | Document title (e.g. 'MedAssist AI — Annex IV Technical Documentation') |
No output schema declared.
No examples provided.
export_document Export Document to PDF/DOCX ~102
Export a generated compliance document to PDF or DOCX. Fetches the document by ID, sends it to the export endpoint, and saves the file to ~/Downloads. Returns the file path. The document must have generated sections (use `get_generation_status` to verify completion first).
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | Document ID (UUID) |
| format | string | yes | Export format: 'pdf' or 'docx' |
| language | string | – | Document language |
No output schema declared.
No examples provided.
generate_document Generate Document ~79
Start AI generation for an existing document. The backend generates all answers in the background, only regenerating questions whose answers have changed (token-efficient). Use `get_generation_status` to poll progress.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | Document ID (UUID) |
| language | string | – | Document language |
| role | string | – | Role context for generation |
No output schema declared.
No examples provided.
generate_document_section Generate Compliance Document Section ~226
Generate a single section of an EU AI Act compliance document using AI. Provide context about the AI system and the section topic, and receive a draft section with article references. Requires the Conformy API to be running with an LLM configured.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | Your input describing this aspect of the system — the AI will expand this into a draft compliance section |
| article_reference | string | – | EU AI Act article reference for this section (e.g. 'Article 11 + Annex IV, Section 1') |
| language | string | – | Language for generation: 'sv' (Swedish) or 'en' (English). Default: 'sv' |
| question_id | string | yes | Unique identifier for the question/section being answered |
| question_label | string | yes | The specific question being answered within this section |
| role | string | – | Role context for generation |
| section_index | integer | yes | Section number within the document (1-based) |
| section_title | string | yes | Title of the document section (e.g. 'System Description and Purpose') |
No output schema declared.
No examples provided.
get_document Get Document ~106
Get a compliance document by ID, including all answers and generated sections. Use this to review what has been generated, identify sections that need improvement, or prepare for edits. After reviewing, use `update_document_answers` to change answers and `generate_document` to regenerate only the changed sections (1 credit per changed section). Use `export_document` to download as PDF or DOCX.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | Document ID (UUID) |
| language | string | – | Response language |
No output schema declared.
No examples provided.
get_document_template Get Document Template ~97
Get the full question template for a compliance document type. Returns all sections and questions that need to be answered. Use this FIRST to understand what information is needed before creating a document.
| Name | Type | Req | Description |
|---|---|---|---|
| document_type | string | yes | Type of compliance document |
| language | string | – | Language for question labels: 'sv' (Swedish) or 'en' (English) |
| role | string | – | Role context (only affects annex-iv) |
No output schema declared.
No examples provided.
get_generation_status Get Generation Status ~49
Check the progress of document generation. Returns how many questions have been generated out of the total.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | Document ID (UUID) |
| language | string | – | Response language |
No output schema declared.
No examples provided.
get_requirements Get Compliance Requirements ~87
Get the list of required compliance documents for a specific risk level and role under the EU AI Act. Use this for a quick lookup without running a full classification.
| Name | Type | Req | Description |
|---|---|---|---|
| risk_level | string | yes | The risk level of the AI system |
| role | string | yes | Your role: 'provider' if you build/develop the system, 'deployer' if you use/deploy it |
No output schema declared.
No examples provided.
list_annex_iii_categories List Annex III High-Risk Categories ~55
List all high-risk AI system categories defined in Annex III of the EU AI Act. Use this to understand which areas trigger high-risk classification, or to look up the correct category key for the classify_ai_system tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_documents List Documents ~86
List all compliance documents for the authenticated organization. Use this as the starting point to continue working on an existing document — pick a document, then use `get_document` to see its current state, `update_document_answers` to change answers, and `generate_document` to regenerate changed sections. Documents created here are also visible on conformy.io.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Response language |
No output schema declared.
No examples provided.
list_nis2_sectors List NIS2 Sectors ~56
List all sectors covered by the NIS2 Directive, split by Annex I (highly critical) and Annex II (other critical). Use this to find the correct sector key for the classify_nis2_entity tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update_document_answers Update Document Answers ~139
Update answers on an existing document. Only provide the answers that changed — you don't need to resend unchanged answers. After updating, use `generate_document` to regenerate. The backend uses smart diffing and only regenerates sections whose answers actually changed, so you only spend credits on what changed. Get the current answers and row version from `get_document` first.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | Answers to update — flat object mapping question IDs to new answer strings |
| document_id | string | yes | Document ID (UUID) |
| language | string | – | Document language |
| row_version | string | yes | Row version from get_document (optimistic concurrency) |
No output schema declared.
No examples provided.
What is the io.github.SwikingSWE/conformy MCP server?
io.github.SwikingSWE/conformy is an MCP server listed in the public MCP registry as io.github.SwikingSWE/conformy. EU AI Act & NIS2 compliance, classify AI systems, check obligations, draft docs. This page covers its npm package (@conformy/mcp-server).
Is the io.github.SwikingSWE/conformy MCP server safe to use?
io.github.SwikingSWE/conformy scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.SwikingSWE/conformy MCP server expose?
io.github.SwikingSWE/conformy exposes 17 tools: classify_ai_system, check_deadline, get_requirements, list_annex_iii_categories, generate_document_section, and 12 more. Their descriptions and schemas cost roughly 1,933 tokens of context every time the server is loaded.
Is the io.github.SwikingSWE/conformy MCP server still maintained?
io.github.SwikingSWE/conformy is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.SwikingSWE/conformy MCP server under?
io.github.SwikingSWE/conformy declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.