SaSame MCP Observatory + Gold Rush Town

factory_start

Start the real SaSame MCP Factory lifecycle from one of seven canonical creator entry types. During Capability Control Beta, free listing, guided build, repair and monitoring entries can start without a payment method; endpoint_url is required only for live_entry/underperforming_entry/monitoring_entry and can be supplied later for guided builds. New paid membership checkout is disabled in beta, while existing subscriber continuity remains preserved. If checkout is re-enabled in the future, guided/underperforming entries return to the account-level membership gate. No checkout is created at start; a redirect never grants access.

Input Schema

TableJSON Schema

Name	Required	Description
`entry_type`	No	Where this creator enters the one Factory lifecycle; defaults to live_entry for backward compatibility
`journey_id`	No	Alias for entry_type. If both are supplied they must match; disagreement fails closed
`buyer_email`	No	Only needed for a fixture/legacy activation checkout journey; membership/free journeys bill at the account level and never bind an email
`endpoint_url`	No	Public MCP endpoint owned/operated by the creator. REQUIRED for live_entry/underperforming_entry/monitoring_entry; OPTIONAL for the four guided-build journeys (provide it later via factory_provide_endpoint)
`principal_id`	No	v2 principal binding; optional during free beta and used to preserve private account/lifecycle status. Required only when future membership gating is re-enabled for guided/underperforming journeys.
`principal_key`	No	v2 principal binding; optional during free beta and used to preserve private account/lifecycle status. Required only when future membership gating is re-enabled for guided/underperforming journeys.
`organization_id`	No	v2 principal binding; legacy identity fields remain accepted
`creator_identity`	Yes	Stable creator reference; SaSame persists only its SHA-256 hash
`verification_mode`	No	Use sasame_self_test_fixture only for SaSame's own synthetic release verification; it is excluded from demand/revenue KPIs
`ownership_proof_url`	No	Same-origin URL that will serve the returned ownership_proof_body; defaults to /.well-known/sasame-factory-claim.txt
`analytics_correlation_id`	No	Optional opaque journey token generated by the caller. SaSame stores only its SHA-256 hash and uses it to correlate Web/MCP/Factory/checkout/fulfillment analytics; never put email, URL, credentials or personal data here.
`self_test_capability_token`	No	Required alongside self_test_free_distribution: a release-bound, single-use, short-lived token signed with SaSame's trust key. Mint with scripts/factory/mint-self-test-capability.mjs (VPS-only). Unrelated to any other argument; omitting it while self_test_free_distribution=true fails closed.
`self_test_free_distribution`	No	SaSame-internal only: requires verification_mode=sasame_self_test_fixture AND a valid self_test_capability_token. Completes the full lifecycle (through DISTRIBUTION) with zero Stripe interaction and never touches the real public shelf — the receipt is stamped shelf=sasame_internal_self_test / plan_context=self_test_no_charge / north_star_counted=false so it can never be mistaken for a real listing. External creators cannot use this to skip payment; it throws for any non-fixture traffic or without a valid token.
`stripe_live_payment_acknowledged`	No	Deprecated compatibility field. factory_start never charges, and public Activation checkout creation is closed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedInput schema / properties / buyer_email / pattern

Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"

Changed2 schema fields changedAug 24, 2026

changedInput schema / properties / principal_id / description

Previous value: -"v2 principal binding; required for the membership-gated guided/underperforming journeys"New value: +"v2 principal binding; optional during free beta and used to preserve private account/lifecycle status. Required only when future membership gating is re-enabled for guided/underperforming journeys."

changedInput schema / properties / principal_key / description

Previous value: -"v2 principal binding; required for the membership-gated guided/underperforming journeys"New value: +"v2 principal binding; optional during free beta and used to preserve private account/lifecycle status. Required only when future membership gating is re-enabled for guided/underperforming journeys."

Changed1 schema field changedJul 29, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedJul 25, 2026

addedInput schema / properties / analytics_correlation_id

Added value: +{
+  "description": "Optional opaque journey token generated by the caller. SaSame stores only its SHA-256 hash and uses it to correlate Web/MCP/Factory/checkout/fulfillment analytics; never put email, URL, credentials or personal data here.",
+  "maxLength": 160,
+  "minLength": 8,
+  "pattern": "^[A-Za-z0-9._:-]+$",
+  "type": "string"
+}

changedInput schema / properties / stripe_live_payment_acknowledged / description

Previous value: -"Optional acknowledgement that, IF a later factory_checkout is used for a fixture/legacy activation lifecycle, completing that Checkout charges REAL money via Stripe LIVE mode. factory_start itself never charges."New value: +"Deprecated compatibility field. factory_start never charges, and public Activation checkout creation is closed."

Changed2 schema fields changedJul 22, 2026

addedInput schema / properties / self_test_capability_token

Added value: +{
+  "description": "Required alongside self_test_free_distribution: a release-bound, single-use, short-lived token signed with SaSame's trust key. Mint with scripts/factory/mint-self-test-capability.mjs (VPS-only). Unrelated to any other argument; omitting it while self_test_free_distribution=true fails closed.",
+  "type": "string"
+}

changedInput schema / properties / self_test_free_distribution / description

Previous value: -"SaSame-internal only: requires verification_mode=sasame_self_test_fixture. Completes the full lifecycle (through DISTRIBUTION) with zero Stripe interaction and never touches the real public shelf — the receipt is stamped shelf=sasame_internal_self_test / plan_context=self_test_no_charge / north_star_counted=false so it can never be mistaken for a real listing. External creators cannot use this to skip payment; it throws for any non-fixture traffic."New value: +"SaSame-internal only: requires verification_mode=sasame_self_test_fixture AND a valid self_test_capability_token. Completes the full lifecycle (through DISTRIBUTION) with zero Stripe interaction and never touches the real public shelf — the receipt is stamped shelf=sasame_internal_self_test / plan_context=self_test_no_charge / north_star_counted=false so it can never be mistaken for a real listing. External creators cannot use this to skip payment; it throws for any non-fixture traffic or without a valid token."

Changed1 schema field changedJul 21, 2026

addedInput schema / properties / self_test_free_distribution

Added value: +{
+  "description": "SaSame-internal only: requires verification_mode=sasame_self_test_fixture. Completes the full lifecycle (through DISTRIBUTION) with zero Stripe interaction and never touches the real public shelf — the receipt is stamped shelf=sasame_internal_self_test / plan_context=self_test_no_charge / north_star_counted=false so it can never be mistaken for a real listing. External creators cannot use this to skip payment; it throws for any non-fixture traffic.",
+  "type": "boolean"
+}

Changed7 schema fields changedJul 20, 2026

changedInput schema / properties / buyer_email / description

Previous value: -"Stripe live buyer email; SaSame persists only its SHA-256 binding"New value: +"Only needed for a fixture/legacy activation checkout journey; membership/free journeys bill at the account level and never bind an email"

changedInput schema / properties / endpoint_url / description

Previous value: -"Public MCP endpoint owned or operated by the creator; currently required for real inspection, claim and Stripe LIVE fulfillment in every entry type"New value: +"Public MCP endpoint owned/operated by the creator. REQUIRED for live_entry/underperforming_entry/monitoring_entry; OPTIONAL for the four guided-build journeys (provide it later via factory_provide_endpoint)"

addedInput schema / properties / organization_id

Added value: +{
+  "description": "v2 principal binding; legacy identity fields remain accepted",
+  "minLength": 8,
+  "type": "string"
+}

addedInput schema / properties / principal_id

Added value: +{
+  "description": "v2 principal binding; required for the membership-gated guided/underperforming journeys",
+  "minLength": 8,
+  "type": "string"
+}

addedInput schema / properties / principal_key

Added value: +{
+  "description": "v2 principal binding; required for the membership-gated guided/underperforming journeys",
+  "minLength": 32,
+  "type": "string"
+}

changedInput schema / properties / stripe_live_payment_acknowledged / description

Previous value: -"Required acknowledgement that completing the returned Checkout charges REAL money via Stripe LIVE mode at the owner-set activation price. Reading tools never charges."New value: +"Optional acknowledgement that, IF a later factory_checkout is used for a fixture/legacy activation lifecycle, completing that Checkout charges REAL money via Stripe LIVE mode. factory_start itself never charges."

changedInput schema / required

Previous value: -[
-  "endpoint_url",
-  "creator_identity",
-  "buyer_email",
-  "stripe_live_payment_acknowledged"
-]New value: +[
+  "creator_identity"
+]

Changed5 schema fields changedJul 19, 2026

changedInput schema / properties / buyer_email / description

Previous value: -"Stripe test buyer email; SaSame persists only its SHA-256 binding"New value: +"Stripe live buyer email; SaSame persists only its SHA-256 binding"

changedInput schema / properties / endpoint_url / description

Previous value: -"Public MCP endpoint owned or operated by the creator; currently required for real inspection, claim and Stripe TEST fulfillment in every entry type"New value: +"Public MCP endpoint owned or operated by the creator; currently required for real inspection, claim and Stripe LIVE fulfillment in every entry type"

addedInput schema / properties / stripe_live_payment_acknowledged

Added value: +{
+  "const": true,
+  "description": "Required acknowledgement that completing the returned Checkout charges REAL money via Stripe LIVE mode at the owner-set activation price. Reading tools never charges.",
+  "type": "boolean"
+}

removedInput schema / properties / stripe_test_only_acknowledged

Removed value: -{
-  "const": true,
-  "description": "Required acknowledgement that this conveyor accepts Stripe test-mode payment only",
-  "type": "boolean"
-}

changedInput schema / required

Previous value: -[
-  "endpoint_url",
-  "creator_identity",
-  "buyer_email",
-  "stripe_test_only_acknowledged"
-]New value: +[
+  "endpoint_url",
+  "creator_identity",
+  "buyer_email",
+  "stripe_live_payment_acknowledged"
+]

Changed3 schema fields changedJul 19, 2026

changedInput schema / properties / endpoint_url / description

Previous value: -"Public MCP endpoint owned or operated by the creator"New value: +"Public MCP endpoint owned or operated by the creator; currently required for real inspection, claim and Stripe TEST fulfillment in every entry type"

addedInput schema / properties / entry_type

Added value: +{
+  "description": "Where this creator enters the one Factory lifecycle; defaults to live_entry for backward compatibility",
+  "enum": [
+    "idea_entry",
+    "blueprint_entry",
+    "building_entry",
+    "ready_entry",
+    "live_entry",
+    "underperforming_entry",
+    "monitoring_entry"
+  ],
+  "type": "string"
+}

addedInput schema / properties / journey_id

Added value: +{
+  "description": "Alias for entry_type. If both are supplied they must match; disagreement fails closed",
+  "enum": [
+    "idea_entry",
+    "blueprint_entry",
+    "building_entry",
+    "ready_entry",
+    "live_entry",
+    "underperforming_entry",
+    "monitoring_entry"
+  ],
+  "type": "string"
+}

AddedJul 19, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond annotations, the description discloses important behavioral facts: no checkout is created at start, a redirect never grants access, existing subscriber continuity is preserved, and future membership gating behavior is described. It does not elaborate on side effects or resumability, but the annotations already flag non-idempotency and readOnlyHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and then provides dense, relevant beta and payment context. It is longer than average but each sentence carries policy or conditional-usage value. There is minor redundancy between 'new paid membership checkout is disabled' and 'no checkout is created at start,' but the two statements convey slightly different facts.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (14 parameters, no output schema), the description supplies the critical invocation-level context: beta constraints, endpoint_url conditionality, and access semantics. It could more explicitly describe the return value shape, but the schema's ownership_proof_url already hints at a returned proof body, and the description's 'redirect never grants access' covers the most safety-critical behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Parameter descriptions in the schema cover 100% of the 14 parameters, so the baseline is 3. The description adds some useful cross-parameter context, especially endpoint_url requirements by entry type)Skip payment policy, but it does not substantially deepen the meaning of parameters beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Start the real SaSame MCP Factory lifecycle' from one of seven canonical creator entry types. It clearly distinguishes this from checkout and membership tools by noting both that no checkout is created and that a redirect never grants access.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit context for when this tool is appropriate: during the beta, free and guided entries can start without payment, while live/underperforming/monitoring entries require endpoint_url. It also names the later-arrival alternative factory_provide_endpoint. However, it does not explicitly name checkout alternatives such as factory_checkout when payment is eventually required, so the when-not guidance is slightly implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SaSame MCP Observatory + Gold Rush Town tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

factory_start

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources