Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.SwikingSWE/conformy

NPM · @CONFORMY/MCP-SERVER · SCANNED AUG 3

EU AI Act & NIS2 compliance — classify AI systems, check obligations, draft docs.

+23 this week 63 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 71 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).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 Management27
  • Stability observed for 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @conformy/mcp-server

# add to Claude Code
claude mcp add swikingswe-conformy -- npx -y @conformy/mcp-server
# add to Codex CLI
codex mcp add swikingswe-conformy -- npx -y @conformy/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "swikingswe-conformy": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@conformy/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add swikingswe-conformy --command npx --arg -y --arg @conformy/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  swikingswe-conformy:
    command: "npx"
    args: ["-y", "@conformy/mcp-server"]
// mcp.json
{
  "mcpServers": {
    "swikingswe-conformy": {
      "command": "npx",
      "args": [
        "-y",
        "@conformy/mcp-server"
      ]
    }
  }
}
Changelog

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Aug 26 +62
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Schema quality: unverified → good functional
    • Tool coverage: unverified → 100 functional
    • Licence: MIT functional
  • 31 Jul 26 −18
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −22
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 40

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/@conformy/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 17 exposed · ~1,933 tokens

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.

Tool Tokens
check_credits ~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 ~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 ~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.

NameTypeReqDescription
entity_levelstringyesEntity classification level

No output schema declared.

No examples provided.

classify_ai_system ~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.

NameTypeReqDescription
annex_iii_categorystringHigh-risk category under Annex III, if known. See list_annex_iii_categories for descriptions.
languagestringResponse language: 'sv' (Swedish) or 'en' (English). Default: 'en'
performs_profilingbooleanDoes the system profile natural persons based on personal data?
prohibited_practicesobjectArticle 5 prohibited practice checks. If any are true, the system is classified as prohibited.
rolestringyesYour role: 'provider' if you build/develop/train the AI system, 'deployer' if you use/deploy it in your organisation
system_descriptionstringyesDescription 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 ~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.

NameTypeReqDescription
annual_turnover_eurnumberyesAnnual turnover in EUR millions (e.g. 50 for €50M)
balance_sheet_eurnumberyesBalance sheet total in EUR millions (e.g. 43 for €43M)
employee_countintegeryesNumber of employees in the organization
is_public_administrationbooleanIs the organization a central government body?
is_qualified_trust_service_providerbooleanIs the organization a qualified trust service provider under eIDAS?
languagestringResponse language: 'sv' (Swedish) or 'en' (English). Default: 'en'
organization_descriptionstringyesDescription of the organization and its activities
provides_dns_servicesbooleanDoes the organization provide DNS resolution services?
provides_tld_registrationbooleanDoes the organization manage a TLD name registry?
sectorstringyesNIS2 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 ~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.

NameTypeReqDescription
answersobjectyesFlat object mapping question IDs to answer strings, e.g. { general_purpose: 'Our system...', general_provider: 'Acme Corp' }
auto_generatebooleanAutomatically start AI generation after creating the document (default: true)
document_typestringyesDocument type (matches backend enum)
languagestringDocument language
rolestringRole context
titlestringyesDocument title (e.g. 'MedAssist AI — Annex IV Technical Documentation')

No output schema declared.

No examples provided.

export_document ~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).

NameTypeReqDescription
document_idstringyesDocument ID (UUID)
formatstringyesExport format: 'pdf' or 'docx'
languagestringDocument language

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
document_idstringyesDocument ID (UUID)
languagestringDocument language
rolestringRole context for generation

No output schema declared.

No examples provided.

generate_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.

NameTypeReqDescription
answerstringyesYour input describing this aspect of the system — the AI will expand this into a draft compliance section
article_referencestringEU AI Act article reference for this section (e.g. 'Article 11 + Annex IV, Section 1')
languagestringLanguage for generation: 'sv' (Swedish) or 'en' (English). Default: 'sv'
question_idstringyesUnique identifier for the question/section being answered
question_labelstringyesThe specific question being answered within this section
rolestringRole context for generation
section_indexintegeryesSection number within the document (1-based)
section_titlestringyesTitle of the document section (e.g. 'System Description and Purpose')

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
document_idstringyesDocument ID (UUID)
languagestringResponse language

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
document_typestringyesType of compliance document
languagestringLanguage for question labels: 'sv' (Swedish) or 'en' (English)
rolestringRole context (only affects annex-iv)

No output schema declared.

No examples provided.

get_generation_status ~49

Check the progress of document generation. Returns how many questions have been generated out of the total.

NameTypeReqDescription
document_idstringyesDocument ID (UUID)
languagestringResponse language

No output schema declared.

No examples provided.

get_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.

NameTypeReqDescription
risk_levelstringyesThe risk level of the AI system
rolestringyesYour 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 ~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 ~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.

NameTypeReqDescription
languagestringResponse language

No output schema declared.

No examples provided.

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 ~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.

NameTypeReqDescription
answersobjectyesAnswers to update — flat object mapping question IDs to new answer strings
document_idstringyesDocument ID (UUID)
languagestringDocument language
row_versionstringyesRow version from get_document (optimistic concurrency)

No output schema declared.

No examples provided.