Skip to main content
Glama
Sign In

Aribot

by com.ayurak
OverviewDiscussionsAdmin

Server Details

Threat modeling, code, API & cloud security, shadow-AI & compliance governance.

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
9.1% over 22 days
OAuth
Requires browser extension
Last Tested
Transport
Streamable HTTP
URL
ChatGPT
–
Claude
–

TDQS

B3.4/5.0

Scored across 29 tools

Disambiguation3/5

Most tools target a distinct verb+resource (file vs get vs sync vs assign tickets; dry-run vs live remediation), but several reporting tools overlap heavily: compliance_status, get_cloud_compliance, get_framework_coverage, and get_api_security all surface compliance/posture data, and get_diagram_summary/get_insights/get_traceability all return diagram metrics. The long descriptions mitigate most confusion, but an agent could plausibly pick the wrong compliance or metrics tool.

Naming Consistency4/5

The set is dominated by a consistent snake_case verb_noun pattern (get_*, list_*, generate_*, file/sync/assign/apply_*), which makes intent predictable. A few names break the verb-first convention (code_review_scan, compliance_scan, compliance_status) and the _on_change / _in_code qualifiers are inconsistent, but these are minor deviations.

Tool Count2/5

29 tools is above the 25+ threshold that the rubric treats as too many, and the surface spans scanning, threat modeling, governance, ticketing, remediation, billing, and reporting. While the domain is genuinely broad, several tools (multiple compliance/posture getters, multiple scan starters) could likely be consolidated.

Completeness4/5

Coverage is strong across the lifecycle: scans (code, compliance, shadow AI), threat modeling (generate_architecture, generate_threat_model, verify_threats_in_code), governance (onboard_agents, get_agent_governance, run_ai_governance_audit), ticketing (file/get/sync/assign/comment), remediation (get/apply/self-healing), and billing. Minor gaps exist, such as no diagram delete/update or explicit scan-cancel operation, but core workflows are covered without dead ends.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updates
    • Addedget_agent_governance
    • Addedget_code_findings
    • Addedget_self_healing
    • Addedget_shadow_ai
  2. 2 tool updates
    • Changedcompliance_status1 field changed
      • addedInput schema / properties / framework
        Added value: +{
+  "description": "Optional framework name or id, e.g. 'ISO 27001', 'NIST'",
+  "type": "string"
+}
    • Addedlist_diagrams
  3. 2 tool updates
    • Changedapply_remediation2 fields changed
      • changedInput schema / properties / resource_context / description
        Previous value: -"provider/resource_id/region/account_id/metadata"New value: +"The cloud resource: provider, resource_id (required), region, account_id, metadata"
      • changedInput schema / required
        Previous value: -[
-  "threat_id",
-  "rule_id"
-]New value: +[
+  "threat_id",
+  "rule_id",
+  "resource_context"
+]
    • Changedget_remediation2 fields changed
      • changedInput schema / properties / resource_context / description
        Previous value: -"provider/resource_id/region/account_id/metadata"New value: +"The cloud resource: provider, resource_id (required), region, account_id, metadata"
      • changedInput schema / required
        Previous value: -[
-  "threat_id",
-  "rule_id"
-]New value: +[
+  "threat_id",
+  "rule_id",
+  "resource_context"
+]
  4. 24 tool updates
    • First observedapply_remediation
    • First observedassign_threat
    • First observedcode_review_scan
    • First observedcomment_threat_on_change
    • First observedcompliance_scan
    • First observedcompliance_status
    • First observeddiscover_shadow_ai
    • First observedfile_threat_tickets
    • First observedgenerate_architecture
    • First observedgenerate_threat_model
    • First observedget_api_security
    • First observedget_billing
    • First observedget_cloud_compliance
    • First observedget_diagram_summary
    • First observedget_framework_coverage
    • First observedget_insights
    • First observedget_remediation
    • First observedget_threat_tickets
    • First observedget_traceability
    • First observedlist_ticket_destinations
    • First observedonboard_agents
    • First observedrun_ai_governance_audit
    • First observedsync_threat_tickets
    • First observedverify_threats_in_code

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources