io.github.shittuay/devops-agent

MCPcommunitydegraded
v1.0.6io.github.shittuayUnknownUpdated 5mo 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.…

Endpoint healthdegraded
checked 7 days ago · last reachable 7 days ago · 119ms · 2 endpoints · auth required
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http, sse). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorio.github.shittuay
LicenseUnknown
Version1.0.6
Sourcemcp-registry
npm@devopsagent/mcp-server
GitHubshittuay/DevOps-Agent
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ 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>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
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 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 1 source file from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

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
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in devops & infrastructure