aribot
Server Details
Threat modeling, code/cloud/pipeline scanning, shadow-AI discovery, compliance checks and fixes.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 99.3% over 64 days
- OAuth
- Requires browser extension
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- aristiun/aribot-mcp
- GitHub Stars
- 0
- Server Listing
- Aribot MCP
TDQS
Scored across 29 tools
Many tools are clearly distinct, but several compliance/metrics retrieval tools overlap: compliance_status, get_cloud_compliance, get_framework_coverage, and run_ai_governance_audit all report compliance or audit posture. Similarly, get_diagram_summary, get_insights, and get_traceability all surface diagram-level security metrics. Descriptions help, but an agent may still misselect among these.
The set is predominantly snake_case with a predictable verb_noun pattern (get_*, list_*, apply_*, assign_*, file_*, sync_*). Minor deviations exist: code_review_scan, compliance_scan, and compliance_status lead with nouns. Overall the naming is readable and consistent enough for an agent to follow.
The server exposes 29 tools across a broad AI-security governance domain, which is heavy. While some tools serve distinct subdomains, the count exceeds 25 and increases the selection surface. This is too many for a well-scoped set according to the calibration.
Core workflows for scans, threat models, remediation, tickets, agent governance, and billing are present. However, there are no update/delete operations for diagrams, threat models, or agent identities, and threat management is mostly assign/file/verify rather than full lifecycle. These are notable gaps for a management platform.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
4 tool updates
- Added
get_agent_governance - Added
get_code_findings - Added
get_self_healing - Added
get_shadow_ai
2 tool updates
- Changed
compliance_status1 field changed- added
Input schema / properties / frameworkAdded value: +{ + "description": "Optional framework name or id, e.g. 'ISO 27001', 'NIST'", + "type": "string" +}
- Added
list_diagrams
2 tool updates
- Changed
apply_remediation2 fields changed- changed
Input schema / properties / resource_context / descriptionPrevious value: -"provider/resource_id/region/account_id/metadata"New value: +"The cloud resource: provider, resource_id (required), region, account_id, metadata" - changed
Input schema / requiredPrevious value: -[ - "threat_id", - "rule_id" -]New value: +[ + "threat_id", + "rule_id", + "resource_context" +]
- Changed
get_remediation2 fields changed- changed
Input schema / properties / resource_context / descriptionPrevious value: -"provider/resource_id/region/account_id/metadata"New value: +"The cloud resource: provider, resource_id (required), region, account_id, metadata" - changed
Input schema / requiredPrevious value: -[ - "threat_id", - "rule_id" -]New value: +[ + "threat_id", + "rule_id", + "resource_context" +]
6 tool updates
- Added
assign_threat - Added
comment_threat_on_change - Added
file_threat_tickets - Added
get_threat_tickets - Added
list_ticket_destinations - Added
sync_threat_tickets
2 tool updates
- Added
generate_architecture - Added
run_ai_governance_audit
4 tool updates
- Changed
compliance_status2 fields changed- changed
Input schema / properties / diagram_id / descriptionPrevious value: -"Optional diagram to add framework coverage for"New value: +"Optional diagram id filter" - changed
Input schema / properties / scan_id / descriptionPrevious value: -"Optional anchor scan; latest is used if omitted"New value: +"Optional scan id filter"
- Changed
discover_shadow_ai3 fields changed- removed
Input schema / properties / limitRemoved value: -{ - "default": 15, - "description": "Max discoveries to return", - "type": "integer" -} - changed
Input schema / properties / scan_id / descriptionPrevious value: -"Optional CodeReviewScan id; company-wide latest if omitted"New value: +"Scan id with uploaded code or repository" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "scan_id" +]
- Changed
get_framework_coverage4 fields changed- changed
Input schema / properties / diagram_id / descriptionPrevious value: -"Diagram pk or uuid"New value: +"Diagram id/uuid" - changed
Input schema / properties / framework / descriptionPrevious value: -"Optional framework filter (e.g. 'NIST-800-53', 'SOC2')"New value: +"Optional framework filter (e.g. eu-ai-act, dora, nist, iso)" - removed
Input schema / properties / include_graph / defaultRemoved value: -false - changed
Input schema / properties / include_graph / descriptionPrevious value: -"Also return the crossmap node/edge graph"New value: +"Include crossmap relationship graph"
- Changed
verify_threats_in_code5 fields changed- removed
Input schema / properties / async_Removed value: -{ - "default": true, - "type": "boolean" -} - changed
Input schema / properties / code_content / descriptionPrevious value: -"Optional inline code context"New value: +"Optional inline code snippet to verify" - changed
Input schema / properties / repository_id / descriptionPrevious value: -"Optional connected repo to fetch code from"New value: +"Optional repository id" - changed
Input schema / properties / scan_id / descriptionPrevious value: -"CodeReviewScan id (uuid)"New value: +"Code review scan id" - changed
Input schema / properties / threat_id / descriptionPrevious value: -"Optional: a single threat id or code"New value: +"Optional specific threat id/code to verify"
1 tool update
- Added
onboard_agents
15 tool updates
- First observed
apply_remediation - First observed
code_review_scan - First observed
compliance_scan - First observed
compliance_status - First observed
discover_shadow_ai - First observed
generate_threat_model - First observed
get_api_security - First observed
get_billing - First observed
get_cloud_compliance - First observed
get_diagram_summary - First observed
get_framework_coverage - First observed
get_insights - First observed
get_remediation - First observed
get_traceability - First observed
verify_threats_in_code
Related MCP Connectors
Threat modeling, code, API & cloud security, shadow-AI & compliance governance.
Security scanner for AI-written code: SAST, secrets, dependencies, IaC, containers and DAST.
Security reviews, threat models over a repo or website, and remediation tracking, in your editor.
Zero-config MCP security scanner for AI-generated apps. 25K+ vulnerability patterns.
Related MCP Servers
- AlicenseBqualityDmaintenanceUniversal AI security layer for code scanning, PII detection, prompt injection defense, secret detection, dependency auditing, and audit logging.2727 PyPI3Apache 2.0

Draugrofficial
AlicenseNot gradedqualityAmaintenanceSecurity scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.8Apache 2.0- AlicenseAqualityDmaintenanceSecurity scanning for AI coding tools (Claude Code, Cursor, Windsurf) including secrets detection, MCP config vulnerabilities, agent instruction checks, threat modeling, prompt injection testing, pre-commit security checks, and dependency vulnerability scanning.722 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered security scanning of codebases through conversational analysis, allowing users to assess, threat model, code review, DAST test, and generate security reports using natural language with Claude.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.