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.

Jungle Cleaner

REMOTE · JUNGLECLEANER.COM · SCANNED SEP 20

Lowers your AWS bill by helping you clean up and optimize your setup

0 this week 39 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security97
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

Install

How do I install the Jungle Cleaner MCP server?

Jungle Cleaner is a hosted endpoint at https://junglecleaner.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · junglecleaner.com

# add to Claude Code
claude mcp add --transport http com-junglecleaner-mcp 'https://junglecleaner.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-junglecleaner-mcp": {
      "url": "https://junglecleaner.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-junglecleaner-mcp": {
      "type": "http",
      "url": "https://junglecleaner.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-junglecleaner-mcp]
url = "https://junglecleaner.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-junglecleaner-mcp": {
      "type": "remote",
      "url": "https://junglecleaner.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-junglecleaner-mcp --url 'https://junglecleaner.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-junglecleaner-mcp:
    url: "https://junglecleaner.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-junglecleaner-mcp": {
      "Transport": "http",
      "Url": "https://junglecleaner.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-junglecleaner-mcp -t streamable-http -u 'https://junglecleaner.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "com-junglecleaner-mcp": {
      "type": "http",
      "url": "https://junglecleaner.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 29 Aug 26 −42
    • Endpoint reachability: reachable → behind authorisation security
    • Stability: pass → unverified security
    • Tool safety: pass → unverified security
    • Transport: pass → unverified security
    • Authorization: unverified → pass security
    • First check of Authorization: pass security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

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

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 · Probed https://junglecleaner.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=junglecleaner.com CN=YR2,O=Let's Encrypt,C=US 7 Aug 2026 5 Nov 2026 RSA 2048 SHA256-RSA 6c103febb751bc27384809047fae9d9fb44
SANs: junglecleaner.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of junglecleaner.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
junglecleaner.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer resource_metadata="https://junglecleaner.com/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://junglecleaner.com/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=63072000
www-authenticate Bearer resource_metadata="https://junglecleaner.com/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://junglecleaner.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://junglecleaner.com/api/mcp
Authorisation server https://junglecleaner.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://junglecleaner.com/api/mcp Auth required 401
http (plaintext) http://junglecleaner.com/api/mcp HTTPS enforced 308 https://junglecleaner.com/api/mcp
MCP tools · 7 exposed · ~863 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_usage ~163

Check whether a specific resource is currently idle or in active use. Uses live CloudWatch metrics and API state checks. Returns a verdict (confirmed_inactive / possibly_active / unknown) with supporting evidence.

NameTypeReqDescription
accountstringThe AWS account name or ID. Defaults to the most recently connected account.
finding_typestringyesThe finding type string from a scan result (e.g. "lambda-unused", "rds-idle", "ebs-unattached").
regionstringThe AWS region (e.g. "us-east-1"). Required if the resource is region-specific.
resource_idstringyesThe resource ARN or ID to check (e.g. an EBS volume ID, Lambda ARN, RDS instance ID).

No output schema declared.

No examples provided.

clean ~187

Get a step-by-step cleanup guide for your latest scan findings. Automatically checks whether idle resources are still in use before recommending deletion. Detects IaC tools (Terraform, CloudFormation, OpenTofu, Pulumi) and shows IaC-first remediation guidance. Returns a ready-to-act guidance prompt — you follow the steps, Jungle Cleaner verifies the savings.

NameTypeReqDescription
accountstringThe name (e.g. "Production") or AWS account ID to clean. Defaults to the most recently connected account if omitted.
categorystringWhich category of findings to include. "cleanup" (default) covers idle/unused resources safe to delete. "upgrade" covers config changes that reduce cost. "recommendation" covers architectural changes…
finding_idstringTarget a single finding by ID. Omit to include all findings of the given category.

No output schema declared.

No examples provided.

connect_aws ~125

Connect an AWS account so it can be scanned for unused resources and wasted spend. Returns a guided setup page. If you are not yet signed in to Jungle Cleaner, this will return a sign-in URL first.

NameTypeReqDescription
namestringA friendly name for the AWS account (e.g. "Production", "Staging", "My Company"). Optional but recommended.
stagestringThe environment stage of this AWS account. Used to tailor recommendations — e.g. shorter log retention for development/testing, longer for production. Defaults to "production" if not set.

No output schema declared.

No examples provided.

get_results ~66

Retrieve the latest scan results without triggering a new scan. Useful if you want to re-read results from a previous run.

NameTypeReqDescription
accountstringThe name (e.g. "Production") or AWS account ID to retrieve results for. Defaults to the most recently connected account if omitted.

No output schema declared.

No examples provided.

list_accounts ~21

List all AWS accounts connected to Jungle Cleaner for the current user.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scan ~179

Scan your connected AWS account for unused resources and wasted spend. Returns findings with estimated monthly cost in plain English. Pass progressToken to receive live progress updates during the scan. If multiple accounts are connected, pass the account name or account ID to target a specific one.

NameTypeReqDescription
accountstringThe name (e.g. "Production") or AWS account ID (e.g. "123456789012") to scan. Defaults to the most recently connected account if omitted.
forcebooleanSkip the Cost Explorer spend gate and run all scanner modules regardless of whether the service has recent spend. Useful for new accounts or when testing resources that were just created and haven't…
progressTokenstring|numberMCP progress token for streaming live scan updates. Always pass this when available so progress notifications are sent during long-running scans.

No output schema declared.

No examples provided.

verify_savings ~122

Check which findings from the latest scan have been remediated — resources deleted, configs changed, policies set. Confirms each remediation via the AWS API and records the estimated monthly saving so your total captured savings accumulate over time. Returns newly confirmed remediations and your running captured savings total.

NameTypeReqDescription
accountstringThe name (e.g. "Production") or AWS account ID to check. Defaults to the most recently connected account if omitted.
progressTokenstring|numberMCP progress token for streaming live progress updates while findings are being checked.

No output schema declared.

No examples provided.

Common questions

What is the Jungle Cleaner MCP server?

Jungle Cleaner is an MCP server listed in the public MCP registry as com.junglecleaner/mcp. Lowers your AWS bill by helping you clean up and optimize your setup. This page covers its hosted endpoint (https://junglecleaner.com/api/mcp).

Is the Jungle Cleaner MCP server safe to use?

Jungle Cleaner scores 39 out of 100 on VerifyMCP. 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 Jungle Cleaner MCP server expose?

Jungle Cleaner exposes 7 tools: connect_aws, list_accounts, scan, get_results, verify_savings, and 2 more. Their descriptions and schemas cost roughly 863 tokens of context every time the server is loaded.

Does the Jungle Cleaner MCP server require authentication?

Yes. Jungle Cleaner asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Jungle Cleaner MCP server still maintained?

Jungle Cleaner 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.