# io.github.alexgaoth/escalate-anything (pypi · escalate-anything)

Get the upper hand on any big US company: contacts, playbooks and escalation paths.

- Trust score: 85/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `escalate-anything`: 85/100 (this document), [markdown](https://verifymcp.io/servers/alexgaoth-escalate-anything/escalate-anything.md), [page](https://verifymcp.io/servers/alexgaoth-escalate-anything/escalate-anything)

## Channel facts

- Registry: `pypi`
- Package: `escalate-anything`
- Version: `0.2.2`
- 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-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 32 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 84/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to alexgaoth/escalate-anything).
  - License check failed: the license (MIT AND CC-BY-4.0) isn't a recognized OSI-approved license.
  - Actively maintained (last published 21 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 1555 tokens (~74/item across 21 items; 19 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.alexgaoth/escalate-anything MCP server?

io.github.alexgaoth/escalate-anything runs locally as a PyPI package, launched with uvx escalate-anything. 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 alexgaoth-escalate-anything -- uvx escalate-anything
```

### Cursor

```json
{
  "mcpServers": {
    "alexgaoth-escalate-anything": {
      "command": "uvx",
      "args": [
        "escalate-anything"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "alexgaoth-escalate-anything": {
      "command": "uvx",
      "args": [
        "escalate-anything"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add alexgaoth-escalate-anything -- uvx escalate-anything
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "alexgaoth-escalate-anything": {
      "type": "local",
      "command": [
        "uvx",
        "escalate-anything"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add alexgaoth-escalate-anything --command uvx --arg escalate-anything
```

### Hermes

```yaml
mcp_servers:
  alexgaoth-escalate-anything:
    command: "uvx"
    args: ["escalate-anything"]
```

### Netclaw

```json
{
  "McpServers": {
    "alexgaoth-escalate-anything": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "escalate-anything"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add alexgaoth-escalate-anything -t stdio -c uvx -a escalate-anything
```

### Other

```json
{
  "mcpServers": {
    "alexgaoth-escalate-anything": {
      "command": "uvx",
      "args": [
        "escalate-anything"
      ]
    }
  }
}
```

## 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-05 (score 85, +1)

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

### 2026-11-03 (score 84, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-01 (score 68, −14)

- [security regression] Malware scan: pass → unverified

### 2026-10-30 (score 82, +1)

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

### 2026-10-29 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-28 (score 66, −14)

- [security regression] Malware scan: pass → unverified

### 2026-10-27 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-26 (score 65, −15)

- [security regression] Malware scan: pass → unverified

## MCP tools (19)

### `find_company` (~58 tokens)

Find a company

Find companies by name, brand or alias (e.g. 'xfinity', 'united', 'chase').
With an empty query, list every company, optionally only one sector.

Input parameters:

- `query` (string)
- `sector`

### `get_company` (~48 tokens)

Get company details

Full record for one company: every channel, facts, tips, known blockers and playbooks,
plus a credibility summary (grade, source tiers, last verified date).

Input parameters:

- `company` (string, required)

### `list_issues` (~30 tokens)

List issue types

Issue ids that a playbook can be built for, optionally only one sector.

Input parameters:

- `sector`

### `get_playbook` (~84 tokens)

Get the playbook for an issue

Steps, channels (deep links, phones), evidence, deadlines, verified facts, applicable rules
and the escalation ladder for one company and issue. Pass the person's two-letter state code
to resolve state agencies. Rule points are limited to this issue; get_rules gives full text.

Input parameters:

- `company` (string, required)
- `issue` (string, required)
- `state`

### `get_escalation` (~40 tokens)

Get the next escalation step

The escalation ladder for a company, lowest rung first, with concrete contacts for each rung.

Input parameters:

- `company` (string, required)
- `state`

### `find_regulators` (~33 tokens)

Find regulators

Federal regulators and state agencies that take complaints for a sector.

Input parameters:

- `sector` (string, required)
- `state`

### `get_rules` (~58 tokens)

Get consumer rules

Laws and regulations for a sector and issue. Rules that were vacated, stayed or withdrawn
are listed separately under not_in_force and must not be cited as current law.

Input parameters:

- `issue`
- `sector`
- `state`

### `get_context` (~64 tokens)

Get how a company handles complaints

How a company handles complaints in practice: a cited dossier (what works, traps, complaint
statistics, scams that use its name), the guide for its sector, and the general scam guide.
Read it before contacting the company.

Input parameters:

- `company`
- `sector`

### `scam_check` (~82 tokens)

Check a message for scam red flags

Check a message, email, text or call script for common scam red flags: gift cards, crypto,
remote access, one-time codes, pay-to-get-refund, pressure, package fees, unpaid tolls and
account verification links. get_context(company) lists what that company says it never asks for.

Input parameters:

- `company`
- `text` (string, required)

### `case_open` (~84 tokens)

Open a case

Start a case in the local log. account_hint is at most the last 4 digits. Never store
passwords, full card numbers or SSNs.

Input parameters:

- `account_hint`
- `amount`
- `company` (string, required)
- `desired_outcome`
- `issue` (string, required)
- `state`
- `summary` (string, required)

### `case_log` (~149 tokens)

Log a contact on a case

Record what happened on a case. kind: contact, sent, response, promise, reference, document,
escalation or note. rung: the escalation rung this contact used (frontline, retention,
written_complaint, executive, regulator, state_agency, payment_dispute, ...). Dates are YYYY-MM-DD.
Set follow_up_on to the date to check back if nothing happens.

Input parameters:

- `case_id` (integer, required)
- `channel`
- `follow_up_on`
- `kind` (string, required)
- `occurred_on`
- `promised`
- `reference`
- `rep_name`
- `rung`
- `text` (string, required)

### `case_get` (~41 tokens)

Get a case

A case with its timeline, promises, reference numbers, pending follow-up and the next
escalation rung to try.

Input parameters:

- `case_id` (integer, required)

### `case_list` (~30 tokens)

List cases

Cases in the local log. status: open, closed, or null for all.

Input parameters:

- `status`

### `case_close` (~70 tokens)

Close a case

Close a case. outcome: resolved, partial, failed or abandoned. what_worked: the channel or
argument that worked, so later cases can reuse it.

Input parameters:

- `amount_recovered`
- `case_id` (integer, required)
- `outcome` (string, required)
- `what_worked`

### `followups_due` (~31 tokens)

List follow-ups due

Open cases whose follow-up date has come and that had no activity since.

Input parameters:

- `on_or_before`

### `draft_brief` (~62 tokens)

Draft a complaint brief

Everything needed to write the next message on a case: recipient channel, timeline,
references, promises, verified facts and rules with sources, and tone rules. rung defaults to
the next escalation rung.

Input parameters:

- `case_id` (integer, required)
- `rung`

### `bill_record` (~80 tokens)

Record a bill

Record one bill (total amount due for the period ending period_end, YYYY-MM-DD).
promo_end is the date a promotional price ends, if the bill shows it.

Input parameters:

- `amount` (number, required)
- `company` (string, required)
- `note`
- `period_end` (string, required)
- `plan`
- `promo_end`

### `bill_check` (~52 tokens)

Check a bill for increases

Find bills that went up versus the median of the previous three, and promotions that end
soon. Each finding suggests an issue id for get_playbook.

Input parameters:

- `company`
- `threshold_pct` (number)

### `report_registry_problem` (~74 tokens)

Report a wrong contact or fact

Record a wrong or dead URL, phone number or fact in the registry, so a person can fix the
data. entity: company, regulator, state or rule id. location: e.g. 'channels.refund-form'.

Input parameters:

- `entity` (string, required)
- `location`
- `problem` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/alexgaoth-escalate-anything/escalate-anything#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 68
- 2026-11-01: 68
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 81
- 2026-10-28: 66
- 2026-10-27: 80
- 2026-10-26: 65
- 2026-10-25: 80
- 2026-10-24: 79
- 2026-10-23: 79
- 2026-10-22: 78
- 2026-10-21: 78
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 76
- 2026-10-17: 76
- 2026-10-16: 47
- 2026-10-15: 32
- 2026-10-14: 47

## Common questions

### What is the io.github.alexgaoth/escalate-anything MCP server?

io.github.alexgaoth/escalate-anything is an MCP server listed in the public MCP registry as io.github.alexgaoth/escalate-anything. Get the upper hand on any big US company: contacts, playbooks and escalation paths. This page covers its PyPI package (escalate-anything).

### Is the io.github.alexgaoth/escalate-anything MCP server safe to use?

io.github.alexgaoth/escalate-anything scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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.alexgaoth/escalate-anything MCP server expose?

io.github.alexgaoth/escalate-anything exposes 19 tools: find_company, get_company, list_issues, get_playbook, get_escalation, and 14 more. Their descriptions and schemas cost roughly 1,170 tokens of context every time the server is loaded.

### Is the io.github.alexgaoth/escalate-anything MCP server still maintained?

io.github.alexgaoth/escalate-anything is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.alexgaoth/escalate-anything MCP server under?

io.github.alexgaoth/escalate-anything declares the MIT AND CC-BY-4.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

### What did VerifyMCP test on the io.github.alexgaoth/escalate-anything MCP server?

VerifyMCP ran 16 checks on io.github.alexgaoth/escalate-anything, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/escalate-anything/
- Socket report: https://socket.dev/pypi/package/escalate-anything
- Repository: https://github.com/alexgaoth/escalate-anything
- Changelog RSS feed: https://verifymcp.io/servers/alexgaoth-escalate-anything/escalate-anything.xml
- Changelog JSON feed: https://verifymcp.io/servers/alexgaoth-escalate-anything/escalate-anything/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/alexgaoth-escalate-anything/escalate-anything.json
- HTML version of this page: https://verifymcp.io/servers/alexgaoth-escalate-anything/escalate-anything