io.github.alexgaoth/escalate-anything
PYPI · ESCALATE-ANYTHING
Get the upper hand on any big US company: contacts, playbooks and escalation paths.
Available components
Last scanned (18 hours ago)
Scores higher than 88% of PyPI servers
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to alexgaoth/escalate-anything). View diagnostics → Pass
- License check failed: the license (MIT AND CC-BY-4.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 21 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1555 tokens (~74/item across 21 items; 19 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +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.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +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.
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
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 5 Nov 2026 · Analysed pypi/escalate-anything@0.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | alexgaoth/escalate-anything |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/alexgaoth/escalate-anything/.github/workflows/release.yml@refs/tags/v0.2.2 |
| Rekor log index | 3258014974 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:3007d293a30c4fd51be764c0c5225eff5ed31a1279d5a4c66ad1e145ec1dc107 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
bill_check Check a bill for increases ~52
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | – | – | – |
| threshold_pct | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
bill_record Record a bill ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| company | string | yes | – |
| note | – | – | – |
| period_end | string | yes | – |
| plan | – | – | – |
| promo_end | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
case_close Close a case ~70
Close a case. outcome: resolved, partial, failed or abandoned. what_worked: the channel or argument that worked, so later cases can reuse it.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_recovered | – | – | – |
| case_id | integer | yes | – |
| outcome | string | yes | – |
| what_worked | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
case_get Get a case ~41
A case with its timeline, promises, reference numbers, pending follow-up and the next escalation rung to try.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
case_list List cases ~30
Cases in the local log. status: open, closed, or null for all.
| Name | Type | Req | Description |
|---|---|---|---|
| status | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
case_log Log a contact on a case ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | integer | yes | – |
| channel | – | – | – |
| follow_up_on | – | – | – |
| kind | string | yes | – |
| occurred_on | – | – | – |
| promised | – | – | – |
| reference | – | – | – |
| rep_name | – | – | – |
| rung | – | – | – |
| text | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
case_open Open a case ~84
Start a case in the local log. account_hint is at most the last 4 digits. Never store passwords, full card numbers or SSNs.
| Name | Type | Req | Description |
|---|---|---|---|
| account_hint | – | – | – |
| amount | – | – | – |
| company | string | yes | – |
| desired_outcome | – | – | – |
| issue | string | yes | – |
| state | – | – | – |
| summary | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
draft_brief Draft a complaint brief ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | integer | yes | – |
| rung | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
find_company Find a company ~58
Find companies by name, brand or alias (e.g. 'xfinity', 'united', 'chase'). With an empty query, list every company, optionally only one sector.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | – |
| sector | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
find_regulators Find regulators ~33
Federal regulators and state agencies that take complaints for a sector.
| Name | Type | Req | Description |
|---|---|---|---|
| sector | string | yes | – |
| state | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
followups_due List follow-ups due ~31
Open cases whose follow-up date has come and that had no activity since.
| Name | Type | Req | Description |
|---|---|---|---|
| on_or_before | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_company Get company details ~48
Full record for one company: every channel, facts, tips, known blockers and playbooks, plus a credibility summary (grade, source tiers, last verified date).
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_context Get how a company handles complaints ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | – | – | – |
| sector | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_escalation Get the next escalation step ~40
The escalation ladder for a company, lowest rung first, with concrete contacts for each rung.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| state | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_playbook Get the playbook for an issue ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| issue | string | yes | – |
| state | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_rules Get consumer rules ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| issue | – | – | – |
| sector | – | – | – |
| state | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_issues List issue types ~30
Issue ids that a playbook can be built for, optionally only one sector.
| Name | Type | Req | Description |
|---|---|---|---|
| sector | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
report_registry_problem Report a wrong contact or fact ~74
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | – |
| location | – | – | – |
| problem | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
scam_check Check a message for scam red flags ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | – | – | – |
| text | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.
pypi · escalate-anything
claude mcp add alexgaoth-escalate-anything -- uvx escalate-anything
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.