_ registry / mcp streamable-http · checked 41m ago

fee-fighter

https://fee-fighter.magicteams.ai

Registry code: 8a6cdbe94eb1dc6e

api record

FeeFighter audits junk fees from a list you provide: it annualizes and totals them, flags charges above typical US ranges, duplicate names and disputable one-time fees, benchmarks categories against typical US fee ranges, and drafts dispute letters. All maths and text only; nothing stored and nothing sent.

endpoint
https://fee-fighter.magicteams.ai/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is fee-fighter live?
Yes — it answered the hub's last check (checked 41m ago). It answered 100% of checks over the last 30 days.
Is fee-fighter free to use?
Yes — the hub reached it with no key and no payment.
What tools does fee-fighter have?
4 tools: dispute_letter, annual_cost, audit_fees, benchmark_fees.
Is fee-fighter safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.8%· all time 99.8%

latency
459ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 407 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • unknown → live
_ what it is for
used for
  • audit junk fees
  • benchmark fees against typical us ranges
  • draft a fee dispute letter
  • project long-term fee cost
takes → gives
data → data, text
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • benchmark_fees reads open 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "category": {
          "type": "string",
          "description": "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, airline_checked_bag, airline_seat_fee, ticket_convenience, rental_application, subscription_app_monthly, delivery_fee, airline_change_fee, hotel_resort_fee. Omit to get the full table; an unknown key returns an error listing valid keys."
        }
      }
    }
    arguments 9 lines
  • dispute_letter reads unknown never probed

    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.

    mcp-tool

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

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "fees"
      ],
      "properties": {
        "fees": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name",
              "amount",
              "frequency"
            ],
            "properties": {
              "name": {
                "type": "string",
                "minLength": 1,
                "description": "Fee label as it appears on the statement, e.g. 'Overdraft fee' or 'Netflix'"
              },
              "amount": {
                "type": "number",
                "description": "Amount per charge in USD, greater than 0, e.g. 38 or 15.99 (for monthly fees, the monthly amount)",
                "exclusiveMinimum": 0
              },
              "category": {
                "type": "string",
                "description": "Optional benchmark 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, airline_checked_bag, airline_seat_fee, ticket_convenience, rental_application, subscription_app_monthly, delivery_fee, airline_change_fee, hotel_resort_fee. Unknown keys are ignored for benchmarking and listed in audit_fees' note."
              },
              "frequency": {
                "enum": [
                  "monthly",
                  "annual",
                  "one-time"
                ],
                "type": "string",
                "description": "How often the fee is charged: 'monthly' (x12 per year), 'annual' or 'one-time'"
              }
            }
          },
          "minItems": 1,
          "description": "Non-empty list of fees to project, each {name, amount, frequency, category?}; category is accepted but not used here"
        },
        "years": {
          "type": "integer",
          "maximum": 30,
          "minimum": 1,
          "description": "Number of years to project, integer 1-30; default 1"
        }
      }
    }
    arguments 52 lines
  • audit_fees reads unknown 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "fees"
      ],
      "properties": {
        "fees": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name",
              "amount",
              "frequency"
            ],
            "properties": {
              "name": {
                "type": "string",
                "minLength": 1,
                "description": "Fee label as it appears on the statement, e.g. 'Overdraft fee' or 'Netflix'"
              },
              "amount": {
                "type": "number",
                "description": "Amount per charge in USD, greater than 0, e.g. 38 or 15.99 (for monthly fees, the monthly amount)",
                "exclusiveMinimum": 0
              },
              "category": {
                "type": "string",
                "description": "Optional benchmark 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, airline_checked_bag, airline_seat_fee, ticket_convenience, rental_application, subscription_app_monthly, delivery_fee, airline_change_fee, hotel_resort_fee. Unknown keys are ignored for benchmarking and listed in audit_fees' note."
              },
              "frequency": {
                "enum": [
                  "monthly",
                  "annual",
                  "one-time"
                ],
                "type": "string",
                "description": "How often the fee is charged: 'monthly' (x12 per year), 'annual' or 'one-time'"
              }
            }
          },
          "minItems": 1,
          "description": "Non-empty list of fees to audit, each {name, amount, frequency, category?}"
        }
      }
    }
    arguments 46 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 8a6cdbe94eb1dc6e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8a6cdbe94eb1dc6e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/8a6cdbe94eb1dc6e/badge.svg)](https://brick.blue/agent/8a6cdbe94eb1dc6e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on magicteams.ai 14 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

6 more sit on this domain. All of them.