Alpaca Trading API integration for Model Context Protocol (MCP)
Package Pricing Lab is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Builds fixed-price service packages from costs and capacity, with margin and capacity math.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http package-pricing-lab-mcp https://mcp.modernmustardseed.com/pricing-lab
# 2 — ask your agent for something these tools do
# build_packages, stress_test_package, compare_models and 1 more
Package Pricing Lab costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http package-pricing-lab-mcp https://mcp.modernmustardseed.com/pricing-labReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business | object | yes | The business cost base. |
| offer_name | string | yes | What the packages sell, for example "Brand identity" or "Bathroom remodel design". |
| items | array | yes | — |
| target_margin_pct | number | no | Profit as a share of price, after owner pay and every cost. Default 30. |
| variance_buffer_pct | number | no | Extra effort added to each tier because a fixed price absorbs jobs that run long. Default 15. |
| tier_names | array | no | Names for the three tiers, smallest first. Default Essential, Standard, Complete. |
| mix_pct | array | no | Expected share of clients choosing each tier, smallest first, adding to 100. Default 30, 50, 20. |
| clients_per_month | number | no | Clients expected per month. When given, the capacity check shows hours needed and the month profit. |
| outcome_value | number | no | What the result is worth to a typical client, for a value check on each price. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business | object | yes | The business cost base. |
| package | object | yes | — |
| target_margin_pct | number | no | Default 30. |
| scope_creep_pct | array | no | Extra effort levels to test, in percent. Default 10, 25, 50. |
| sales_per_month | number | no | Normal sales of this package per month. Enables the slow month view. |
| slow_month_drop_pct | number | no | How far sales fall in a slow month, in percent. Default 40. |
| cash_reserve | number | no | Cash set aside for slow months. |
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 (defau
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business | object | yes | The business cost base. |
| current | object | yes | — |
| packages | array | yes | — |
| jobs_per_month | number | yes | — |
| efficiency_gains_pct | array | no | Effort reductions to compare, in percent. Default 0, 15, 30. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| packages | array | yes | — |
| voice | string | no | "we" (default) for a team, "I" for a solo business. |
| ascending | boolean | no | True when packages are listed smallest first and each includes the one before it. Default true when there is more than one package. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Package Pricing Lab or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Package Pricing Lab can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.