# Jungle Cleaner (remote · junglecleaner.com)

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

- Trust score: 69/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `junglecleaner.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-junglecleaner-mcp/api-mcp.md), [page](https://verifymcp.io/servers/com-junglecleaner-mcp/api-mcp)

## Channel facts

- Endpoint: `https://junglecleaner.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 863 tokens (~123/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-junglecleaner-mcp https://junglecleaner.com/api/mcp
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-junglecleaner-mcp --url https://junglecleaner.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-junglecleaner-mcp:
    url: "https://junglecleaner.com/api/mcp"
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 69, +1)

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

### 2026-07-31 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 67, +1)

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

### 2026-07-28 (score 66, +1)

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

### 2026-07-27 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (7)

### `connect_aws` (~125 tokens)

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.

Input parameters:

- `name` (string): A friendly name for the AWS account (e.g. "Production", "Staging", "My Company"). Optional but recommended.
- `stage` (string): The 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.

### `list_accounts` (~21 tokens)

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

### `scan` (~179 tokens)

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.

Input parameters:

- `account` (string): The name (e.g. "Production") or AWS account ID (e.g. "123456789012") to scan. Defaults to the most recently connected account if omitted.
- `force` (boolean): Skip 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…
- `progressToken` (string|number): MCP progress token for streaming live scan updates. Always pass this when available so progress notifications are sent during long-running scans.

### `get_results` (~66 tokens)

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

Input parameters:

- `account` (string): The name (e.g. "Production") or AWS account ID to retrieve results for. Defaults to the most recently connected account if omitted.

### `verify_savings` (~122 tokens)

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.

Input parameters:

- `account` (string): The name (e.g. "Production") or AWS account ID to check. Defaults to the most recently connected account if omitted.
- `progressToken` (string|number): MCP progress token for streaming live progress updates while findings are being checked.

### `clean` (~187 tokens)

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.

Input parameters:

- `account` (string): The name (e.g. "Production") or AWS account ID to clean. Defaults to the most recently connected account if omitted.
- `category` (string): Which 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_id` (string): Target a single finding by ID. Omit to include all findings of the given category.

### `check_usage` (~163 tokens)

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.

Input parameters:

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-junglecleaner-mcp/api-mcp#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 69
- 2026-08-01: 68
- 2026-07-31: 68
- 2026-07-30: 67
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 65
- 2026-07-26: 65

## Links

- Remote endpoint: https://junglecleaner.com/api/mcp
- Website: https://junglecleaner.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-junglecleaner-mcp/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-junglecleaner-mcp/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-junglecleaner-mcp/api-mcp