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.

Penny Rounding

REMOTE · PENNY-ROUNDING.GUMBALLTOOLS.COM · SCANNED SEP 25

Round cash totals to the nearest nickel correctly — after tax, on the total, cash only.

+3 this week 73 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1505 tokens (~501/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 Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 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
Install

How do I install the Penny Rounding MCP server?

Penny Rounding is a hosted endpoint at https://penny-rounding.gumballtools.com/api/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 · penny-rounding.gumballtools.com

# add to Claude Code
claude mcp add --transport http com-gumballtools-penny-rounding 'https://penny-rounding.gumballtools.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-gumballtools-penny-rounding": {
      "url": "https://penny-rounding.gumballtools.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-gumballtools-penny-rounding": {
      "type": "http",
      "url": "https://penny-rounding.gumballtools.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-gumballtools-penny-rounding]
url = "https://penny-rounding.gumballtools.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-gumballtools-penny-rounding": {
      "type": "remote",
      "url": "https://penny-rounding.gumballtools.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-gumballtools-penny-rounding --url 'https://penny-rounding.gumballtools.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-gumballtools-penny-rounding:
    url: "https://penny-rounding.gumballtools.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-gumballtools-penny-rounding": {
      "Transport": "http",
      "Url": "https://penny-rounding.gumballtools.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-gumballtools-penny-rounding -t streamable-http -u 'https://penny-rounding.gumballtools.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "com-gumballtools-penny-rounding": {
      "type": "http",
      "url": "https://penny-rounding.gumballtools.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 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
  • 24 Sept 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.

  • 22 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 15 Sept 26 +1

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

  • 13 Sept 26 +1

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

  • 11 Sept 26 +1

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

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 25 Sept 2026 · Probed https://penny-rounding.gumballtools.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.gumballtools.com CN=YR2,O=Let's Encrypt,C=US 6 Sept 2026 5 Dec 2026 RSA 2048 SHA256-RSA 60927985e79d22e7a1106139f609d74b0e4
SANs: *.gumballtools.com, gumballtools.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of penny-rounding.gumballtools.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
gumballtools.com. absent 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
Header Value
strict-transport-security max-age=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://penny-rounding.gumballtools.com/api/mcp Verified 200
http (plaintext) http://penny-rounding.gumballtools.com/api/mcp HTTPS enforced 308 https://penny-rounding.gumballtools.com/api/mcp
MCP tools · 3 exposed · ~1,505 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
price_band ~474

For a list price and a tax rate, find every nearby list price that settles to the SAME cash total, and the highest one. Use this for "what price should I charge" and "can I price to gain from rounding" questions. There is exactly one free move here and it is easy to get backwards, so do not reason about it unaided: Rounding collapses a band of five consecutive list prices onto one nickel. At 0% tax, $19.98 through $20.02 all settle to $20.00 in cash. Within that band the cash collected is IDENTICAL, so the highest price in it is strictly better — same from cash customers, up to 4 cents more from every card customer. That is genuinely free. The move that looks clever and is not: pricing BELOW a nickel so rounding "adds" a couple of cents. You collect the same cash and less on card. The rounding delta is not revenue. Do not recommend it. Input: `listPrice` as a dollar string, `taxRatePercent`, and optionally `spreadCents` (1-50, default 5) for how far either side to look. Returns: the whole band, the highest price in it, the free gain in cents (never more than 4), and a verdict. Tell the user the size of the number. Four cents is not a pricing strategy.

NameTypeReqDescription
listPricestring|numberyesA STRING is read as dollars ("19.99"); a NUMBER is read as integer CENTS (1999). A non-integer number is refused rather than guessed at.
rulestring–symmetric (default) is the Common Cents Act and Canadian method. always-down is Indiana's rule for cash payments of TAX, not a retail rule. always-up is not law anywhere for retail and is here only t…
spreadCentsinteger–How far either side to look, 1-50. Default 5, which is one whole band.
taxRatePercentnumber–Percentage, e.g. 8.25 — not 0.0825. Supply it whenever it is known: rounding happens after tax, so the rate decides which nickel the total lands on.

No output schema declared.

No examples provided.

round_cash_total ~662

Settle a transaction under post-penny cash rounding: exact subtotal, tax on the exact subtotal, then round the final total to the nearest nickel — and only for cash. Use this for any "what does X round to" or "what do I owe in cash" question. Four things are wrong in most explanations of this, and each one changes the answer: 1. CASH ONLY. Card, EFT, and gift-card payments are still priced to the cent. The same basket legitimately comes to two different amounts by tender. If asked about a card payment, do not round. 2. THE TOTAL, NOT EACH ITEM. Rounding per item multiplies the effect by the basket size. Five items at $0.99 total $4.95 — already a nickel, no rounding — where per-item rounding would collect $5.00. 3. AFTER TAX. Tax is computed on the exact subtotal and the rounding comes last. Rounding the base first changes the tax owed. 4. THE DIGIT DECIDES. 1, 2, 6, 7 round down; 3, 4, 8, 9 round up; 0 and 5 stand. Do not reason about "nearest" from scratch, and do not assume rounding is always up. Input: pass `subtotal` as a dollar string ("19.99") or `items` as a list. A NUMERIC amount is read as CENTS and a STRING as dollars — 1999 and "19.99" are the same amount, 19.99 as a number is refused. Pass `taxRatePercent` as a percentage (8.25, not 0.0825); rounding depends on it, so omitting it usually gives the wrong nickel. `tender` is cash or card, default cash. `rule` is symmetric (default), always-down, always-up, or none. Returns: the exact subtotal, tax, exact total, the rounded amount due, the signed delta, which digit decided it, warnings, and a `disclaimer` field. THIS IS NOT LEGAL OR TAX ADVICE. There was no federal rounding law as of September 2026 and state law varies. Do not tell a user what their jurisdiction requires — report the arithmetic and the caveats.

NameTypeReqDescription
itemsarray–Line items, totalled in exact cents. Rounding applies to the TOTAL only.
rulestring–symmetric (default) is the Common Cents Act and Canadian method. always-down is Indiana's rule for cash payments of TAX, not a retail rule. always-up is not law anywhere for retail and is here only t…
subtotalstring|number–The pre-tax subtotal. Use this or `items`.
taxRatePercentnumber–Percentage, e.g. 8.25 — not 0.0825. Supply it whenever it is known: rounding happens after tax, so the rate decides which nickel the total lands on.
tenderstring–Default cash. A card is NEVER rounded — if the user is paying by card, the exact total is the answer and any rounding rule is ignored.

No output schema declared.

No examples provided.

rounding_impact ~369

Compute what cash rounding is actually worth across a list of prices: mean delta per transaction, the up/down/unchanged split, and a per-thousand figure. Use this whenever someone asks whether rounding costs or earns money — a very common question and one usually answered with a guess. Do not guess. Symmetric rounding nets to EXACTLY zero over evenly spread totals, because that is what it was designed to do. Real price lists all end in .99 and are not evenly spread, so the true figure is small but not always zero and it moves with the tax rate. This computes it for the actual prices given. Input: `prices` is a list of dollar strings or integer cents. `taxRatePercent` matters, because tax decides which nickel each total lands on. `rule` defaults to symmetric; pass always-up to quantify what the "just round everything up" idea would be worth (about 2 cents a sale, and no jurisdiction has adopted it for retail). Returns: mean and total delta in cents, the split, a per-thousand transaction figure, a per-price breakdown, and a plain-language verdict. Report the verdict — the size of the number is the answer.

NameTypeReqDescription
pricesarrayyesThe prices actually charged.
rulestring–symmetric (default) is the Common Cents Act and Canadian method. always-down is Indiana's rule for cash payments of TAX, not a retail rule. always-up is not law anywhere for retail and is here only t…
taxRatePercentnumber–Percentage, e.g. 8.25 — not 0.0825. Supply it whenever it is known: rounding happens after tax, so the rate decides which nickel the total lands on.

No output schema declared.

No examples provided.

Common questions

What is the Penny Rounding MCP server?

Penny Rounding is an MCP server listed in the public MCP registry as com.gumballtools/penny-rounding. Round cash totals to the nearest nickel correctly, after tax, on the total, cash only. This page covers its hosted endpoint (https://penny-rounding.gumballtools.com/api/mcp).

Is the Penny Rounding MCP server safe to use?

Penny Rounding scores 73 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 Penny Rounding MCP server expose?

Penny Rounding exposes 3 tools: round_cash_total, rounding_impact, price_band. Their descriptions and schemas cost roughly 1,505 tokens of context every time the server is loaded.

Does the Penny Rounding MCP server require authentication?

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

Is the Penny Rounding MCP server still maintained?

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