Aribot MCP vs Kastell
A side-by-side look at the Aribot MCP and Kastell MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
Aribot MCPSecurity · Remote HTTP/SSEGoverned threat modeling, code threat verification, traceability & compliance, as MCP tools.42FairAuth: not declaredVerdict: choose Aribot MCP for security work over a hosted endpoint; choose Kastell for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose Aribot MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
Choose Kastell when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Aribot MCP | |
|---|---|---|
| Category | Security | Security |
| Quality signal | 42/100 · Fair | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 60 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Aribot MCP | View Kastell |
Tools & capabilities
Aribot MCP tools
No tool names declared yet. Check the project README from the listing page.
Kastell tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Aribot MCP
{
"mcpServers": {
"aribot-mcp": {
"url": "https://api.aribot.ayurak.com/aribot/claude-connector"
}
}
}
Kastell
{
"mcpServers": {
"kastelldev-kastell": {
"command": "npx",
"args": [
"-y",
"kastell"
]
}
}
}
Frequently asked questions
Aribot MCP is categorized under Security and uses a remote HTTP/SSE transport. Kastell belongs to Security and uses a local stdio subprocess. Pick Aribot MCP for security work and Kastell for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Aribot MCP has no declared pricing — check the project's own site. Kastell is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add aribot-mcp and kastelldev-kastell as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Aribot MCP has a quality signal of 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Kastell has 61/100 (Good) with 5 views, 0 installs and 60 GitHub stars.