Der Aribot MCP MCP-Server,
verbunden mit einem Klick.

“Nutze „get_billing“: Billing status + self-service payment for your company: credit-wallet balance, pay-per-use flag, license tier / annual commitment, per-actio.”

“Nutze „onboard_agents“: Bulk-onboard agent identities to the governed fleet (Agent Governance). Accepts plain ids or {agent_id} descriptors in `agents`, A2A 1.0 Age.”

“Nutze „generate_threat_model“: Create a threat model from a normalized architecture (ReactFlow nodes + edges). Ingests components via the shared Stage-0 service; the pipel.”

“Nutze „verify_threats_in_code“: Verify whether threats are mitigated in a scan's uploaded code. With `threat_id`, verifies one threat synchronously and returns the verdict;.”

get_billing — Billing status + self-service payment for your company: credit-wallet balance, pay-per-use flag, license tier / annual commitment, per-actio

onboard_agents — Bulk-onboard agent identities to the governed fleet (Agent Governance). Accepts plain ids or {agent_id} descriptors in `agents`, A2A 1.0 Age

generate_threat_model — Create a threat model from a normalized architecture (ReactFlow nodes + edges). Ingests components via the shared Stage-0 service; the pipel

verify_threats_in_code — Verify whether threats are mitigated in a scan's uploaded code. With `threat_id`, verifies one threat synchronously and returns the verdict;

get_traceability — Return the diagram→threat→finding→control→requirement→remediation traceability matrix for a scan in your scope, with coverage metrics.

get_framework_coverage — Compliance-framework coverage for a diagram (real, ControlCodeMap-backed), optionally for one framework, plus an optional crossmap relations

get_remediation — Compute a remediation plan for a threat/finding WITHOUT applying it (mode=dry_run). Runs the same governed engine as apply_remediation, incl

compliance_status — Company-level compliance posture rollup (pass rate, control compliance, mitigated counts, per-framework coverage). Suitable for a CI gate. W