Developer · Remote MCP server
Aribot MCP
Threat modeling, code, API & cloud security, shadow-AI & compliance governance.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.ayurak/aribot-mcp- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, SSE (HTTP + Server-Sent Events)
- Published
- 2026-07-05
- Updated
- 2026-07-05
- Publisher
- com.ayurak
- Namespace
- Namespace verified by the MCP Registry via the domain ayurak.com · how
- Website
- api.aribot.ayurak.com/aribot/claude-connector
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.aribot.ayurak.com/ | None |
| SSE (HTTP + Server-Sent Events) | https://mcp.aribot.ayurak.com/sse | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://mcp.aribot.ayurak.com/(HTTP)- Reachable
- Yes (HTTP 200)
- Handshake
- aribot-mcp 1.0.0 · protocol 2024-11-05
- Tools discovered
18 - show names
get_billing,onboard_agents,generate_threat_model,verify_threats_in_code,get_traceability,get_framework_coverage,get_remediation,compliance_status,discover_shadow_ai,get_api_security,get_cloud_compliance,code_review_scan,compliance_scan,apply_remediation,get_diagram_summary,get_insights,generate_architecture,run_ai_governance_audit- Checked on
- 2026-10-05
- Endpoint
https://mcp.aribot.ayurak.com/sse(SSE)- Reachable
- Yes (HTTP 401)
- SSE stream
- Not opened: sign-in required
- Sign-in required
- Yes - HTTP 401; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect Aribot MCP
Aribot MCP is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.aribot.ayurak.com/, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
It also lists an endpoint on the older SSE transport https://mcp.aribot.ayurak.com/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| AriadneLocal-first multilingual, auditable memory for Codex, Claude Code, and MCP clients. | Local · stdio |
| ariadneReturns only the unit tests affected by your current Kotlin/Android code changes. | Local · stdio |
| AriadneDeterministic local cross-service API-chain discovery for AI coding agents. | Local · stdio |
| AribotThreat modeling, code/cloud/pipeline scanning, shadow-AI discovery, compliance checks and fixes. | Remote · HTTPLive check: ✓ handshake |
| ArketoDraw your app's architecture on a live canvas and flag the bottlenecks and security gaps. | Remote · HTTPLive check: sign-in required |
| arkheiaai MCP-SERVERDetect fabrication and hallucination in any LLM output. 30+ models supported. | Local · stdio |
| ArkHive MCPTamper-evident memory + governance MCP for Claude Code, Cursor, Codex. Ships the Seatbelt kit. | Local · stdio |
| ArletCreate, deploy, and operate MCP servers directly from your GitHub repositories. | Remote · HTTPLive check: sign-in required |