Package Pricing Lab MCP server
online · 100% uptimeBuilds fixed-price service packages from costs and capacity, with margin and capacity math.
Little public usage data yet
Reviews
Write oneNobody has reviewed Package Pricing Lab yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Package Pricing Lab tools (4, 1 write)
write = sends, deletes, buys or postsbuild_packagesFreeTurn the work a service business does into three fixed-price packages (smallest, middle, largest). Takes the cost base (fixed costs, owner pay, staff, delivery capacity) and the deliverables the business offers, each marked core (every client needs it), common (most clients want it) or premium (some clients want it), with its typical effort and direct cost. Returns each tier with what it includes and leaves out, its cost, break-even price, target price, a recommended price rounded up to a clean number, margin and profit per sale, how far the work can overrun before the margin hits zero, and a capacity check: hours needed, break-even clients a month, and the month profit after owner pay. All results are deterministic arithmetic with the method explained. Adjustments to what was built are treated as included, so effort carries a variance buffer.
compare_modelsFreeCompare the economics of how a business charges today, by the hour or by the day, with fixed packages for the same work. Takes the cost base, the current rate and unit, the share of hours worked that reach an invoice, one to three packages with price and typical effort, and jobs per month. The current rate always comes from the user and is never assumed. Returns, at several efficiency gains (default 0, 15 and 30 percent less effort as delivery gets repeatable), revenue and profit per job and per month under each model, earnings per hour worked, revenue ceilings at full capacity, the package price that matches what each job collects today, and plain findings. Deterministic arithmetic with the method explained.
package_scope_languagewrite actionFreeWrite plain scope language for one to three fixed packages: an included line for each deliverable, an adjustments line (adjustments to anything delivered are included at no added cost), out-of-scope lines (deliverables from larger packages and anything listed as excluded), the rule that a genuinely new deliverable becomes a new package scoped and priced before work starts, worked boundary examples, and a ready-to-paste text block per package. Lines that use time-based or extra-charge wording are left out and named in notes. Written in "we" by default or "I" for a solo business.
stress_test_packageFreeShow what scope creep and a slow month do to one fixed-price package. Takes the cost base, the package price, its typical effort and direct cost, and optionally sales per month and a cash reserve. Returns margin and profit per sale at each scope creep level (default 10, 25 and 50 percent more effort on the same deliverables), the overrun at which the package earns nothing, the price that holds the target margin at the worst case, and the month view: a normal month, a slow month (default 40 percent fewer sales), a slow month with creep, break-even sales a month, and how many slow months the reserve covers. Deterministic arithmetic with the method explained.
Public scan report
scanner v0.1.10 · 2026-10-12 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 159ms20/20
- Tool poisoning4 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
- Maintenanceno repository listed3/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
Findings (2)
- highWrite-action tools reachable without authentication
auth.open-write - lowNo source repository listed
maint.no-repo
How Package Pricing Lab compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 65/100
- higher than 20% of 48,273 servers
- Tools
- 4
- the typical server has 7
- Tools that change things
- 25%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 402 ms
- faster than 38% of 30,037 servers
What its tools let an agent do: 3 read · 1 change
Install Package Pricing Lab in Claude Code, Cursor or VS Code
claude mcp add --transport http pricing-lab https://mcp.modernmustardseed.com/pricing-lab
Package Pricing Lab: common questions
- Is Package Pricing Lab MCP server safe?
- With care: it is graded C, so read the findings first (65/100). Read the Package Pricing Lab safety report
- How do I install Package Pricing Lab?
- It runs remotely at mcp.modernmustardseed.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Package Pricing Lab need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Package Pricing Lab maintained?
- The latest release is v1.0.0.
- Is Package Pricing Lab up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Package Pricing Lab compare with other MCP servers?
- safety score 65/100 (higher than 20% of 48,273 servers); tools 4 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.