@cyanheads/devops-status-mcp-server

MCPcommunity
v0.5.0io.github.cyanheadsUnknownUpdated 1d agonpmGitHub

Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1d agoLast update
Package
Authorio.github.cyanheads
LicenseUnknown
Version0.5.0
Sourcenpm+mcp-registry
npm@cyanheads/devops-status-mcp-server
GitHubcyanheads/devops-status-mcp-server
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✓ 60 resolved+ · none vulnerable
Tool surface2 tools · none privileged
Security scan✓ Cleanv0.2.3 · 19d ago
EvalsNone
IndexedJun 12, 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

Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.

Keywords
mcp