Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/galadriel-tech-solutions/cloudpulse-mcp/cloudpulsegit clone --depth 1 https://github.com/Galadriel-Tech-Solutions/cloudpulse-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/galadriel-tech-solutions/cloudpulse-mcp/cloudpulse)<a href="https://agentmods.dev/mcp/galadriel-tech-solutions/cloudpulse-mcp/cloudpulse"><img src="https://agentmods.dev/badge/mcp/galadriel-tech-solutions/cloudpulse-mcp/cloudpulse.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cloudpulse scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"cloudpulse": {
"command": "npx",
"args": [
"-y",
"cloudpulse-mcp"
],
"env": {
"AWS_ACCESS_KEY_ID": "",
"AWS_SECRET_ACCESS_KEY": "",
"AWS_REGION": "",
"VERCEL_TOKEN": "",
"GOOGLE_APPLICATION_CREDENTIALS": "",
"GOOGLE_CLOUD_PROJECT": "",
"CLOUDFLARE_API_TOKEN": "",
"CLOUDFLARE_ACCOUNT_ID": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 19 lines scan A 468e6178ab99
cloudpulse is an MCP server published in the GitHub repository Galadriel-Tech-Solutions/cloudpulse-mcp (1 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
cloud-regions
Cloud region data for AWS, Azure, GCP, OCI & more. Query by location, compliance, GPU. Runs locally from the mcp-server-cloud-regions npm package.
cloudwatch
MCP server "cloudwatch" as configured in awslabs/mcp. Runs locally from the awslabs.cloudwatch-mcp-server@latest Python package. Needs 1 environment variable to run.
cloudwatch-appsignals
MCP server "cloudwatch-appsignals" as configured in awslabs/mcp. Runs locally from the awslabs.cloudwatch-applicationsignals-mcp-server@latest Python package. Needs 1 environment variable to run.
cloudflare-api
Cloudflare's hosted MCP servers for Workers, KV, R2, D1 and account resources. Remote server at mcp.cloudflare.com.
cloudflare-builds
MCP server "cloudflare-builds", hosted remotely at builds.mcp.cloudflare.com, as configured in cloudflare/skills.
cloudflare-observability
MCP server "cloudflare-observability", hosted remotely at observability.mcp.cloudflare.com, as configured in cloudflare/skills.