
Infraveil Control Plane
io.github.infraveilhqPublished by GitHub account infraveilhqv0.1.1Updated Oct 24, 2026
Govern your backend control plane from your AI agent - signed, human-approval-gated.
Overview
Lets an AI assistant act on an Infraveil backend control plane through signed, human-approval-gated requests.
- What you can do
- This local MCP server connects an assistant to an Infraveil control plane so it can govern backend operations from the agent. Requests are signed with the agent's existing token, and the description states that actions are gated behind human approval. The manifest lists no tools, so the exact operations available are not shown here.
- When to use it
- Consider it when you already run an Infraveil control plane and want an assistant to carry out governed backend actions on your behalf, with signing and approval checks in the loop.
- Requirements
- Runs as a local process on the user's machine, installed from the PyPI package infraveil-mcp over stdio; desktop only. Needs INFRAVEIL_AGENT_ID, INFRAVEIL_AGENT_TOKEN, INFRAVEIL_BASE_URL and INFRAVEIL_CLIENT_ID, or alternatively INFRAVEIL_AGENT_FILE pointing at a rendered agent source that supplies the ids and token. Network access to the control plane is required.
Installation
In SourceWeft
- Open Infraveil Control Plane in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 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.