Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Business Frameworks

REMOTE · BUSINESS-FRAMEWORKS.MATRYOSHKA-PARADIGMS.WORKERS.DEV

Operating judgement for businesses under $50M revenue. Free top layer; nodes and bundles over x402.

+3 this week 70 Trust /100

Last scanned (3 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Project Management

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1656 tokens (~276/item across 6 items; 6 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Changelog

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.

  • 23 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “bf_apply_decision” rewrote its description, which is the text the model reads security
    • Tool “bf_decision_schema” rewrote its description, which is the text the model reads security
    • Tool “bf_read_bundle” rewrote its description, which is the text the model reads security
    • Tool “bf_read_node” rewrote its description, which is the text the model reads security
    • Tool “bf_resolve” rewrote its description, which is the text the model reads security
    • Tool “bf_apply_decision” now declares an output schema ▲ functional
    • Tool “bf_catalogue” now declares an output schema ▲ functional
    • Tool “bf_decision_schema” now declares an output schema ▲ functional
    • Tool “bf_read_bundle” now declares an output schema ▲ functional
    • Tool “bf_read_node” now declares an output schema ▲ functional
    • Tool “bf_resolve” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • Server version: 2026.10.13 → 2026.10.22 functional
    • “bf_decision_schema” reworded the description of “decision” cosmetic
    • “bf_read_node” reworded the description of “variant” cosmetic
  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 0
    • Server version: 2026.10.10 → 2026.10.13 functional
  • 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
Diagnostics

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 24 Oct 2026 · Probed https://business-frameworks.matryoshka-paradigms.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=matryoshka-paradigms.workers.dev CN=YE1,O=Let's Encrypt,C=US 15 Sept 2026 14 Dec 2026 ECDSA 256 ECDSA-SHA384 57ba197f59361131aa11fe55d79806a6b72
SANs: *.matryoshka-paradigms.workers.dev, matryoshka-paradigms.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of business-frameworks.matryoshka-paradigms.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://business-frameworks.matryoshka-paradigms.workers.dev/mcp Verified 200
http (plaintext) http://business-frameworks.matryoshka-paradigms.workers.dev/mcp Inconclusive 405
MCP tools · 6 exposed · ~1,537 tokens

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 →

Tool Tokens
bf_apply_decision ~236

Runs one decision node's rule on the numbers you send and returns the computed figures, a verdict, the actions in order, the check to keep and the node text with its citations. Deterministic: the result comes from the published rule, not from a model. Costs the decision's catalogue price ($0.05, USDC on Base over x402); the input is checked first, and an input the rule cannot use is refused without charge. Call it when the user has the figures for a specific decision in a business under about $50M in revenue and wants the rule's answer for them; get the schema from bf_decision_schema first. When the question gives figures for a decision, the applied route computes them; the answer reports its result and does not recompute it. Do not call it with invented or placeholder figures, and do not treat the verdict as tax, legal or investment advice.

NameTypeReqDescription
decisionstringyesDecision path from bf_decision_schema, e.g. "cash-flow/decide/runway".
inputobjectyesThe figures, shaped as that decision's input_schema.
NameTypeReqDescription
appliedobject––
cite_asstring––
handlestringyes–
nodeobject––

No examples provided.

bf_catalogue ~180

Lists every Business Frameworks node: handle, title, layer, token count, price, whether it is free, and whether its decision rule can be run on numbers. Business Frameworks is operating judgement for running a business from launch to about $50M in revenue: value, cash flow, risk (the cost of capital) and growth, down to ten decision rules. Call this first, once, to choose which node answers the question; pass `branch` to see one branch only. Free. Do not use it for businesses above about $50M in revenue, for tax, legal or accounting treatment, or for market data: it holds judgement and rules, not figures about any company.

NameTypeReqDescription
branchstring–One of: equation, value, cash-flow, risk, growth, decision, market. Omit for the whole catalogue.
NameTypeReqDescription
accessstring––
bundlesobject––
cite_asstring––
license_urlstring––
nodesarray––
paymentstring––
productstring––
scopestring––
versionstring––

No examples provided.

bf_decision_schema ~177

Returns the input schema, an example input, the price and the fit record (what the framework does for this decision by model, before paying) for one of the applied decisions (reinvest or distribute, build or run for cash, cash cycle, runway, owner pay, hurdle rate, concentration, pace of growth, price, adjacency; and, in the market branch, verdict, pricing power, binding node, rent, shock). Free. Call it before bf_apply_decision to learn which numbers the rule needs and what each one means; without `decision` it lists them all. Do not guess missing inputs to fill the schema: ask the user for the figures the business actually has.

NameTypeReqDescription
decisionstring–Decision path, e.g. "risk/decide/hurdle". Omit to list the fifteen.
NameTypeReqDescription
decisionstring––
decisionsarray––
example_inputobject––
fitobject––
handlestring––
howstring––
input_schemaobject––
price_usdstring|number|null––
summarystring––
titlestring––

No examples provided.

bf_read_bundle ~221

Returns the nodes of one bundle in order — the central node full, the supporting nodes terse — with citations and a cite-as line per node, on one settlement at the quoted price (a flat $0.05 for every bundle, band included; USDC on Base over x402). Pass the bundle id from bf_resolve or bf_catalogue, and a band to add the scale band for the business's revenue. Call it after bf_resolve has quoted the bundle and the user accepts the price; the quote's url is the same resource over HTTP. Do not call it to browse: the quote already lists the nodes and the price, and a narrow question is cheaper node by node through bf_read_node.

NameTypeReqDescription
bandstring–A scale band to add, by slug ("1-5m") or label ("$1–5M"); omit for the bundle without a band.
bundlestringyesBundle id from bf_resolve or bf_catalogue, e.g. "runway"; the quote url is accepted too.
NameTypeReqDescription
cite_asstring––
handlestring––
idstring––
nodesarray––
price_usdstring|number|null––
taskstring––

No examples provided.

bf_read_node ~356

Returns one node with its citations and a cite-as line; `variant` chooses full (the default), terse (the lede alone) or agent (the same text as fields: scope, inputs, rule, action, check, units, example, the applied route, the recheck, and two strings to paste: recheck_note and closing_citation) at the same price. Free nodes (marked in bf_catalogue) cost nothing; the rest cost their catalogue price ($0.02 to $0.05, USDC on Base over x402), charged once per call, only when the node is returned. Call it with a `path` from bf_catalogue when the question needs that node's rule; prefer variant agent when you will answer from it (the decision in one sentence, the first step, the reason, the next check, the offer to write the recheck into the user's notes, then closing_citation last). Read the free parent first; use bf_resolve when the question takes several nodes. Do not call a paid path to see what it contains: the catalogue line says what it covers; a rule on numbers is bf_apply_decision.

NameTypeReqDescription
pathstringyesNode path from bf_catalogue, e.g. "risk" (free) or "risk/decide/hurdle" (paid). A full handle is accepted.
variantstring–full (default): lede, conditions and reasoning; terse: the lede alone; agent: the same text as fields (scope, inputs, rule, action, check, reasoning, units, example, apply, recheck, recheck_note, clo…
NameTypeReqDescription
actionstring|null––
apply–––
checkstring|null––
citationsarray––
cite_asstring––
citesarray––
closing_citationstring––
example–––
free_first–––
handlestringyes–
inputsstring|null––
kindstring––
leads_toarray––
levelsobject––
reasoningstring|null––
recheck–––
recheck_notestring|null––
relatedarray––
rulestring|null––
scopeobject––
textstring––
titlestring––
tokensnumber––
units–––
urlstring––
variantstring––
versionsarray––

No examples provided.

bf_resolve ~367

Quotes the minimal set of nodes that answers a broad task — a decision bundle, a market (chain) bundle or a cross bundle — with its price — one flat price, USD 0.05, with or without its scale band — stated before anything is paid. Deterministic and free: a named bundle or decision wins, then the input fields sent, then the authored patterns of the question; on ambiguity it returns candidates with their task lines, and with no match the task lines to choose from. Call it when the user's question takes more than one node (a whole decision with its context, a supply chain read, a shock traced to a seat), passing the question, revenue_usd and chain_position when known; then buy the quote with bf_read_bundle or read nodes one at a time with bf_read_node. Do not use it for a single term or a single rule, which bf_catalogue and bf_read_node answer more cheaply, and do not treat a quote as an answer: it names the nodes and the price, nothing more.

NameTypeReqDescription
bundlestring–A bundle id from a task line, when the caller already knows which.
chain_positionstring–Where the business sits on the chain being read: binding_upstream, binding_downstream, at_binding or unknown.
decisionstring–A decision path when the task is one decision, e.g. "cash-flow/decide/runway".
inputsobject–The figures already in hand, by field name; the resolver reads the names, not the values.
questionstring–The task in the user's words (up to 2,000 characters).
revenue_usdnumber–Annual revenue in US dollars, to pick the scale band.
NameTypeReqDescription
accessstring––
bundleobject––
bystring––
candidatesarray––
howstring––
matchstring––
tasksarray––

No examples provided.

Install

How do I install the Business Frameworks MCP server?

Business Frameworks is a hosted endpoint at https://business-frameworks.matryoshka-paradigms.workers.dev/mcp, 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 · business-frameworks.matryoshka-paradigms.workers.dev

# add to Claude Code
claude mcp add --transport http matryoshka-paradigms-business-frameworks 'https://business-frameworks.matryoshka-paradigms.workers.dev/mcp'
Common questions

What is the Business Frameworks MCP server?

Business Frameworks is an MCP server listed in the public MCP registry as io.github.matryoshka-paradigms/business-frameworks. Operating judgement for businesses under $50M revenue. Free top layer; nodes and bundles over x402. This page covers its hosted endpoint (https://business-frameworks.matryoshka-paradigms.workers.dev/mcp).

Is the Business Frameworks MCP server safe to use?

Business Frameworks scores 70 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 Business Frameworks MCP server expose?

Business Frameworks exposes 6 tools: bf_catalogue, bf_read_node, bf_decision_schema, bf_apply_decision, bf_resolve, bf_read_bundle. Their descriptions and schemas cost roughly 1,537 tokens of context every time the server is loaded.

Does the Business Frameworks MCP server require authentication?

No. We connected to Business Frameworks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Business Frameworks MCP server still maintained?

Business Frameworks is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.