Developer · Remote MCP server
aictrl
Governance layer for AI coding agents: knowledge-graph grounding, session audit, policy controls.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.vasparshin/aictrl- Version
- 1.0.0-beta.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-07
- Updated
- 2026-08-07
- Publisher
- vasparshin (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/vasparshin) · how
- Repository
- github.com/vasparshin/aictrl-team-skills
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://aictrl.dev/mcp | X-API-Key (required, secret) |
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.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect aictrl
aictrl is a remote MCP server: there is nothing to install. Its endpoint is https://aictrl.dev/mcp, 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.
The registry entry declares an HTTP header for the connection: X-API-Key (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
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 |
|---|---|
| aicommander.devRemote shell and detached long-running jobs on your own machines - no SSH, open ports or VPN. | Remote & Local · HTTP, stdioLive check: sign-in required |
| AIContextBuilderSymbol-aware C# and.NET code context for AI coding assistants. | Local · stdio |
| aicooliesSearch and read the aicoolies catalog of AI and developer tools via a remote MCP knowledge graph. | Remote · HTTPLive check: ✓ handshake |
| AicoreutilsJSON-first Coreutils CLI for AI agents. 114 commands with sandbox, dry-run, and MCP support. | Local · stdio |
| aide-memoryPersistent memory layer for AI coding agents - your agent remembers what you taught it. | Local · stdio |
| AidexPersistent code indexing for AI assistants. 50x less context than grep. 11 languages. | Local · stdio |
| AidimagPersistent, verified memory for AI coding agents: recall, capture, guardrails, review queue. | Local · stdio |
| AiEGISAI agent security and governance. Register, verify, scan, and monitor agents. | Remote · SSELive check: ✗ no handshake |