When was npm:cloudpulse-mcp last audited?

Last checked 2026-06-03; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

B+

npm:cloudpulse-mcp

Item: npm:cloudpulse-mcp
Rating: 89
Author: wmcp.sh

https://www.npmjs.com/package/cloudpulse-mcp

89/100 · MCP Trust Grade · checked 1mo ago · MCP 0.1.2

Is the npm:cloudpulse-mcp MCP server safe to use?

Independent trust grade B+ (89/100). Static analysis of npm package cloudpulse-mcp@0.1.2 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured. wmcp.sh continuously watches npm:cloudpulse-mcp for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

What it offers — 4 tools · Cloud & DevOps

list_cloud_topology

Scan all configured cloud platforms (AWS, Vercel, GCP, Cloudflare) and return a unified topology of active services including their endpoints and regi

get_correlated_logs

Fetch logs from multiple cloud platforms (AWS CloudWatch + Vercel) for a given time window and optional trace ID, then merge them into a single chrono

diagnose_service_link

Diagnose connectivity issues between a source service and a target resource. Checks Vercel environment variables, AWS Security Group inbound rules on

check_resource_limits

Query quota limits and current usage across configured cloud platforms. Highlights resources approaching or exceeding their limits (default warning th

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 4 tool(s) detected in source

Security (OWASP MCP)30%90

no high-risk patterns in sampled source
scanned 6 source files

Maintenance / popularity20%92

published within 90 days
3 published versions

Tool hygiene15%70

no TypeScript types
12 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license
17 weekly downloads

Findings

INFO Static analysis of npm package cloudpulse-mcp@0.1.2 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:cloudpulse-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:cloudpulse-mcp grade B+

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3Acloudpulse-mcp

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade B+](https://wmcp.sh/mcp/grade/npm%3Acloudpulse-mcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Acloudpulse-mcp)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3Acloudpulse-mcp"><img src="https://wmcp.sh/mcp/grade/npm%3Acloudpulse-mcp/badge.svg" alt="MCP Trust Grade B+ · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.