
aictrl
io.github.vasparshinPublished by GitHub account vasparshinv1.0.0-beta.1Updated Oct 25, 2026
Governance layer for AI coding agents: knowledge-graph grounding, session audit, policy controls.
The publisher's own server: aictrl
Overview
A remote governance layer for AI coding agents, offering knowledge-graph grounding, session audit and policy controls through a hosted endpoint.
- What you can do
- Ground coding-agent work in a knowledge graph so responses draw on structured context rather than guesswork. Audit agent sessions to review what an assistant did. Apply policy controls that govern how the agent operates. The manifest lists no individual tools, so the exact operations are not documented here.
- When to use it
- Consider it when you run AI coding agents and want oversight: grounding their output in a knowledge graph, keeping an audit trail of sessions, or enforcing policy limits on what they may do.
- Requirements
- A remote MCP endpoint at aictrl.dev over streamable HTTP; no local package or runtime is needed. An aictrl API key is required, supplied in the X-API-Key header and obtained from the provider's site. Network access to the endpoint is required.
Installation
In SourceWeft
- Open aictrl in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.vasparshin%2Faictrl/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"aictrl": {
"type": "http",
"url": "https://aictrl.dev/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.0-beta.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.
