mcp-flatratemath
[](https://mcprush.com/to/flat-rate-math-mcp?ref=badge)
# flatratemath MCP server
A Model Context Protocol server that prices three ways of paying for
software work on one number: total cost per delivered request. It is the
stdio version of the
[flatratemath CLI](https://github.com/scrapertweeter3-prog/flatratemath),
one Python file, standard library only, nothing to install.
## Tools
`cost_per_request` prices a single lane. Give it a mode (bid for a
one-time fixed price, salary for a fully loaded monthly hire, flat for a
monthly subscription), the dollar rate, the months the work stays alive,
and the number of discrete requests you expect to submit.
`compare_lanes` takes up to three lanes and ranks them by cost per
request. An $84,000 fixed bid, an $18,290/month hire, and a $5,995/month
flat subscription over 12 months and 30 requests come back as:
flat sub: $71,940 total, $2,398 per request
fixed bid: $84,000 total, $2,800 per request
hire: $219,480 total, $7,316 per request
The flat lane in that example is a real one: the unlimited development
subscription at [Poket Dev](https://www.poketdev.com). I kept redrawing
the same spreadsheet for clients choosing between those lanes, so the
math exists as a CLI and now as a server an agent can call.
## Install
Clone the repo and point your MCP client at the file:
git clone https://github.com/scrapertweeter3-prog/mcp-flatratemath
Client command: `python3 /path/to/mcp-flatratemath/server.py`
The wire side is JSON-RPC 2.0 over stdio, one JSON object per line
(newline-delimited JSON, the MCP stdio transport).
Handshakes answered: initialize, ping, tools/list, tools/call.
## License
MIT
TDQS
Scored across 2 tools
The two tools have mostly distinct purposes: cost_per_request prices one payment lane, while compare_lanes ranks up to three lanes side by side. There is some inherent overlap because compare_lanes presumably repeats the single-lane calculation, but the boundary between single-lane pricing and multi-lane comparison is clear enough for an agent.
Both names use snake_case, but the convention is mixed: compare_lanes follows a verb_noun pattern, while cost_per_request is a noun phrase. The meanings remain readable, but the set is not fully consistent.
Two tools is thin for a standalone pricing server, though the domain is narrow enough that a single-lane calculator plus a comparison tool covers the main need. It sits at the borderline of being under-scoped.
The surface covers pricing one lane and comparing up to three lanes, which addresses the core flat-rate math use case. Minor gaps might include scenario/sensitivity analysis or saving/exporting results, but agents can work around those limitations.