Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.lhf552004/cloudpulse

NPM · CLOUDPULSE-MCP · SCANNED SEP 20

Cross-cloud observability for AI agents. Covers AWS, GCP, Vercel, and Cloudflare.

Available components

npm · cloudpulse-mcp 78
0 this week 78 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security90
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects uuid 9.0.1, reached via @google-cloud/logging > google-gax > uuid. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 78 of 277 dependencies flagged as unhealthy (3 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 647 tokens (~161/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 89% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.lhf552004/cloudpulse MCP server?

io.github.lhf552004/cloudpulse runs locally as an npm package, launched with npx -y cloudpulse-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · cloudpulse-mcp

# add to Claude Code
claude mcp add lhf552004-cloudpulse -- npx -y cloudpulse-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "lhf552004-cloudpulse": {
      "command": "npx",
      "args": [
        "-y",
        "cloudpulse-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "lhf552004-cloudpulse": {
      "command": "npx",
      "args": [
        "-y",
        "cloudpulse-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add lhf552004-cloudpulse -- npx -y cloudpulse-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lhf552004-cloudpulse": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "cloudpulse-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add lhf552004-cloudpulse --command npx --arg -y --arg cloudpulse-mcp
# ~/.hermes/config.yaml
mcp_servers:
  lhf552004-cloudpulse:
    command: "npx"
    args: ["-y", "cloudpulse-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "lhf552004-cloudpulse": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "cloudpulse-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add lhf552004-cloudpulse -t stdio -c npx -a -y cloudpulse-mcp
// mcp.json
{
  "mcpServers": {
    "lhf552004-cloudpulse": {
      "command": "npx",
      "args": [
        "-y",
        "cloudpulse-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 19 Sept 26 +1
    • Stability: 0.97 → pass security
  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 13 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 12 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 11 Sept 26 +1
    • Stability: 0.97 → pass security
  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/cloudpulse-mcp@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 277 packages
Packages resolved 277
Deprecated 3
Stale 75
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~647 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_resource_limits ~105

Query quota limits and current usage across configured cloud platforms. Highlights resources approaching or exceeding their limits (default warning threshold: 80%). Use this to proactively catch Lambda concurrency limits, Vercel plan caps, and similar issues before they cause outages.

NameTypeReqDescription
aws_regionstring––
platformsarray–Platforms to check. Omit to check all configured platforms.
warn_thresholdnumber–Usage percentage at which to emit a warning. Default: 80.

No output schema declared.

No examples provided.

diagnose_service_link ~202

Diagnose connectivity issues between a source service and a target resource. Checks Vercel environment variables, AWS Security Group inbound rules on the required port, and external API reachability. Returns a list of diagnostic results with actionable messages.

NameTypeReqDescription
aws_regionstring––
portinteger–TCP port to verify access on. Auto-detected from common resource types when omitted.
s3_originstring–When target is aws-s3, check CORS for this origin (e.g. 'https://my-app.pages.dev').
source_servicestringyesThe origin service that initiates the connection.
target_resourcestringyesThe resource to connect to. Format: '<type>:<identifier>'. Examples: 'aws-rds:my-db', 'aws-lambda:my-function', 'external-api:https://api.example.com'
vercel_projectstring–Vercel project name or ID for env-var checks.

No output schema declared.

No examples provided.

get_correlated_logs ~245

Fetch logs from multiple cloud platforms (AWS CloudWatch + Vercel) for a given time window and optional trace ID, then merge them into a single chronological timeline. Use this to correlate errors across frontend and backend services.

NameTypeReqDescription
aws_log_group_prefixstring–CloudWatch log group prefix to search. Default: /aws/lambda
aws_regionstring–AWS region. Defaults to AWS_REGION env var.
cloudflare_workerstring–Cloudflare Worker script name to tail logs from.
end_timestring–End of time window (ISO-8601 string or Unix epoch in ms). Defaults to now.
gcp_servicestring–GCP Cloud Run service name to filter logs. Omit to pull all project logs.
start_timestringyesStart of time window (ISO-8601 string or Unix epoch in ms). Example: '2024-06-01T10:00:00Z'
trace_idstring–Trace / request ID to filter logs across platforms.
vercel_projectstring–Vercel project name or ID to pull deployment logs from.

No output schema declared.

No examples provided.

list_cloud_topology ~95

Scan all configured cloud platforms (AWS, Vercel, GCP, Cloudflare) and return a unified topology of active services including their endpoints and regions. Run this first to understand the infrastructure landscape.

NameTypeReqDescription
aws_regionstring–AWS region to scan. Defaults to AWS_REGION env var or us-east-1.
platformsarray–Platforms to include. Omit to auto-detect all configured platforms.

No output schema declared.

No examples provided.

Common questions

What is the io.github.lhf552004/cloudpulse MCP server?

io.github.lhf552004/cloudpulse is an MCP server listed in the public MCP registry as io.github.lhf552004/cloudpulse. Cross-cloud observability for AI agents. Covers AWS, GCP, Vercel, and Cloudflare. This page covers its npm package (cloudpulse-mcp).

Is the io.github.lhf552004/cloudpulse MCP server safe to use?

io.github.lhf552004/cloudpulse scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.lhf552004/cloudpulse MCP server expose?

io.github.lhf552004/cloudpulse exposes 4 tools: list_cloud_topology, get_correlated_logs, diagnose_service_link, check_resource_limits. Their descriptions and schemas cost roughly 647 tokens of context every time the server is loaded.

Is the io.github.lhf552004/cloudpulse MCP server still maintained?

io.github.lhf552004/cloudpulse is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.lhf552004/cloudpulse MCP server under?

io.github.lhf552004/cloudpulse declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.