Home / MCP registry index / Topics / Infrastructure as code

Infrastructure as code MCP servers, with their tools checked

Every server in the official MCP registry that mentions Infrastructure as code, with a public endpoint, read the way an MCP client reads it and checked for tool poisoning. The list updates as the registry does, and each server is read again every week.

6 listed. We have read the tools of 0 so far; the others want credentials first, could not be reached, or are still waiting for their first read.

Infrastructure servers can change live systems. Check which tools write, deploy or delete before you connect one with real credentials.

DevOps & Cloud Code Auditor io.github.Ansarii/devops-code-auditor	not read yet
io.github.Baneado98/cloud-pathfinder io.github.Baneado98/cloud-pathfinder	not read yet
FoggyKitchen MCP io.github.foggykitchen/foggykitchen-mcp	not read yet
Terraform block count, body discarded io.github.sadri-dridi/terraform-ok	not read yet
DevOps Agent io.github.shittuay/devops-agent	not read yet
work.agentexchange.planets/agent-planets work.agentexchange.planets/agent-planets	not read yet

Choosing one

Open a server's page to see the tools it advertises, whether it sets instructions for the model, and our latest read. A clean read means our rules found nothing, not that a server is harmless; still check what access it asks for. To check one that is not listed, paste its URL into the free MCP server check.