Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Ampel is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
50
tools declared
remote
at its publisher
—
calls last 7d
What it does
AmpelOracle — 50-tool compliance traffic-light: Go/Caution/Stop signals for ESG, MiCA, AML.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ampel-mcp https://tooloracle.io/ampel/mcp/
# 2 — ask your agent for something these tools do
# readiness_check, article_status, gap_report and 47 more
Ampel costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TOAll 61 servers
tooloracle61 servers
14 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http ampel-mcp https://tooloracle.io/ampel/mcp/Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
50 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Full DORA readiness score + Ampel per article. Returns GREEN/YELLOW/RED/GREY for all 26 articles, score 0-100, days until deadline.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID (optional) |
Detailed Ampel for a specific DORA article. Each check with GREEN/YELLOW/RED conditions and evidence.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| article | string | no | e.g. Art. 28 |
| entity_id | string | no | Entity ID |
DORA compliance gaps. RED/GREY/YELLOW items with priority and required actions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID (optional) |
All evidence artefacts for an entity with hashes and expiry dates.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID (optional) |
Collect live Art. 10 evidence from NVD, CISA KEV, CERT-Bund. Auto-assesses.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID (optional) |
List all registered regulated entities.
No parameter schema on file.
Register a new regulated entity.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Entity name |
| entity_type | string | no | Type |
| lei | string | no | — |
| jurisdiction | string | no | — |
Chain-linked audit log with integrity check.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | — |
| limit | integer | no | Max entries |
Generate data-driven DORA Ampel PDF report. Score, gap analysis, provider register, audit trail integrity.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID (optional) |
| format | string | no | json (meta) or pdf (download) |
Run freshness watchdog. Expires stale evidence, downgrades GREEN->YELLOW->GREY if evidence too old.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID (optional, checks all) |
Bridge gap analysis: classifies gaps by DATA/EVIDENCE/POLICY/WORKFLOW with closure path, owner, effort level.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID (optional) |
Register an ICT third-party provider for DORA Art. 28 Register of Information. Stores provider data and creates evidence.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider_name | string | no | Provider name e.g. Amazon Web Services EMEA SARL |
| provider_type | string | no | cloud_infrastructure, saas_application, core_banking, cybersecurity, etc. |
| criticality | string | no | critical, important, standard |
| headquarters | string | no | Country e.g. Luxembourg, Germany |
| lei | string | no | Legal Entity Identifier |
| services | string | no | Services provided |
| data_location | string | no | Where data is stored e.g. EU (Frankfurt) |
| contract_start | string | no | — |
| contract_end | string | no | — |
| annual_cost_eur | number | no | — |
| substitutability | string | no | — |
| certifications | string | no | — |
| entity_id | string | no | — |
Check DORA Art. 30 contract clauses for a provider. Returns PASS/WARN/BLOCK with missing clauses and bridge classification.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider_id | string | no | Provider ID |
| standard_clauses | array | no | Present standard clauses: service_description, data_location, data_protection, service_availability_sla, incident_notification, audit_right, termination_notice, cooperation_with_authorities |
| cif_clauses | array | no | CIF clauses if applicable |
| is_cif | boolean | no | Is this a CIF (Critical/Important Function) provider? |
| exit_strategy | boolean | no | Exit strategy documented? |
| entity_id | string | no | — |
Re-run full assessment for an entity. Recomputes Ampel statuses from all available evidence.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID (optional) |
Full entity onboarding: creates initial RED assessments for all 39 checks, collects auto-evidence from live sources, re-assesses, and returns readiness score.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID to onboard |
Start bridge resolution workflow. Generates templates (Risk Acceptance, Contract Renegotiation, Concentration Policy, Exit Strategy), tracks approval process. Call bridge_approve to sign off.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check_id | string | no | Check to resolve: art30_c1, art30_c2, art30_c3, art8_c3, art31_c1 |
| entity_id | string | no | Entity ID (optional) |
| expiry_days | integer | no | Days until resolution expires (default 30) |
Approve or reject a bridge resolution. On approval: creates signed evidence, upgrades Ampel to GREEN, logs to audit chain.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| resolution_id | string | no | Resolution ID from bridge_resolve |
| approved_by | string | no | Name + role of approver (e.g. Dr. Mueller, CISO) |
| reject | boolean | no | Set true to reject instead of approve |
| rejection_reason | string | no | Reason for rejection (if rejecting) |
Check status of all bridge resolution workflows for an entity. Shows open, pending, closed, rejected.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID (optional) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days_back | integer | no | Check items from last N days (default: 7) |
Live Azure AD integration: MFA registration %, risky users, conditional access policies. DORA Art. 9 evidence. Requires Azure AD config in integrations_config.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| force_refresh | boolean | no | Force fresh API call (default true) |
ServiceNow incident + change management sync. DORA Art. 17/21 evidence. Returns 30-day incident stats, classification, resolution rates.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days_back | integer | no | Days to look back (default 30) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contract_text | string | no | Contract text (plain text from PDF). Paste key sections. |
| provider_name | string | no | Provider name e.g. Salesforce |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity to assess |
| checks | string | no | Comma-separated check IDs or omit for all |
Server + DB status.
No parameter schema on file.
Quick connectivity test.
No parameter schema on file.
Oracle Event Bus status: events, cross-refs, connected oracles.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID for cross-refs |
Get findings, SLA breaches, escalation status per entity.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID (empty=all) |
Trigger escalation engine: auto-create findings, check SLA, escalate.
No parameter schema on file.
Simulate provider failure: which articles/checks are affected, score impact, risk level.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID |
| provider_name | string | no | Provider name (e.g. AWS, Finastra) |
Simulate stale evidence: what happens if a check stays stale for N days.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID |
| check_id | string | no | Check ID |
| days | integer | no | Days stale (default 30) |
Executive board summary: overall score, top 5 risks, overdue findings, SLA breaches, concentration risk, evidence health, owner workload. Designed for management/board reporting.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID |
Update finding lifecycle: claim, set remediation plan, request re-test, close, or accept risk. Status flow: open -> in_progress -> retest_pending -> closed | risk_accepted.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| finding_id | string | no | Finding ID |
| action | string | no | claim | plan | request_retest | close | accept_risk |
| owner | string | no | New owner (for claim) |
| remediation_plan | string | no | Remediation plan text (for plan) |
| accepted_by | string | no | Name (for accept_risk) |
| expiry_days | integer | no | Risk acceptance expiry days (default 90) |
| reason | string | no | Close reason (for close) |
| actor | string | no | Who is performing this action |
Re-test a finding: collect fresh evidence, reassess check, auto-close if GREEN. Full closed-loop.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| finding_id | string | no | Finding ID to re-test |
Score trend over time: weekly deltas, trajectory, peer benchmark. Shows improvement or decline.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID |
Full provider dependency graph: providers, systems, checks, blast radius, SPOF detection.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID |
DORA incident lifecycle: log, classify, notify (BaFin), close. Each step creates signed evidence.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID |
| action | string | no | log | classify | notify | close |
| title | string | no | — |
| description | string | no | — |
| severity | string | no | — |
| incident_id | string | no | — |
| classification | string | no | — |
| report_type | string | no | — |
| root_cause | string | no | — |
| lessons_learned | string | no | — |
Export evidence pack for article/check/entity. Pruefer-ready: evidence, assessments, findings, audit trail, signatures.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID |
| article | string | no | DORA article e.g. Art. 10 |
| check_id | string | no | Specific check ID |
Enrich provider dependencies with OECD economic risk: GDP, unemployment, CLI per provider country. DORA Art. 28-31 relevant.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID |
Upload contract text for DORA Art. 30 analysis. Creates document record with SHA-256 hash, version tracking, audit trail.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID |
| provider_name | string | no | Provider name |
| contract_text | string | no | Contract text (extracted from PDF) |
| file_name | string | no | Original file name |
| document_type | string | no | ict_outsourcing_agreement | dpa | sla | master_service_agreement |
Analyze contract against 15 DORA Art. 30 mandatory clauses. Returns compliance status per clause with confidence score, extracted text, gap reasoning, suggested fix.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document_id | string | no | Document ID from contract_upload |
Overview of all analyzed contracts per entity. Shows clause gaps, review status, document versions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID |
Tag findings with cross-regulation impact (DORA + MiCA + AMLR). Shows which DORA findings also affect MiCA insider info or AMLR screening.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | Entity ID |
Show cross-regulation impacts for a specific DORA article. Maps DORA → MiCA + AMLR.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dora_article | string | no | DORA article ID (e.g. dora_art28) |
Generate ITS 2024/1772 compliant BaFin incident report draft. All mandatory fields per DORA Art. 19/20. Preview mode — requires board approval.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | — |
| incident_id | string | no | — |
| report_type | string | no | initial | intermediate | final |
| title | string | no | — |
| description | string | no | — |
| classification | string | no | major | significant | minor |
| affected_services | string | no | — |
| affected_clients | string | no | — |
| root_cause | string | no | — |
| remediation | string | no | — |
Approve BaFin report for submission (4-eyes principle). Creates signed approval evidence.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | — |
| report_id | string | no | — |
| approver_name | string | no | — |
| approver_role | string | no | — |
Map CVE/vulnerability to internal ICT providers and systems. Auto-creates findings for critical matches. DORA Art. 10.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | — |
| cve_id | string | no | CVE identifier |
| vendor | string | no | Vendor/software name to check |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | — |
| dora_article | string | no | dora_art5|dora_art6|dora_art8|dora_art10|dora_art11|dora_art17|dora_art28|dora_art30 |
Create temporary trial entity (48h) for self-service DORA assessment. No login needed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_name | string | no | Institute name |
| entity_type | string | no | credit_institution|payment_institution|insurance_undertaking|asset_management|credit_institution_casp |
| jurisdiction | string | no | DE|AT|FR|etc |
| providers | string | no | Comma-separated provider names: AWS,SWIFT,Finastra |
Run complete DORA+MiCA assessment for trial entity. Returns score, gaps, automation potential.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trial_id | string | no | — |
| entity_id | string | no | — |
Generate watermarked trial report with score, gaps, and CTA.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trial_id | string | no | — |
| entity_id | string | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Ampel or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestf61e7ee8fb954a08136467b247c1aa1dc9c06ecf9de539356bd718745ac025d3
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| readiness_check | no tags | |
| article_status | no tags | |
| gap_report | no tags | |
| evidence_summary | no tags | |
| collect_art10 | no tags | |
| entity_list | no tags | |
| create_entity | no tags | |
| audit_trail | no tags | |
| generate_report | no tags | |
| freshness_check | no tags | |
| bridge_report | no tags | |
| register_provider | no tags | |
| check_contract | no tags | |
| assess_all | no tags | |
| onboard_entity | no tags | |
| bridge_resolve | no tags | |
| bridge_approve | no tags | |
| bridge_status | no tags | |
| reg_watchdog | no tags | |
| azure_ad_check | no tags | |
| servicenow_sync | no tags | |
| llm_clause_check | no tags | |
| cross_oracle_assess | no tags | |
| health_check | no tags | |
| ping | no tags | |
| bus_status | no tags | |
| escalation_status | no tags | |
| run_escalation | no tags | |
| whatif_provider | no tags | |
| whatif_stale | no tags | |
| board_summary | no tags | |
| update_finding | no tags | |
| retest_finding | no tags | |
| score_trend | no tags | |
| dependency_graph | no tags | |
| incident_flow | no tags | |
| evidence_pack | no tags | |
| provider_country_risk | no tags | |
| contract_upload | no tags | |
| contract_analyze | no tags | |
| contract_status | no tags | |
| cross_regulation_check | no tags | |
| regulation_impact | no tags | |
| bafin_report_draft | no tags | |
| bafin_approve_send | no tags | |
| cve_asset_map | no tags | |
| policy_draft | no tags | |
| create_trial | no tags | |
| run_trial_assessment | no tags | |
| generate_trial_report | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestf61e7ee8fb954a08
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Ampel can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.