Skip to content

Package Pricing Lab MCP server

com.modernmustardseed/pricing-labmodernmustardseed.comstreamable-httpv1.0.0Scanned

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

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Package Pricing Lab MCP server can do

The Package Pricing Lab MCP server is published by modernmustardseed.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: build_packages and package_scope_language), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 17, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • build_packagesTurn the work a service business does into three fixed-price packages (smallest, middle, largest).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Build three fixed packages
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • package_scope_languageWrite 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 c…1 finding

    Why it is in this group

    • The description's first verb is "write": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "package_scope_language" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "write": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Write package scope language
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • compare_modelsCompare the economics of how a business charges today, by the hour or by the day, with fixed packages for the same work.No findings

    Why it is in this group

    • The name "compare_models" says "compare": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Compare time-based billing with packages
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • stress_test_packageShow what scope creep and a slow month do to one fixed-price package.No findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Stress test a package
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:26 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.modernmustardseed.com/pricing-lab: tools/list returned 4 tools to an anonymous client, including build_packages (write), package_scope_language (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "package_scope_language" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "write": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http pricing-lab https://mcp.modernmustardseed.com/pricing-lab
claude mcp add --transport http pricing-lab https://mcp.modernmustardseed.com/pricing-lab

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pricing-lab__stress_test_package",
      "mcp__pricing-lab__compare_models"
    ],
    "ask": [
      "mcp__pricing-lab__build_packages",
      "mcp__pricing-lab__package_scope_language"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pricing-lab. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.modernmustardseed/pricing-lab/verify?hash=cfa65bab3fc3a85a8e7dd180a85dfe346ede9b6cbbae83a276072f92a91f8f1a" | jq -e '.changed == false'

Pinned hash cfa65bab3fc3, from Nov 17, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.modernmustardseed/pricing-lab/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.modernmustardseed/pricing-lab
[![Anlyon Radar](https://radar.anlyon.com/badge/com.modernmustardseed/pricing-lab.svg)](https://radar.anlyon.com/servers/com.modernmustardseed/pricing-lab)

Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.

Package Pricing Lab MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Package Pricing Lab MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Package Pricing Lab MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Package Pricing Lab MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Package Pricing Lab MCP server have?

4 tools: 2 write, 2 read. build_packages, package_scope_language, stress_test_package and compare_models.

Does the Package Pricing Lab MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Package Pricing Lab MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Package Pricing Lab MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.