SaSame operates one modular MCP Factory. Seven creator entry points join one lifecycle across 21 stations.

Does connecting the public MCP charge money?

No. Calling a public tool does not itself create a charge. Paid Factory memberships are available only when the canonical plan price_state is LIVE.

Does SaSame endorse MCP servers?

No. Observations and grades are measurement status, not endorsement, safety, quality or malware verdicts.

What should an MCP owner do first?

Open https://live-vps.sasame.online/start/ or connect https://live-vps.sasame.online/public-mcp and call audit_mcp with the public MCP URL. The baseline is free and does not create a charge, claim, or subscription. resolve_and_run remains available as supporting bounded routing.

Does SaSame execute every routed action?

No. plan_only never executes. safe_read_only executes only explicitly requested, conservatively read-only public tools with complete arguments. Payments, writes, deployments, accounts, DNS, wallets, legal commitments, and identity actions are not auto-executed.

When is a result complete?

Only the verified state is complete. planned, handoff_required, failed, refused, and no_route remain incomplete.

Where is the service available?

The public MCP targets AI agents, developers, MCP providers, and clients worldwide. English is the canonical machine language. SaSame SRL is the Romanian/EU operator; that is legal context, not a geographic restriction.

Worldwide · English canonical · MCP Streamable HTTP

Agents found your MCP. Why did they not call it?Get a reproducible activation baseline before choosing a repair or package.

Name: SaSame MCP Factory
Brand: SaSame

SaSame operates one modular MCP Factory — production, distribution, inspection, and continuous observation for Model Context Protocol servers — organized as 21 lifecycle stations with seven creator entry journeys. Protocol Observatory and MCP Owner Intelligence are permanent inspection and intake stations within the one Factory Lifecycle, not separate products.

For MCP owners, start with the free Factory audit and owner-controlled claim path: submit one public MCP URL, measure where agent selection stops, and enter the wider lifecycle only when the evidence justifies it.

Primary MCP-owner action · free baseline

https://live-vps.sasame.online/start/

Primary public-MCP tool: audit_mcp

{
  "url": "https://your-public-mcp.example/mcp"
}

Audit why agents do not call my MCP Connect public MCP Router manifest Agent card

Living Gate

SIGNALDay 44/30

external pulse: yes · decision 2026-07-17

External AI Reach

80487hits· 220 IPs

discovery / reach — NOT demand

Verified Services

0external· 3 total

external providers = 0; rest are SaSame's own

as of 2026-08-01 (offline fallback) · source: funnel.json · market.json

Supporting routing contract

For non-owner tasks: get a planned route, fallbacks, and an honest verified state.

Step 1

accept goal and constraints

Step 2

derive bounded capability terms

Step 3

find observed public candidates

Step 4

live-check the candidate MCP surface

Step 5

rank a primary route and fallbacks

Step 6

execute only when mode, arguments, annotations, and constraints allow it

Step 7

record planned, handoff_required, verified, failed, refused, or no_route

Step 8

append privacy-minimized outcome evidence

Outcome truth

Only verified means complete.

Plans, candidates, and handoffs remain incomplete by construction. This prevents a router from presenting discovery as delivery.

plannedcomplete: false

A route exists, but no downstream operation was executed.

handoff_requiredcomplete: false

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

verifiedcomplete: true

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

failedcomplete: false

Execution was attempted but did not produce a verified result.

refusedcomplete: false

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

no_routecomplete: false

No sufficiently relevant observed public capability was available.

Examples

Globally applicable goals.

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

Client configuration

Connect once.

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

The live endpoint reported 94 tools at 2026-08-01T22:01:19.625Z. The count is evidence, not a promise.

Supporting rails

The Observatory powers the activation baseline. The router and other rails remain available without becoming the commercial front door.

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

What the router will not imply or auto-run.

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.

Machine entrypoints

One product contract, multiple representations.

public_mcp router_manifest agent_card llms for_agents mcp_owner_intelligence_plans factory_public_contract observatory methodology readiness_index fresh_frontier live_data town public_repo factory_start

Operated by SaSame SRL in Romania / European Union. The target audience is worldwide; jurisdiction is legal context only.