# FeeFighter (remote · fee-fighter.magicteams.ai)

Audit junk fees, project annual costs and draft dispute letters. Free.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `fee-fighter.magicteams.ai`: 77/100 (this document), [markdown](https://verifymcp.io/servers/everyai-com-fee-fighter/fee-fighter.md), [page](https://verifymcp.io/servers/everyai-com-fee-fighter/fee-fighter)

## Channel facts

- Endpoint: `https://fee-fighter.magicteams.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-10-23.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 771 tokens (~192/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 48/100
  - Stability check failed: schema churn in the 19 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions.
- **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.
  - 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 FeeFighter MCP server?

FeeFighter is a hosted endpoint at https://fee-fighter.magicteams.ai/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.

### Claude

```bash
claude mcp add --transport http everyai-com-fee-fighter 'https://fee-fighter.magicteams.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "everyai-com-fee-fighter": {
      "url": "https://fee-fighter.magicteams.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "everyai-com-fee-fighter": {
      "type": "http",
      "url": "https://fee-fighter.magicteams.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.everyai-com-fee-fighter]
url = "https://fee-fighter.magicteams.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "everyai-com-fee-fighter": {
      "type": "remote",
      "url": "https://fee-fighter.magicteams.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add everyai-com-fee-fighter --url 'https://fee-fighter.magicteams.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  everyai-com-fee-fighter:
    url: "https://fee-fighter.magicteams.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "everyai-com-fee-fighter": {
      "Transport": "http",
      "Url": "https://fee-fighter.magicteams.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add everyai-com-fee-fighter -t streamable-http -u 'https://fee-fighter.magicteams.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "everyai-com-fee-fighter": {
      "type": "http",
      "url": "https://fee-fighter.magicteams.ai/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-10-22 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 41 to 44.

### 2026-10-20 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 34 to 38.

### 2026-10-18 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 28 to 31.

### 2026-10-15 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 18 to 21.

### 2026-10-13 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 11 to 14.

### 2026-10-12 (score 72, +1)

- [security] Tool “annual_cost” rewrote its description, which is the text the model reads

### 2026-10-10 (score 71, −1)

- [security regression] Stability: 0.07 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security] Tool “annual_cost” rewrote its description, which is the text the model reads
- [security] Tool “audit_fees” rewrote its description, which is the text the model reads
- [security] Tool “benchmark_fees” rewrote its description, which is the text the model reads
- [security] Tool “dispute_letter” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional regression] “annual_cost” changed the type of “years”: number → integer
- [functional improvement] Tool coverage: 92% → 100%
- [functional] First check of Tool coverage: 100
- [functional] Schema quality: good → excellent
- [cosmetic] “annual_cost” reworded the description of “fees”
- [cosmetic] “annual_cost” reworded the description of “years”
- [cosmetic] “audit_fees” reworded the description of “fees”
- [cosmetic] “benchmark_fees” reworded the description of “category”
- [cosmetic] “dispute_letter” reworded the description of “account_reference”
- [cosmetic] “dispute_letter” reworded the description of “amount”
- [cosmetic] “dispute_letter” reworded the description of “company”
- [cosmetic] “dispute_letter” reworded the description of “date_charged”
- [cosmetic] “dispute_letter” reworded the description of “fee_name”
- [cosmetic] “dispute_letter” reworded the description of “reason”
- [cosmetic] “dispute_letter” reworded the description of “requested_action”
- [cosmetic] “dispute_letter” reworded the description of “your_name”

### 2026-10-06 (score 72, +1)

- [functional improvement] Stability: unverified → 0.07

## MCP tools (4)

### `audit_fees` (~110 tokens)

Audit fees

Audit a list of fees: annualize each one (monthly x12), total the yearly cost and monthly average, and flag charges above the typical US range for their category, duplicate names and one-time fees of $30+ worth disputing. Use when the user lists fees to review. For a multi-year projection use annual_cost; for typical ranges alone use benchmark_fees.

Input parameters:

- `fees` (array, required): Non-empty list of fees to audit, each {name, amount, frequency, category?}

Output parameters:

- `currency` (string): Currency of all amounts; always USD
- `fees` (array): One audited row per input fee, in input order
- `flagged_count` (integer): Number of fees with at least one flag
- `note` (string): Plain-language summary of the audit result; lists any unknown category keys that were ignored
- `total_annual` (number): Sum of all annualized fees, USD
- `total_monthly_average` (number): total_annual divided by 12, USD

### `annual_cost` (~143 tokens)

Annual cost

Project the cumulative cost of a fee list over 1-30 years by straight multiplication of each recurring fee's annualized amount, with one-time fees counted once (no compounding or inflation), with a per-fee breakdown. Use for 'what will these cost me over N years'. It does not flag fees: use audit_fees to find problem charges, benchmark_fees for typical ranges.

Input parameters:

- `fees` (array, required): Non-empty list of fees to project, each {name, amount, frequency, category?}; category is accepted but not used here
- `years` (integer): Number of years to project, integer 1-30; default 1

Output parameters:

- `cumulative_total` (number): Sum of all per-fee cumulative amounts, USD
- `note` (string): Method note: recurring fees multiplied by years, one-time fees counted once, no compounding
- `per_fee` (array): Per-fee projection, in input order
- `years` (integer): Number of years projected (1-30)

### `benchmark_fees` (~178 tokens)

Benchmark fees

Look up typical US consumer fee ranges (min/max per charge, USD) for one category such as bank_overdraft, or the full 14-category table when category is omitted. Use to answer 'is this fee normal?' questions. To check a user's own list of fees against these ranges, use audit_fees.

Input parameters:

- `category` (string): Category key (case-insensitive; spaces/hyphens become underscores), one of: bank_overdraft, bank_monthly_maintenance, atm_out_of_network, late_payment, gym_membership_monthly, streaming_monthly, airl…

Output parameters:

- `basis` (string): Basis label for the range (typical US range - verify current pricing)
- `categories` (array): Every benchmark row (full-table response only)
- `category` (string): Benchmark category key, e.g. bank_overdraft
- `count` (integer): Number of categories (full-table response only)
- `currency` (string): Currency of all ranges; always USD
- `disclaimer` (string): Informational-only disclaimer
- `label` (string): Human-readable fee label, e.g. 'Out-of-network ATM fee'
- `source_note` (string): Where the ranges come from and how to read them
- `typical_max` (number): High end of the typical US range per charge, USD
- `typical_min` (number): Low end of the typical US range per charge, USD

### `dispute_letter` (~277 tokens)

Dispute letter

Draft (text only; nothing is sent) a firm, polite letter asking a company to reverse or refund one specific fee, with grounds, a 14-day written-response request, an escalation path and sending tips. Use once the user has picked a fee to contest. To find which fees are worth disputing first, use audit_fees.

Input parameters:

- `account_reference` (string): Optional account or reference number; prefer a masked form like '****1234'
- `amount` (number, required): Fee amount in USD, greater than 0, e.g. 38
- `company` (string, required): Company or bank that charged the fee, e.g. 'First National Bank'
- `date_charged` (string): Optional date the fee was charged, free text, e.g. 2026-09-14
- `fee_name` (string, required): Name of the fee being disputed, e.g. 'Overdraft fee'
- `reason` (string): Optional grounds for the dispute; default cites an undisclosed/unexpected charge and asks for a courtesy reversal
- `requested_action` (string): What to ask the company to do, e.g. 'waive' or 'refund'; default 'reverse or refund'
- `your_name` (string, required): Account holder's full name, used in From and to sign the letter

Output parameters:

- `disclaimer` (string): Not legal or financial advice disclaimer
- `letter` (string): Full letter text with To/From/Subject header and signature
- `sending_tips` (array): Practical tips for sending, following up and escalating
- `subject` (string): Subject line, e.g. Request to reverse or refund the $38.00 fee

## Diagnostics

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

## Score history

- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 75
- 2026-10-18: 75
- 2026-10-17: 74
- 2026-10-16: 74
- 2026-10-15: 74
- 2026-10-14: 73
- 2026-10-13: 73
- 2026-10-12: 72
- 2026-10-10: 71
- 2026-10-06: 72
- 2026-10-04: 71

## Common questions

### What is the FeeFighter MCP server?

FeeFighter is an MCP server listed in the public MCP registry as io.github.everyai-com/fee-fighter. Audit junk fees, project annual costs and draft dispute letters. Free. This page covers its hosted endpoint (https://fee-fighter.magicteams.ai/mcp).

### Is the FeeFighter MCP server safe to use?

FeeFighter scores 77 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 FeeFighter MCP server expose?

FeeFighter exposes 4 tools: audit_fees, annual_cost, benchmark_fees, dispute_letter. Their descriptions and schemas cost roughly 708 tokens of context every time the server is loaded.

### Does the FeeFighter MCP server require authentication?

No. We connected to FeeFighter without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the FeeFighter MCP server still maintained?

FeeFighter is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://fee-fighter.magicteams.ai/mcp
- Repository: https://github.com/everyai-com/sahadeva
- Changelog RSS feed: https://verifymcp.io/servers/everyai-com-fee-fighter/fee-fighter.xml
- Changelog JSON feed: https://verifymcp.io/servers/everyai-com-fee-fighter/fee-fighter.json
- HTML version of this page: https://verifymcp.io/servers/everyai-com-fee-fighter/fee-fighter