Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.comil27/debt-payoff-mcp

REMOTE · DEBTFREE.RUGSCORE.WORKERS.DEV

RETIRED - this server is discontinued and its backend is offline. Do not use.

0 this week 72 Trust /100

Last scanned (17 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 444 tokens (~148/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://debtfree.rugscore.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rugscore.workers.dev CN=WE1,O=Google Trust Services,C=US 22 Oct 2026 20 Jan 2027 ECDSA 256 ECDSA-SHA256 36c00e33ac8728a90ec5c843addf8f13
SANs: rugscore.workers.dev, *.rugscore.workers.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of debtfree.rugscore.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://debtfree.rugscore.workers.dev/mcp Verified 200
http (plaintext) http://debtfree.rugscore.workers.dev/mcp Served over HTTP 200
MCP tools · 3 exposed · ~385 tokens

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 →

Tool Tokens
budget_50_30_20 ~120

Split a monthly take-home income into a 50/30/20 budget (needs / wants / savings & debt). Returns dollar targets for each bucket. Optional custom percentages.

NameTypeReqDescription
monthlyIncomenumberyesMonthly take-home (after-tax) income in dollars.
needsPctnumber–Optional. % for needs (default 50).
savingsPctnumber–Optional. % for savings & debt payoff (default 20).
wantsPctnumber–Optional. % for wants (default 30).

No output schema declared.

No examples provided.

debt_payoff_plan ~155

Plan how to pay off debt(s): returns months to debt-free, total interest, and payoff order — comparing the snowball (smallest balance first) and avalanche (highest APR first) strategies. Accepts one debt or many.

NameTypeReqDescription
aprnumber–Annual interest rate %, single-debt shortcut.
balancenumber–Single-debt shortcut (use with apr & min instead of debts[]).
debtsarray–Your debts; each has name, balance, apr (annual %), min (monthly minimum payment).
extranumber–Extra $/month toward debt beyond the minimums. Default 0.
minnumber–Monthly minimum payment, single-debt shortcut.

No output schema declared.

No examples provided.

savings_goal ~110

How long to reach a savings goal. Given a target amount, monthly contribution, optional current savings and APY, returns months/years to reach it and total contributed.

NameTypeReqDescription
apynumber–Optional. Annual interest/return % on savings (default 0).
currentSavednumber–Optional. Amount already saved (default 0).
goalAmountnumberyesTarget amount to save, in dollars.
monthlyContributionnumberyesAmount saved each month, in dollars.

No output schema declared.

No examples provided.

Install

How do I install the io.github.comil27/debt-payoff-mcp server?

io.github.comil27/debt-payoff-mcp is a hosted endpoint at https://debtfree.rugscore.workers.dev/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.

remote · debtfree.rugscore.workers.dev

# add to Claude Code
claude mcp add --transport http comil27-debt-payoff-mcp 'https://debtfree.rugscore.workers.dev/mcp'
Common questions

What is the io.github.comil27/debt-payoff-mcp server?

io.github.comil27/debt-payoff-mcp is listed in the public MCP registry as io.github.comil27/debt-payoff-mcp. RETIRED - this server is discontinued and its backend is offline. Do not use. This page covers its hosted endpoint (https://debtfree.rugscore.workers.dev/mcp).

Is the io.github.comil27/debt-payoff-mcp server safe to use?

io.github.comil27/debt-payoff-mcp scores 72 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 io.github.comil27/debt-payoff-mcp server expose?

io.github.comil27/debt-payoff-mcp exposes 3 tools: debt_payoff_plan, budget_50_30_20, savings_goal. Their descriptions and schemas cost roughly 385 tokens of context every time the server is loaded.

Does the io.github.comil27/debt-payoff-mcp server require authentication?

No. We connected to io.github.comil27/debt-payoff-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.comil27/debt-payoff-mcp server still maintained?

io.github.comil27/debt-payoff-mcp 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 did VerifyMCP test on the io.github.comil27/debt-payoff-mcp server?

VerifyMCP ran 12 checks on io.github.comil27/debt-payoff-mcp, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.comil27/debt-payoff-mcp: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.