Skip to content

io.tooloracle/ampel

by tooloracle.io · remote · no sign-in to list tools · v1.0.0 · published by io.tooloracle

AmpelOracle — 50-tool compliance traffic-light: Go/Caution/Stop signals for ESG, MiCA, AML.

Final · 1Changes · 40

50 tools: 1 do something that can't be undone, 40 change things and 9 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http ampel https://tooloracle.io/ampel/mcp/

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

50 tools

Can't be undone 1Claude Code: ask
  • bafin_approve_sendApprove BaFin report for submission (4-eyes principle).Can send data outNo findings

    Why it is in this group

    • The name "bafin_approve_send" says "approve": a word for a change.
    • The name "bafin_approve_send" also says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "bafin_approve_send" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Approve BaFin report for submission (4-eyes principle). Creates signed approval evidence.
Changes things 40Claude Code: ask
  • assess_allRe-run full assessment for an entity.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Re-run full assessment for an entity. Recomputes Ampel statuses from all available evidence.
  • audit_trailChain-linked audit log with integrity check.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Chain-linked audit log with integrity check.
  • azure_ad_checkLive Azure AD integration: MFA registration %, risky users, conditional access policies.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Live Azure AD integration: MFA registration %, risky users, conditional access policies. DORA Art. 9 evidence. Requires Azure AD config in integrations_config.json.
  • bafin_report_draftGenerate ITS 2024/1772 compliant BaFin incident report draft.No findings

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    Description, as the server wrote it
    Generate ITS 2024/1772 compliant BaFin incident report draft. All mandatory fields per DORA Art. 19/20. Preview mode — requires board approval.
  • board_summaryExecutive board summary: overall score, top 5 risks, overdue findings, SLA breaches, concentration risk, evidence health, owner workload.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Executive board summary: overall score, top 5 risks, overdue findings, SLA breaches, concentration risk, evidence health, owner workload. Designed for management/board reporting.
  • bridge_approveApprove or reject a bridge resolution.No findings

    Why it is in this group

    • The name "bridge_approve" says "approve": a word for a change.
    Description, as the server wrote it
    Approve or reject a bridge resolution. On approval: creates signed evidence, upgrades Ampel to GREEN, logs to audit chain.
  • bridge_reportBridge gap analysis: classifies gaps by DATA/EVIDENCE/POLICY/WORKFLOW with closure path, owner, effort level.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Bridge gap analysis: classifies gaps by DATA/EVIDENCE/POLICY/WORKFLOW with closure path, owner, effort level.
  • bridge_resolveStart bridge resolution workflow.No findings

    Why it is in this group

    • The name "bridge_resolve" says "resolve": a word for reading.
    • The description's first verb is "start": a word for a change.
    Description, as the server wrote it
    Start bridge resolution workflow. Generates templates (Risk Acceptance, Contract Renegotiation, Concentration Policy, Exit Strategy), tracks approval process. Call bridge_approve to sign off.
  • check_contractCheck DORA Art.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check DORA Art. 30 contract clauses for a provider. Returns PASS/WARN/BLOCK with missing clauses and bridge classification.
  • collect_art10Collect live Art.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Collect live Art. 10 evidence from NVD, CISA KEV, CERT-Bund. Auto-assesses.
  • contract_uploadUpload contract text for DORA Art.No findings

    Why it is in this group

    • The name "contract_upload" says "upload": a word for a change.
    Description, as the server wrote it
    Upload contract text for DORA Art. 30 analysis. Creates document record with SHA-256 hash, version tracking, audit trail.
  • create_entityRegister a new regulated entity.No findings

    Why it is in this group

    • The name "create_entity" says "create": a word for a change.
    Description, as the server wrote it
    Register a new regulated entity.
  • create_trialCreate temporary trial entity (48h) for self-service DORA assessment.No findings

    Why it is in this group

    • The name "create_trial" says "create": a word for a change.
    Description, as the server wrote it
    Create temporary trial entity (48h) for self-service DORA assessment. No login needed.
  • cross_oracle_assessEnterprise cross-oracle assessment.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Enterprise cross-oracle assessment. Runs 18 checks across CyberShield (NIS2/ISO 27001), SupplyChainOracle (LkSG/CSRD), HealthGuard (MDR/GDPR), CFOCoPilot (XRechnung), TaxOracle (DAC6), LegalTechOracle (DORA contracts). Auto-stores evidence and updates Ampel status.
  • cross_regulation_checkTag findings with cross-regulation impact (DORA + MiCA + AMLR).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Tag findings with cross-regulation impact (DORA + MiCA + AMLR). Shows which DORA findings also affect MiCA insider info or AMLR screening.
  • cve_asset_mapMap CVE/vulnerability to internal ICT providers and systems.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Map CVE/vulnerability to internal ICT providers and systems. Auto-creates findings for critical matches. DORA Art. 10.
  • dependency_graphFull provider dependency graph: providers, systems, checks, blast radius, SPOF detection.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Full provider dependency graph: providers, systems, checks, blast radius, SPOF detection.
  • evidence_packExport evidence pack for article/check/entity.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Export evidence pack for article/check/entity. Pruefer-ready: evidence, assessments, findings, audit trail, signatures.
  • evidence_summaryAll evidence artefacts for an entity with hashes and expiry dates.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    All evidence artefacts for an entity with hashes and expiry dates.
  • freshness_checkRun freshness watchdog.No findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    Description, as the server wrote it
    Run freshness watchdog. Expires stale evidence, downgrades GREEN->YELLOW->GREY if evidence too old.
  • gap_reportDORA compliance gaps.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    DORA compliance gaps. RED/GREY/YELLOW items with priority and required actions.
  • generate_reportGenerate data-driven DORA Ampel PDF report.No findings

    Why it is in this group

    • The name "generate_report" says "generate": a word for a change.
    Description, as the server wrote it
    Generate data-driven DORA Ampel PDF report. Score, gap analysis, provider register, audit trail integrity.
  • generate_trial_reportGenerate watermarked trial report with score, gaps, and CTA.No findings

    Why it is in this group

    • The name "generate_trial_report" says "generate": a word for a change.
    Description, as the server wrote it
    Generate watermarked trial report with score, gaps, and CTA.
  • health_checkServer + DB status.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Server + DB status.
  • incident_flowDORA incident lifecycle: log, classify, notify (BaFin), close.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    DORA incident lifecycle: log, classify, notify (BaFin), close. Each step creates signed evidence.
  • llm_clause_checkLLM-based DORA Art.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    LLM-based DORA Art. 30 contract analysis. Paste contract text, get clause-by-clause PRESENT/PARTIAL/MISSING for all 15 mandatory clauses. Uses Claude API.
  • onboard_entityFull entity onboarding: creates initial RED assessments for all 39 checks, collects auto-evidence from live sources, re-assesses, and returns readiness score.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Full entity onboarding: creates initial RED assessments for all 39 checks, collects auto-evidence from live sources, re-assesses, and returns readiness score.
  • policy_draftGenerate DORA policy/framework document draft for a specific article.No findings

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    Description, as the server wrote it
    Generate DORA policy/framework document draft for a specific article. 8 templates available (Art. 5,6,8,10,11,17,28,30). Uses entity data for customization.
  • provider_country_riskEnrich provider dependencies with OECD economic risk: GDP, unemployment, CLI per provider country.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Enrich provider dependencies with OECD economic risk: GDP, unemployment, CLI per provider country. DORA Art. 28-31 relevant.
  • readiness_checkFull DORA readiness score + Ampel per article.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Full DORA readiness score + Ampel per article. Returns GREEN/YELLOW/RED/GREY for all 26 articles, score 0-100, days until deadline.
  • reg_watchdogAI Regulatory Watchdog: scrapes EBA/ESMA/BaFin/CERT-Bund for DORA updates.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe description's first sentence says "scrape": it reads web pages, which anyone can write.
    Description, as the server wrote it
    AI Regulatory Watchdog: scrapes EBA/ESMA/BaFin/CERT-Bund for DORA updates. Returns alerts with affected articles and severity. Run daily via cron or on-demand.
  • register_providerRegister an ICT third-party provider for DORA Art.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Register an ICT third-party provider for DORA Art. 28 Register of Information. Stores provider data and creates evidence.
  • retest_findingRe-test a finding: collect fresh evidence, reassess check, auto-close if GREEN.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Re-test a finding: collect fresh evidence, reassess check, auto-close if GREEN. Full closed-loop.
  • run_escalationTrigger escalation engine: auto-create findings, check SLA, escalate.No findings

    Why it is in this group

    • The name "run_escalation" says "run": a word for a change.
    Description, as the server wrote it
    Trigger escalation engine: auto-create findings, check SLA, escalate.
  • run_trial_assessmentRun complete DORA+MiCA assessment for trial entity.No findings

    Why it is in this group

    • The name "run_trial_assessment" says "run": a word for a change.
    Description, as the server wrote it
    Run complete DORA+MiCA assessment for trial entity. Returns score, gaps, automation potential.
  • score_trendScore trend over time: weekly deltas, trajectory, peer benchmark.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Score trend over time: weekly deltas, trajectory, peer benchmark. Shows improvement or decline.
  • servicenow_syncServiceNow incident + change management sync.No findings

    Why it is in this group

    • The name "servicenow_sync" says "sync": a word for a change.
    Description, as the server wrote it
    ServiceNow incident + change management sync. DORA Art. 17/21 evidence. Returns 30-day incident stats, classification, resolution rates.
  • update_findingUpdate finding lifecycle: claim, set remediation plan, request re-test, close, or accept risk.No findings

    Why it is in this group

    • The name "update_finding" says "update": a word for a change.
    Description, as the server wrote it
    Update finding lifecycle: claim, set remediation plan, request re-test, close, or accept risk. Status flow: open -> in_progress -> retest_pending -> closed | risk_accepted.
  • whatif_providerSimulate provider failure: which articles/checks are affected, score impact, risk level.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Simulate provider failure: which articles/checks are affected, score impact, risk level.
  • whatif_staleSimulate stale evidence: what happens if a check stays stale for N days.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Simulate stale evidence: what happens if a check stays stale for N days.
Only reads 9Claude Code: allow
  • article_statusDetailed Ampel for a specific DORA article.No findings

    Why it is in this group

    • The name "article_status" says "status": a word for reading.
    Description, as the server wrote it
    Detailed Ampel for a specific DORA article. Each check with GREEN/YELLOW/RED conditions and evidence.
  • bridge_statusCheck status of all bridge resolution workflows for an entity.No findings

    Why it is in this group

    • The name "bridge_status" says "status": a word for reading.
    Description, as the server wrote it
    Check status of all bridge resolution workflows for an entity. Shows open, pending, closed, rejected.
  • bus_statusOracle Event Bus status: events, cross-refs, connected oracles.No findings

    Why it is in this group

    • The name "bus_status" says "status": a word for reading.
    Description, as the server wrote it
    Oracle Event Bus status: events, cross-refs, connected oracles.
  • contract_analyzeAnalyze contract against 15 DORA Art.No findings

    Why it is in this group

    • The name "contract_analyze" says "analyze": a word for reading.
    Description, as the server wrote it
    Analyze contract against 15 DORA Art. 30 mandatory clauses. Returns compliance status per clause with confidence score, extracted text, gap reasoning, suggested fix.
  • contract_statusOverview of all analyzed contracts per entity.No findings

    Why it is in this group

    • The name "contract_status" says "status": a word for reading.
    Description, as the server wrote it
    Overview of all analyzed contracts per entity. Shows clause gaps, review status, document versions.
  • entity_listList all registered regulated entities.No findings

    Why it is in this group

    • The name "entity_list" says "list": a word for reading.
    Description, as the server wrote it
    List all registered regulated entities.
  • escalation_statusGet findings, SLA breaches, escalation status per entity.No findings

    Why it is in this group

    • The name "escalation_status" says "status": a word for reading.
    Description, as the server wrote it
    Get findings, SLA breaches, escalation status per entity.
  • pingQuick connectivity test.No findings

    Why it is in this group

    • The name "ping" says "ping": a word for reading.
    Description, as the server wrote it
    Quick connectivity test.
  • regulation_impactShow cross-regulation impacts for a specific DORA article.No findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.
    Description, as the server wrote it
    Show cross-regulation impacts for a specific DORA article. Maps DORA → MiCA + AMLR.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Looked at Oct 22, 2026, 15:18 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
41
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
none
RFC 9728 protected resource metadata
https://tooloracle.io/.well-known/oauth-protected-resource/ampel/mcp
Authorization servers
https://feedoracle.io
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 41 tools that change things (1 irreversible, 40 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://tooloracle.io/ampel/mcp/: tools/list returned 50 tools to an anonymous client, including bafin_approve_send (irreversible), readiness_check (write), gap_report (write), evidence_summary (write), collect_art10 (write) and 36 more

    What this check looks for

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http ampel https://tooloracle.io/ampel/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ampel__article_status",
      "mcp__ampel__entity_list",
      "mcp__ampel__bridge_status",
      "mcp__ampel__ping",
      "mcp__ampel__bus_status",
      "mcp__ampel__escalation_status",
      "mcp__ampel__contract_analyze",
      "mcp__ampel__contract_status",
      "mcp__ampel__regulation_impact"
    ],
    "ask": [
      "mcp__ampel__readiness_check",
      "mcp__ampel__gap_report",
      "mcp__ampel__evidence_summary",
      "mcp__ampel__collect_art10",
      "mcp__ampel__create_entity",
      "mcp__ampel__audit_trail",
      "mcp__ampel__generate_report",
      "mcp__ampel__freshness_check",
      "mcp__ampel__bridge_report",
      "mcp__ampel__register_provider",
      "mcp__ampel__check_contract",
      "mcp__ampel__assess_all",
      "mcp__ampel__onboard_entity",
      "mcp__ampel__bridge_resolve",
      "mcp__ampel__bridge_approve",
      "mcp__ampel__reg_watchdog",
      "mcp__ampel__azure_ad_check",
      "mcp__ampel__servicenow_sync",
      "mcp__ampel__llm_clause_check",
      "mcp__ampel__cross_oracle_assess",
      "mcp__ampel__health_check",
      "mcp__ampel__run_escalation",
      "mcp__ampel__whatif_provider",
      "mcp__ampel__whatif_stale",
      "mcp__ampel__board_summary",
      "mcp__ampel__update_finding",
      "mcp__ampel__retest_finding",
      "mcp__ampel__score_trend",
      "mcp__ampel__dependency_graph",
      "mcp__ampel__incident_flow",
      "mcp__ampel__evidence_pack",
      "mcp__ampel__provider_country_risk",
      "mcp__ampel__contract_upload",
      "mcp__ampel__cross_regulation_check",
      "mcp__ampel__bafin_report_draft",
      "mcp__ampel__bafin_approve_send",
      "mcp__ampel__cve_asset_map",
      "mcp__ampel__policy_draft",
      "mcp__ampel__create_trial",
      "mcp__ampel__run_trial_assessment",
      "mcp__ampel__generate_trial_report"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ampel. Review it before you use it.

Capability tags behind 2 rules
  • mcp__ampel__reg_watchdog untrusted-input
  • mcp__ampel__bafin_approve_send outbound