# Rotten America Petitions (npm · @rottenamerica/petitions-mcp)

Find, draft and start verified petitions from a chat; follow signatures and post updates.

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

## Components

- remote · `rottenamerica.com`: 38/100, [markdown](https://verifymcp.io/servers/com-rottenamerica-petitions/rottenamerica.md), [page](https://verifymcp.io/servers/com-rottenamerica-petitions/rottenamerica)
- npm · `@rottenamerica/petitions-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-rottenamerica-petitions/rottenamerica-petitions-mcp.md), [page](https://verifymcp.io/servers/com-rottenamerica-petitions/rottenamerica-petitions-mcp)

## Channel facts

- Registry: `npm`
- Package: `@rottenamerica/petitions-mcp`
- Version: `0.4.0`
- Transport: `stdio`

## Trust breakdown

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

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 13 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 430 tokens (~143/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Rotten America Petitions MCP server?

Rotten America Petitions runs locally as an npm package, launched with npx -y @rottenamerica/petitions-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-rottenamerica-petitions -- npx -y @rottenamerica/petitions-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-rottenamerica-petitions": {
      "command": "npx",
      "args": [
        "-y",
        "@rottenamerica/petitions-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-rottenamerica-petitions": {
      "command": "npx",
      "args": [
        "-y",
        "@rottenamerica/petitions-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-rottenamerica-petitions -- npx -y @rottenamerica/petitions-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-rottenamerica-petitions": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@rottenamerica/petitions-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-rottenamerica-petitions --command npx --arg -y --arg @rottenamerica/petitions-mcp
```

### Hermes

```yaml
mcp_servers:
  com-rottenamerica-petitions:
    command: "npx"
    args: ["-y", "@rottenamerica/petitions-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-rottenamerica-petitions": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@rottenamerica/petitions-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-rottenamerica-petitions -t stdio -c npx -a -y @rottenamerica/petitions-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-rottenamerica-petitions": {
      "command": "npx",
      "args": [
        "-y",
        "@rottenamerica/petitions-mcp"
      ]
    }
  }
}
```

## 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-11-21 (score 71, +1)

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

### 2026-11-19 (score 70, +1)

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

### 2026-11-17 (score 69, +1)

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

### 2026-11-15 (score 68, +1)

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

### 2026-11-13 (score 67, +1)

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

### 2026-11-11 (score 66, +1)

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

### 2026-11-09 (score 65, +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-11-08 (score 64, +20)

- [security improvement] CVE-2026-111769 no longer affects this package
- [security improvement] GHSA-f897-62hf-6gxq no longer affects this package
- [security improvement] CVE-2023-54404 no longer affects this package
- [security improvement] CVE-2026-111767 no longer affects this package
- [security improvement] CVE-2026-104850 no longer affects this package
- [security improvement] CVE-2026-111768 no longer affects this package
- [security improvement] CVE-2026-111771 no longer affects this package
- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: fail → pass
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 67% → 80%
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.2.2 → 0.4.0

## MCP tools (3)

### `find_petitions` (~85 tokens)

Find live petitions

Searches live Rotten America petitions by words in the title or ask. Use it before starting a new petition: if one already asks for the same thing, suggest signing and sharing it instead of splitting support.

Input parameters:

- `limit` (integer)
- `query` (string): Words to look for, e.g. 'PFAS' or 'Tampa'. Leave out for the newest.

### `get_petition` (~98 tokens)

Read one petition

One live petition: its exact wording, who it goes to, its verified signature count and goal, the links to sign and to check the count, and its ledger: whether every signature checks out, whether the wording is sealed, and which Bitcoin blocks hold its signatures. Quote the block numbers when the user asks for proof.

Input parameters:

- `slug` (string, required): The petition's slug, from find_petitions, my_petitions or start_petition.

### `prove_signature` (~116 tokens)

Prove one signature is counted

Proves that one signature is on a petition's public ledger and in Bitcoin, from the signature hash on the signer's receipt (64 hex characters). Walks the Merkle path itself, so the answer does not rest on Rotten America's word. Only the signer has their receipt hash; never ask for or guess anyone's personal details.

Input parameters:

- `receipt_hash` (string, required): The signature hash printed on the signer's receipt.
- `slug` (string, required): The petition's slug, from find_petitions, my_petitions or start_petition.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-rottenamerica-petitions/rottenamerica-petitions-mcp#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 70
- 2026-11-19: 70
- 2026-11-18: 69
- 2026-11-17: 69
- 2026-11-16: 68
- 2026-11-15: 68
- 2026-11-14: 67
- 2026-11-13: 67
- 2026-11-12: 66
- 2026-11-11: 66
- 2026-11-10: 65
- 2026-11-09: 65
- 2026-11-08: 64
- 2026-11-07: 44

## Common questions

### What is the Rotten America Petitions MCP server?

Rotten America Petitions is an MCP server listed in the public MCP registry as com.rottenamerica/petitions. Find, draft and start verified petitions from a chat; follow signatures and post updates. This page covers its npm package (@rottenamerica/petitions-mcp).

### Is the Rotten America Petitions MCP server safe to use?

Rotten America Petitions scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 Rotten America Petitions MCP server expose?

Rotten America Petitions exposes 3 tools: find_petitions, get_petition, prove_signature. Their descriptions and schemas cost roughly 299 tokens of context every time the server is loaded.

### Is the Rotten America Petitions MCP server still maintained?

Rotten America Petitions is still listed as active in the MCP registry. We last reached this channel on 21 November 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 Rotten America Petitions MCP server under?

Rotten America Petitions declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Rotten America Petitions MCP server?

VerifyMCP ran 15 checks on Rotten America Petitions, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Rotten America Petitions: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@rottenamerica/petitions-mcp
- Socket report: https://socket.dev/npm/package/@rottenamerica/petitions-mcp
- Website: https://rottenamerica.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-rottenamerica-petitions/rottenamerica-petitions-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-rottenamerica-petitions/rottenamerica-petitions-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-rottenamerica-petitions/rottenamerica-petitions-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-rottenamerica-petitions/rottenamerica-petitions-mcp
