Package Pricing Lab
REMOTE · MCP.MODERNMUSTARDSEED.COM
Builds fixed-price service packages from costs and capacity, with margin and capacity math.
Available components
Last scanned (20 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1168 tokens (~292/item across 4 items; 4 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 Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 20 Oct 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.
- 18 Oct 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 69
First indexed and scored.
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 22 Oct 2026 · Probed https://mcp.modernmustardseed.com/pricing-lab
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.modernmustardseed.com | CN=YR2,O=Let's Encrypt,C=US | 11 Oct 2026 | 9 Jan 2027 | RSA 2048 | SHA256-RSA | 5037aab1b1b95f22d0713db17fad3a7354f |
| SANs: mcp.modernmustardseed.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 mcp.modernmustardseed.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| modernmustardseed.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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.modernmustardseed.com/pricing-lab | Verified | 200 | |
| http (plaintext) | http://mcp.modernmustardseed.com/pricing-lab | HTTPS enforced | 308 | https://mcp.modernmustardseed.com/pricing-lab |
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 →
build_packages Build three fixed packages ~388
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business | object | yes | The business cost base. |
| clients_per_month | number | – | Clients expected per month. When given, the capacity check shows hours needed and the month profit. |
| items | array | yes | – |
| mix_pct | array | – | Expected share of clients choosing each tier, smallest first, adding to 100. Default 30, 50, 20. |
| offer_name | string | yes | What the packages sell, for example "Brand identity" or "Bathroom remodel design". |
| outcome_value | number | – | What the result is worth to a typical client, for a value check on each price. |
| target_margin_pct | number | – | Profit as a share of price, after owner pay and every cost. Default 30. |
| tier_names | array | – | Names for the three tiers, smallest first. Default Essential, Standard, Complete. |
| variance_buffer_pct | number | – | Extra effort added to each tier because a fixed price absorbs jobs that run long. Default 15. |
No output schema declared.
No examples provided.
compare_models Compare time-based billing with packages ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business | object | yes | The business cost base. |
| current | object | yes | – |
| efficiency_gains_pct | array | – | Effort reductions to compare, in percent. Default 0, 15, 30. |
| jobs_per_month | number | yes | – |
| packages | array | yes | – |
No output schema declared.
No examples provided.
package_scope_language Write package scope language ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ascending | boolean | – | True when packages are listed smallest first and each includes the one before it. Default true when there is more than one package. |
| packages | array | yes | – |
| voice | string | – | "we" (default) for a team, "I" for a solo business. |
No output schema declared.
No examples provided.
stress_test_package Stress test a package ~272
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business | object | yes | The business cost base. |
| cash_reserve | number | – | Cash set aside for slow months. |
| package | object | yes | – |
| sales_per_month | number | – | Normal sales of this package per month. Enables the slow month view. |
| scope_creep_pct | array | – | Extra effort levels to test, in percent. Default 10, 25, 50. |
| slow_month_drop_pct | number | – | How far sales fall in a slow month, in percent. Default 40. |
| target_margin_pct | number | – | Default 30. |
No output schema declared.
No examples provided.
How do I install the Package Pricing Lab MCP server?
Package Pricing Lab is a hosted endpoint at https://mcp.modernmustardseed.com/pricing-lab, 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 · mcp.modernmustardseed.com
claude mcp add --transport http com-modernmustardseed-pricing-lab 'https://mcp.modernmustardseed.com/pricing-lab'
What is the Package Pricing Lab MCP server?
Package Pricing Lab is an MCP server listed in the public MCP registry as com.modernmustardseed/pricing-lab. Builds fixed-price service packages from costs and capacity, with margin and capacity math. This page covers its hosted endpoint (https://mcp.modernmustardseed.com/pricing-lab).
Is the Package Pricing Lab MCP server safe to use?
Package Pricing Lab 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 Package Pricing Lab MCP server expose?
Package Pricing Lab exposes 4 tools: build_packages, stress_test_package, compare_models, package_scope_language. Their descriptions and schemas cost roughly 1,067 tokens of context every time the server is loaded.
Does the Package Pricing Lab MCP server require authentication?
No. We connected to Package Pricing Lab without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Package Pricing Lab MCP server still maintained?
Package Pricing Lab is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.