Worldwide · English canonical · MCP Streamable HTTP

Connect AI. Choose capabilities. Let it work. Review what happened.

SaSame continuously observes and measures the Model Context Protocol ecosystem and publishes verifiable evidence and history, so people and AI agents can connect an AI, choose capabilities, act, and review what happened.

One user flow: connect an AI client, choose allowed capabilities, run public or authenticated MCP tools, and keep a clear record of what happened. SASAME S.R.L. is the external accountable operator; Pancho is its internal operating organism; the MCP Factory, Protocol Observatory, router, Account Control, CLI and website are internal production/execution machinery and an optional product surface behind that one evidence-first service — not separate products, and not the mandatory external identity for every context.

Four things to do

Connect an AI — Add SaSame to ChatGPT, Claude, Claude Code, or another MCP client.
Choose capabilities — Decide which tools, Missions, and account actions the AI may use.
Let it work through MCP — Call public tools for discovery and audits or authenticated tools for account operations.
Review what happened — Check usage, evidence, drafts, exports, and outcome state before treating anything as complete.

Use simple verbs

SaSame is easiest for agents to understand as actions: observe, audit, connect, start, choose, draft, and reset.

Observe

Read current public evidence about SaSame, MCP readiness, and known endpoints.

start_here

Audit

Measure one public MCP endpoint without an API key or payment method.

audit_mcp

Connect

Connect SaSame to ChatGPT, Claude, Claude Code, or another MCP client.

https://srl-sasame.com/documentation/connect

Start

Enter the Factory Lifecycle from an idea, build, live MCP, problem, or monitoring need.

factory_start

Run

Give SaSame a natural-language goal and let the authenticated Client MCP route it across enabled capabilities, executing only bounded read-only work it can verify.

sasame_run

Choose

Choose which authenticated capabilities and Missions an AI client can see.

capability_set

Complete

Complete one evidence-backed marketing deliverable and verify the deliverable itself; no external send or performance claim is implied.

marketing_mission_complete

Contact

Prepare one evidence-backed contact action for an explicit recipient, then close the contact step from the external provider receipt.

marketing_contact_prepare

Reset

Reset the free beta usage bucket while preserving lifetime usage history.

usage_reset

Free beta paths

Capability Control Beta is the current new-user path. No payment method is required for new users during beta.

public_mcp

Use SaSame without signing in.

https://live-vps.sasame.online/public-mcp

start_here, audit_mcp, factory_stations, factory_start, claim_start

knowledge_mcp_srl

Ask an agent to search or read the SaSame website through MCP.

https://srl-sasame.com/api/mcp

knowledge_search, knowledge_get

authenticated_client_mcp

Sign in once, approve MCP access, then use all default beta capabilities from the AI client. Start with sasame_run when you have an outcome rather than a preset workflow in mind.

https://live-sasame.sasame.online/mcp

sasame_run, session_info, account_status, capabilities_status, capability_set, usage_status, usage_reset, marketing_mission_start, marketing_mission_evidence, marketing_mission_draft, marketing_mission_complete, marketing_contact_prepare, marketing_contact_receipt, mcp_ecosystem_search, mcp_readiness_check, mcp_evidence_lookup, factory_dashboard, factory_export

Not the beta path: new paid Factory membership checkout · private-contact scraping · owner shell access · Client MCP custody of outbound provider credentials · automatic marketing bulk outreach

MCP surfaces

Public discovery/audit, site knowledge, and signed-in account operations are separate MCP surfaces. Use tools/list on the selected surface as the live callable truth.

Public MCP

Keyless discovery, observation, public audit, owner claim start and Factory lifecycle entry.

https://live-vps.sasame.online/public-mcp

auth: none

Knowledge MCP

Keyless search and retrieval of current public SaSame website knowledge.

https://srl-sasame.com/api/mcp

auth: none

Authenticated Client MCP

Signed-in goal-first operation surface for natural-language goals, capability settings, beta usage, Factory binding, exports, verified Marketing Mission deliverables, and provider-neutral external contact action/receipt handoff.

https://live-sasame.sasame.online/mcp

auth: OAuth account consent

Factory station, 21 stations, 7 creator entry journeys

One Factory Lifecycle: the creator's entry station is determined by the product's state, not by buying a separate service. Creators keep ownership of the product, repository, code, data and API rights, credentials, and actual repair. The live station catalog and availability come from factory_stations and factory_health on the public MCP; static copy never promises per-station availability.

Creator entry states: idea; blueprint; unfinished build; finished build; live MCP; underperforming MCP; portfolio monitoring. Enter with factory_start; read the live station catalog with factory_stations.

Start here

MCP owners: start with free Factory audit and owner claim. Run a free point-in-time MCP audit, then optionally prove endpoint control with the free owner claim. Neither action charges, creates a subscription, or changes the measured readiness result. Register an account or enter a paid Factory lifecycle only when the creator explicitly chooses to continue.

Agents and developers: connect the public MCP (no API key): https://live-vps.sasame.online/public-mcp

Call audit_mcp, claim_start, observation_trajectory, factory_start for free inspection, owner claim, longitudinal evidence, or Factory lifecycle entry. resolve_and_run is supporting routing infrastructure:

{
  "goal": "Describe the outcome you need",
  "environment": "your client or runtime",
  "constraints": [
    "read only",
    "free only"
  ],
  "execution_mode": "plan_only"
}

Use plan_only for routing without execution. Use safe_read_only only for an explicitly requested read-only call with complete arguments.

What happens after a goal arrives

accept goal and constraints
derive bounded capability terms
find observed public candidates
live-check the candidate MCP surface
rank a primary route and fallbacks
execute only when mode, arguments, annotations, and constraints allow it
record planned, handoff_required, verified, failed, refused, or no_route
append privacy-minimized outcome evidence

Outcome states

`planned`

A route exists, but no downstream operation was executed.

complete: false

`handoff_required`

A route exists, but authorization, required arguments, or a human/owner action is still needed.

complete: false

`verified`

A permitted downstream call returned substantive output and passed the router's verification contract.

complete: true

`failed`

Execution was attempted but did not produce a verified result.

complete: false

`refused`

The request violated a safety, credential, payment, mutation, or input boundary.

complete: false

`no_route`

No sufficiently relevant observed public capability was available.

complete: false

Only verified is complete. Plans and handoffs remain incomplete by construction.

Examples from anywhere

Search GitHub issues related to an authentication bug
github · read only · free only
Find recent biomedical evidence about a treatment question
pubmed · read only
Extract text from a public screenshot
ocr · read only · no credentials
Check whether a public MCP endpoint is callable before connecting it
mcp readiness · measurement only
Research a topic using multiple public sources
research · read only · include evidence

Product posture

protocol_observatory

Permanent Factory inspection and observation station

Current and longitudinal observations used to inspect public MCP and agent-protocol implementations.

mcp_owner_intelligence

Factory readiness and intake station

Owner-facing inspection, claim, lifecycle and monitoring entry inside the one Factory. Plan names, prices and entitlements come only from the canonical Factory commercial contract.

agent_execution_router

Factory routing/entry surface into the Lifecycle

Bounded public capability routing; not the primary commercial product.

receipts_and_town

Factory station (Gold Rush Town) and supporting evidence modules

Privacy-minimized work records, non-custodial settlement evidence, and Gold Rush Town — a Factory station for public demonstration and engagement. These do not replace the Protocol Observatory or MCP Owner Intelligence stations.

Hard boundaries

Public observations and grades are measurement status, not endorsement, safety, quality, malware, KYC, identity, sanctions, or legal-authority verdicts.
A plan, candidate route, or handoff is never reported as executed or verified.
The public router does not accept credential-like endpoint data or secret-like arguments.
AI agents execute autonomously by default inside honest, logged, verify-or-rollback envelopes. No act is owner-required. Exposing owner shell or file tools publicly, spam, impersonation, anti-bot evasion, and committing secrets are prohibited (decision SASAME-2026-07-19-AUTONOMY-SAFETY-RAILS).
SaSame is non-custodial and does not hold or move third-party funds.
Agent-work records are evidence statements, not fiscal or tax invoices.
tools/list and the live health contract are authoritative for the current callable surface; static copy never promises a fixed tool count.
Public MCP and authenticated client MCP are separate surfaces: public calls are keyless and free, while account settings and beta usage mutations require OAuth account consent and the caller's organization role.

Connect from an MCP client

{
  "mcpServers": {
    "sasame": {
      "type": "http",
      "url": "https://live-vps.sasame.online/public-mcp"
    }
  }
}

Machine entrypoints

Operator: SASAME S.R.L. (Romania / European Union). The service targets agents and developers worldwide; the operator jurisdiction is legal context only.