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

services.gera/mcp-gera-compliance

NPM · @GERA-SERVICES/MCP-GERA-COMPLIANCE · SCANNED SEP 25

Classify AI systems under the EU AI Act and look up obligations and articles. Offline, no auth.

0 this week 72 Trust /100
Trust breakdown (7 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 → 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 93 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 778 tokens (~194/item across 4 items; 4 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 Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 9% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
Install

How do I install the services.gera/mcp-gera-compliance server?

services.gera/mcp-gera-compliance runs locally as an npm package, launched with npx -y @gera-services/mcp-gera-compliance. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @gera-services/mcp-gera-compliance

# add to Claude Code
claude mcp add services-gera-mcp-gera-compliance -- npx -y @gera-services/mcp-gera-compliance
// .cursor/mcp.json
{
  "mcpServers": {
    "services-gera-mcp-gera-compliance": {
      "command": "npx",
      "args": [
        "-y",
        "@gera-services/mcp-gera-compliance"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "services-gera-mcp-gera-compliance": {
      "command": "npx",
      "args": [
        "-y",
        "@gera-services/mcp-gera-compliance"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add services-gera-mcp-gera-compliance -- npx -y @gera-services/mcp-gera-compliance
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "services-gera-mcp-gera-compliance": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@gera-services/mcp-gera-compliance"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add services-gera-mcp-gera-compliance --command npx --arg -y --arg @gera-services/mcp-gera-compliance
# ~/.hermes/config.yaml
mcp_servers:
  services-gera-mcp-gera-compliance:
    command: "npx"
    args: ["-y", "@gera-services/mcp-gera-compliance"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "services-gera-mcp-gera-compliance": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@gera-services/mcp-gera-compliance"
      ]
    }
  }
}
# add to Vellum
assistant mcp add services-gera-mcp-gera-compliance -t stdio -c npx -a -y @gera-services/mcp-gera-compliance
// mcp.json
{
  "mcpServers": {
    "services-gera-mcp-gera-compliance": {
      "command": "npx",
      "args": [
        "-y",
        "@gera-services/mcp-gera-compliance"
      ]
    }
  }
}
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.

  • 25 Sept 26 −3
    • 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
    • Stability: 0.97 → pass security
  • 22 Sept 26 +1

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

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 17 Sept 26 −4
    • Stability: pass → 0.77 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

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

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 25 Sept 2026 · Analysed npm/@gera-services/mcp-gera-compliance@1.0.1

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 →

MCP tools · 4 exposed · ~778 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. 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 →

Tool Tokens
classify_ai_system ~540

Run the EU AI Act risk classification on an AI system using the Gera deterministic decision tree (Articles 5, 6(1), 6(2), 6(3), 50). Pass the boolean answer keys that apply to the system (omit a key to mean "no"/unknown). Returns the risk tier (prohibited | high_risk | borderline | limited_risk | minimal_risk), the triggered articles, the obligations, and the full reasoning trace. This is deterministic and offline — same result the GeraCompliance product gives.

NameTypeReqDescription
annex1_safety_component_regulated_productboolean––
annex3_biometric_identification_permittedboolean––
annex3_critical_infrastructureboolean––
annex3_education_assessmentboolean––
annex3_employment_recruitmentboolean––
annex3_essential_services_accessboolean––
annex3_justice_democratic_processboolean––
annex3_law_enforcementboolean––
annex3_migration_border_controlboolean––
art5_criminal_prediction_profilingboolean––
art5_emotion_detection_workplace_educationboolean––
art5_exploits_vulnerabilitiesboolean––
art5_facial_image_scrapingboolean––
art5_realtime_remote_biometric_id_law_enforcementboolean––
art5_sensitive_attribute_inferenceboolean––
art5_social_scoring_public_authorityboolean––
art5_subliminal_manipulationboolean––
art6_3_detects_patterns_not_replacing_humanboolean––
art6_3_improves_prior_human_activityboolean––
art6_3_materially_influences_decisionsboolean––
art6_3_merely_prepares_decisionsboolean––
art6_3_narrow_procedural_taskboolean––
art6_3_preparatory_taskboolean––
art6_3_significant_risk_health_safety_rightsboolean––
cat4_m1_narrows_opportunitiesboolean––
cat4_m2_override_impracticalboolean––
cat4_m3_contractual_inputboolean––
limited_risk_direct_user_interaction_no_disclosureboolean––
limited_risk_generates_synthetic_mediaboolean––

No output schema declared.

No examples provided.

get_regulation_info ~117

Look up a specific EU AI Act article by number (e.g. "5", "6", "14", "50", "99"), or search all articles by keyword (e.g. "biometric", "transparency", "penalties"). Returns the article title, a practitioner summary, and which risk tiers it applies to. Omit both arguments to list every available article.

NameTypeReqDescription
articlestring–Article number, e.g. "14".
keywordstring–Keyword to search article titles and summaries.

No output schema declared.

No examples provided.

get_requirements ~66

Return the compliance obligations, key articles, and whether a conformity assessment is required for a given EU AI Act risk tier. Use after classify_ai_system, or directly when the tier is already known.

NameTypeReqDescription
risk_tierstringyesThe EU AI Act risk tier to look up.

No output schema declared.

No examples provided.

list_risk_triggers ~55

List the eight Article 5 prohibited practices and the eight Annex III high-risk categories, each with the boolean answer key used by classify_ai_system. Use this to map a plain-language system description onto the correct classification inputs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the services.gera/mcp-gera-compliance server?

services.gera/mcp-gera-compliance is listed in the public MCP registry as services.gera/mcp-gera-compliance. Classify AI systems under the EU AI Act and look up obligations and articles. Offline, no auth. This page covers its npm package (@gera-services/mcp-gera-compliance).

Is the services.gera/mcp-gera-compliance server safe to use?

services.gera/mcp-gera-compliance scores 72 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 services.gera/mcp-gera-compliance server expose?

services.gera/mcp-gera-compliance exposes 4 tools: classify_ai_system, get_requirements, get_regulation_info, list_risk_triggers. Their descriptions and schemas cost roughly 778 tokens of context every time the server is loaded.

Is the services.gera/mcp-gera-compliance server still maintained?

services.gera/mcp-gera-compliance 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 services.gera/mcp-gera-compliance server under?

services.gera/mcp-gera-compliance declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.