mcpbeat Sign in

Package Pricing Lab MCP Server

answering

Package Pricing Lab is answering right now. Last checked 5 min ago. It exposes 4 tools.

Builds fixed-price service packages from costs and capacity, with margin and capacity math.

Uptime history 4 hours of history
4 hours agonow
100.0%
Uptime 24h
12 of 12 checks
4
Tools
read from the server
362 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Package Pricing Lab every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add pricing-lab --transport http https://mcp.modernmustardseed.com/pricing-lab
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "pricing-lab": {
      "url": "https://mcp.modernmustardseed.com/pricing-lab"
    }
  }
}
~/.codex/config.toml
[mcp_servers.pricing-lab]
url = "https://mcp.modernmustardseed.com/pricing-lab"
.cursor/mcp.json
{
  "mcpServers": {
    "pricing-lab": {
      "url": "https://mcp.modernmustardseed.com/pricing-lab"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "pricing-lab": {
      "url": "https://mcp.modernmustardseed.com/pricing-lab"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

build
build_packages
Turn 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
compare_models
Compare 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
package_scope_language
Write 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
stress_test_package
Show 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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.modernmustardseed.com/pricing-lab streamable-http answering 167 ms 5 min ago

Alternatives to Package Pricing Lab

same job, measured the same way
Pricemyrepair MCP
by iwanek86

UK car repair and servicing cost ranges per car model, in GBP, from PriceMyRepair.

4 tools answering
StackTab MCP
by thecompound

StackTab: SaaS service pricing and monthly stack cost estimates.

309 installs/wk local only
BeevR
by beevr

Read-only access to BeevR's services, fixed-price MVP packages, case studies and articles (EN/VI).

8 tools answering
Maintenance Log
by theluckystrike

Equipment maintenance log: assets, service entries with costs, and a due report from stored dates.

8 tools answering
Bitroad
by bitroad

Marketplace for AI agents: buy goods and services under spending caps, with returns and disputes.

65 tools answering
Seatcanvas
by seatcanvas

SeatCanvas MCP server: pricing, venue capacity estimates, and prefilled seating plans.

3 tools answering
Micropage
by micropage-sh

Create, edit and publish micropage.sh landing pages and blog posts from markup.

2 089 installs/wk answering
MCP E-Invoicing Core
by cmendezs

Base package for e-invoicing MCP servers. Compliance logic and signing keys stay with you.

709 installs/wk local only

Package Pricing Lab — questions

Answers built from our own checks of this server.

What can Package Pricing Lab do?
It exposes 4 tools, read directly from the server on our last check. Among them: build_packages, compare_models, package_scope_language, stress_test_package. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Package Pricing Lab working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 12 of 12 checks got a reply (100.0%), average response time 362 ms. The bar chart above shows every period we have measured.
How do I connect Package Pricing Lab?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Package Pricing Lab need an API key?
No. Package Pricing Lab completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Package Pricing Lab?
It answers our handshake in 362 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.