mcp server
aribot-mcp
Threat modeling, code, API & cloud security, shadow-AI & compliance governance.
Description as published by the maintainer. Source
- version 1.0.1
- active
- security
active — Registry entry last updated 2026-07-05. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
16 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
apply_remediation(rule_id, threat_id, resource_context)- Apply a remediation for real (mode=live). Routed through the full governance funnel — patent reachability/kill-chain gates, autonomy policy and the approval flow. If your policy requires approval it returns 'requires_approval' rather than acting. Required: threat_id, rule_id.
code_review_scan(scan_id)- Start (or re-run) a code-security scan for an existing scan/repository in your scope. Returns a poll pointer; results include SAST, secrets, deps, pipeline review and the traceability matrix. Required: scan_id.
compliance_scan(source, scan_type, account_id, diagram_id, frameworks, severity_filter, simulation_mode)- Run a cloud/platform or compliance scan against an account or diagram in your scope (async). scan_type ∈ platform|compliance|pipeline|sbom. Returns a task id to poll. Required: scan_type.
compliance_status(scan_id, diagram_id)- Company-level compliance posture rollup (pass rate, control compliance, mitigated counts, per-framework coverage). Suitable for a CI gate. Wraps the traceability company rollup.
discover_shadow_ai(limit, scan_id)- Shadow-AI posture (part of Code Security): unsanctioned / unknown AI-service usage discovered in code — totals, risk score, provider/type breakdown, hardcoded-key count, and top discoveries. Company latest, or one scan with `scan_id`. Reads code_review ShadowAIReport/ShadowAIDiscovery.
generate_threat_model(name, edges, nodes)- Create a threat model from a normalized architecture (ReactFlow nodes + edges). Ingests components via the shared Stage-0 service; the pipeline then auto-generates threats. Returns the diagram id. Required: nodes.
get_api_security(limit, scan_id)- API security inventory (part of Code Security): discovered API endpoints with authentication status, risk level and risk factors, plus method/risk breakdowns. Company-wide or one scan with `scan_id`. Reads code_review ApiEndpointDiscovery.
get_billing(request_plan, topup_amount, checkout_request_id)- Billing status + self-service payment for your company: credit-wallet balance, pay-per-use flag, license tier / annual commitment, per-action prices, purchasable plans, and any approved-but-unpaid plans. Pass `checkout_request_id` to get a hosted Stripe Checkout URL to COMPLETE an approved plan, `topup_amount` (EUR) to get one to TOP UP the wallet, or `request_plan` (starter|pay_per_use|pro|max|enterprise) to REQUEST a plan (files a request for super-admin approval — never grants). Use this to view or RESOLVE a 402 without leaving the connector.
get_cloud_compliance(account_id)- Cloud security & compliance posture (Cloud Compliance): per connected cloud account, the latest CIS/NIST cloud-policy scan — compliance %, failing policies/records, status — plus a company rollup. Reads customers.Account.latest_scan -> compliances.ScanResults.
get_diagram_summary(diagram_id)- The canonical diagram summary every badge/card/header reads: threat counts by severity, risk value, compliance and framework coverage. Required: diagram_id.
get_framework_coverage(framework, diagram_id, include_graph)- Compliance-framework coverage for a diagram (real, ControlCodeMap-backed), optionally for one framework, plus an optional crossmap relationship graph. Wraps derive_framework_coverage + crossmap_cypher.build_graph. Required: diagram_id.
get_insights(diagram_id)- Threat/control matrix metrics + framework coverage for a diagram, joined with its latest code-security scan when one exists. Required: diagram_id.
get_remediation(rule_id, threat_id, resource_context)- Compute a remediation plan for a threat/finding WITHOUT applying it (mode=dry_run). Runs the same governed engine as apply_remediation, including the patent gates, and returns the proposed steps. Required: threat_id, rule_id.
get_traceability(scan_id)- Return the diagram→threat→finding→control→requirement→remediation traceability matrix for a scan in your scope, with coverage metrics. Required: scan_id.
onboard_agents(agents, cohort, agent_cards, auto_suspend_threshold)- Bulk-onboard agent identities to the governed fleet (Agent Governance). Accepts plain ids or {agent_id} descriptors in `agents`, A2A 1.0 Agent Cards in `agent_cards` (name/url/provider/version/protocolVersion), or MCP client descriptors, under an optional `cohort` + shared auto-suspend policy. Idempotent. Requires the agent_governance licence + a manage:agents grant (or a first-party super-admin). Agents also self-onboard on first token/call.
verify_threats_in_code(async_, scan_id, threat_id, code_content, repository_id)- Verify whether threats are mitigated in a scan's uploaded code. With `threat_id`, verifies one threat synchronously and returns the verdict; without it, verifies every diagram threat in the background. Wraps code_review ThreatVerificationService. Required: scan_id.
Last successful function declaration observed on . Source: https://mcp.aribot.ayurak.com/. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.aribot.ayurak.com/.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-05 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-05 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 16 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.aribot.ayurak.com | |
| mcp endpoint status | ok | The server listed 16 functions when asked. | as of probe | mcp.aribot.ayurak.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json