io.github.shittuay/devops-agent

MCPcommunity
v1.0.6io.github.shittuayUnknownUpdated 2mo agonpmGitHub

Manage AWS, Azure, GCP, Kubernetes, CI/CD, Docker, Terraform and more. 727 tools.

Manage AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, Docker, Ansible, and more from any MCP-compatible AI client. 727 tools across 17 modules — all accessible via a single connection. Node.js 18+ — required to run the stdio bridge via An API key from devopsagent.io (see Getting Your API Key) No npm account needed — you're just a user of the published package 1. Log in at devopsagent.io 2.…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2mo agoLast update
Package
Authorio.github.shittuay
LicenseUnknown
Version1.0.6
Sourcemcp-registry
npm@devopsagent/mcp-server
GitHubshittuay/DevOps-Agent
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 0 resolved · none vulnerable
Tool surface—
Security scan✓ Cleanv1.0.6 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Manage AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, Docker, Ansible, and more from any MCP-compatible AI client. 727 tools across 17 modules — all accessible via a single connection. Node.js 18+ — required to run the stdio bridge via An API key from devopsagent.io (see Getting Your API Key) No npm account needed — you're just a user of the published package 1. Log in at devopsagent.io 2. Navigate to Settings → API Keys 3. Click Generate Key — your key will be prefixed with 4. Copy it and use…

Keywords
mcp