A Registry Entry Is Not Runtime Identity
Why should operators avoid treating registry metadata as runtime identity?
Because metadata can persist while deployments, domains, repositories and capability surfaces change independently.
Search the graph
Find current SaSame knowledge.
Current company, Factory, documentation, research, evidence, product and API records are searched by default. Historical records are available only when you explicitly include them.
Refine
Collections
Current records onlyRetired initiatives are excluded from normal search results.
Include historical recordsResults
All68 knowledge records
About SaSame
What kind of company is SaSame?
SaSame is an owner-governed, AI-operated company; SASAME S.R.L. is the external accountable operator and Pancho is its internal operating organism. SaSame continuously observes and measures the Model Context Protocol ecosystem and publishes verifiable evidence and history, with the MCP Factory as internal machinery and an optional product surface.
Advanced Learning Path
What does advanced MCP evidence work involve?
Advanced work combines longitudinal change detection, conformance boundaries, identity resolution and repair/reverification.
Agent Execution Router
How does an AI agent use SaSame to accomplish a task, not just register an MCP?
Call resolve_and_run on the same public MCP endpoint with a goal, environment and constraints; it returns a bounded route and an honest execution state — only "verified" means something actually ran.
API
How can software and AI systems retrieve SaSame knowledge?
Use the read-only Knowledge API, search endpoint or MCP retrieval tools, all backed by the same document and relation model.
Architecture
How is the SaSame Knowledge Platform structured?
One canonical Knowledge Database feeds the website, search, API, MCP, Markdown projections and future PDF outputs through versioned adapters.
Assisted Review
Can Assisted Review be purchased now?
No. Assisted Review has an approved €99 one-time price, but it isn't on sale yet — we haven't finished building a clear, working process for what happens right after payment, so we won't sell it until that's ready.
Beginner Learning Path
What should a beginner learn first about MCP?
Start with clients, servers, tools and endpoints, then learn why registry metadata and runtime behavior are separate evidence layers.
Blog
What is published on the SaSame blog?
The blog publishes technical explanations, implementation notes and evidence interpretation, not generic sales articles.
Brand
What does the SaSame brand represent?
The SaSame brand represents SASAME S.R.L.'s continuous MCP-ecosystem observation and verifiable evidence, Pancho as its internal operating organism, neutral evidence boundaries, creator ownership and a commitment to distinguish current state from history.
Capabilities
How do HOCR and the Factory relate to capabilities?
HOCR now routes CP2 Mission survivors through the smallest sufficient capability surface: deterministic rules or compiled Recipes first, selective LLM escalation only when novelty, uncertainty, risk or explicit Research requirements justify it.
Commercial Integrity
When is a SaSame plan honestly purchasable?
A paid plan only ever goes on sale once it passes every one of these checks: real payment is set up (not just an approved price), the checkout and legal terms are current, and we've actually verified what happens after someone pays.
Company
What is SaSame?
SaSame is an MCP-native AI execution service: connect an AI, choose what it may use, let it work through MCP, and review what happened.
Compatibility Evidence
What does MCP compatibility evidence mean?
It means a stated client or protocol check passed or failed under a defined method at a defined time.
Connect a Generic MCP Client
How do I connect SaSame to another MCP client?
Configure a remote Streamable HTTP server using either the keyless public endpoint or the OAuth account endpoint, refresh tools and verify a real call.
Connect an AI Client
How do I connect SaSame to an AI client?
Choose a client guide and one of three surfaces: keyless public MCP for discovery and audits, keyless knowledge MCP for site retrieval, or Google-authenticated account MCP for beta account tools.
Connect ChatGPT
How do I connect the SaSame MCP to ChatGPT?
Create a custom MCP app using either the keyless public endpoint or the Google-authenticated account endpoint, scan tools, enable the app and verify a real call.
Connect Claude
How do I connect the SaSame MCP to Claude?
Add either the keyless public URL or the Google-authenticated account URL as a remote custom connector, connect it, enable it and verify a real tool call.
Connect Claude Code
How do I connect the SaSame MCP to Claude Code?
Register either the public or authenticated Streamable HTTP endpoint, confirm it in the MCP list, complete OAuth when required and verify a real tool call.
Contact
How should someone contact SaSame?
Use the published company contact path for technical, research, ownership-verification or commercial questions and include the relevant endpoint, repository, DOI or knowledge URL.
Deployment
How are SaSame components deployed safely?
Deployments bind an immutable source SHA to a component release, health checks, external verification and a rollback target before traffic changes.
Documentation
Where should I start with SaSame?
Start with Getting Started, then follow Architecture, Factory, Monitoring, Owner Verification, Observatory, Deployment, Reference and API.
Evidence
What does SaSame evidence prove?
Evidence now includes the CP3 receipt chain: Factory Orders executed selected Mission survivors through registered stations and returned inspection/observation receipts without creating payment, demand or North-Star credit.
Evolution Loop
How does SaSame improve its own evolution method?
SaSame evolves by converting both successful execution and operational residue into knowledge: CP5 makes cleanup, dependency hygiene and test drift part of the same inherited learning loop.
Expert Learning Path
What defines expert MCP lifecycle architecture?
Expert work integrates governance, multi-component releases, evidence quality, commercial fulfillment and machine retrieval without parallel sources of truth.
Factory
How does the SaSame MCP Factory lifecycle work?
The Factory connects entry, blueprint, build, inspection, shipment, observation, repair and reverification through one evidence-backed lifecycle.
Factory
What is the Factory plan?
Factory is €9 per month. New membership checkout is disabled during Capability Control Beta — existing subscribers retain full access. Plan details remain unchanged; new checkout re-opens when the beta period ends.
Factory Pro
What is the Factory Pro plan?
Factory Pro is €29 per month. New membership checkout is disabled during Capability Control Beta — existing subscribers retain full access. Plan details remain unchanged; new checkout re-opens when the beta period ends.
Factory Team
What is the Factory Team plan?
Factory Team is €79 per month. New membership checkout is disabled during Capability Control Beta — existing subscribers retain full access. Plan details remain unchanged; new checkout re-opens when the beta period ends.
FAQ
What should users know before using SaSame?
Creators retain ownership, observations are bounded evidence, public MCP calls do not charge money, and only LIVE plans with verified fulfillment are purchasable.
Founder Role
What role does the founder play in SaSame?
The founder is represented publicly as the non-identifying owner_principal who defines purpose, doctrine, strategic priorities and exceptional human decisions while AI executors operate within recorded rails.
Free Listing
What is included in Free Listing?
Free Listing is €0 and available now: register and claim as many already-live MCPs as you like, with best-effort observation — no checkout, no card and no account required.
Getting Started
How do I begin using the SaSame MCP Factory?
Identify your MCP state, select the matching Factory entry point, then collect a reproducible baseline before changing anything.
Gold Rush Town
What is Gold Rush Town?
Gold Rush Town is a live, walkable 3D visualization of the Factory's real Observatory data — a public demonstration station, not a separate product or a second company identity.
Guided Build
How does BYO-LLM Guided Build actually work, step by step?
The creator's own LLM does the building from fixed instructions SaSame serves; SaSame runs zero LLM calls and deterministically verifies the artifacts the creator submits back — string/regex/length checks, never a fuzzy AI judgment.
History
Why does SaSame preserve unsuccessful or superseded work?
Preserving prior work makes the current system auditable and prevents repeated reinvention, while lifecycle labels keep old ideas from being presented as active.
Incident Reports
What belongs in a SaSame incident report?
An incident report records impact, detection, timeline, affected components, evidence, containment, recovery, verification and unresolved risk.
Intermediate Learning Path
What should an intermediate MCP operator understand?
Intermediate operators need deployment, authentication, monitoring, owner verification and reproducible failure handling.
Knowledge Publishing Workflow
How do documents enter the SaSame Knowledge Platform?
Documents enter through reviewed CMS edits, provider-neutral AI drafts or controlled migrations, then pass validation, CAS versioning, Markdown projection and receipt generation before public release.
Learning
How can I learn MCP concepts from beginner to expert?
Use progressive tracks: beginner concepts, intermediate operations, advanced evidence and expert lifecycle architecture.
mcp-readiness CLI
Is there a command-line tool to check an MCP server’s readiness?
mcp-readiness is SaSame’s open-source command-line tool: run it with npx against any public MCP endpoint to get the same bounded readiness grade the Observatory publishes, with no account or key required.
Mission
What is SaSame trying to accomplish?
SaSame aims to make MCP production and operation reproducible, observable and evidence-backed while creators retain ownership of code, credentials, data rights and support.
Mission Control
What does Mission Control manage?
Mission Control is the homeostasis surface for the SaSame ecosystem: it can represent Mission populations, deterministic launch/kill/complete transitions, closeout knowledge inheritance, successor Missions and read-only portfolio capacity without turning a killed business shape into a company pivot.
Monitoring
What does Factory monitoring measure?
Monitoring records time-bounded reachability, protocol behavior, declared capabilities and selected compatibility checks with provenance and history.
Observatory
How does the human Observatory experience relate to the evidence runtime?
The Knowledge Platform is the canonical human interface for the Observatory Factory station, while live-vps preserves signed JSON, feeds, badges, certificates, lookup and longitudinal evidence URLs.
Owner Verification
What does owner verification prove?
Owner verification proves control of a defined MCP identity or related resource through a bounded control-proof method at a stated time.
Philosophy
What does SaSame actually believe, independent of any current product?
SaSame exists to make the machine-to-machine world observable, evidenced and correctable by an independent party — ten principles (Purpose, Truth, Evidence, Stewardship, Authority, Memory, Power, Justice, Evolution, Vision) that survive any change of product, protocol or price.
Press
What should press and analysts cite about SaSame?
Press should cite the current Factory definition, primary research records, exact DOI pages and dated evidence rather than inferred traction or superseded positioning.
Pricing
What is the current acquisition path for SaSame?
Capability Control Beta is the current new-user path: sign in, connect an AI client, choose capabilities, use them — no payment required for new users during beta. New paid Factory membership checkout is disabled; Free Listing remains available. Existing subscribers retain all entitlements, renewals and webhooks. CP4 keeps North-Star accounting strict: only independent LIVE payment plus exact verified fulfillment can count; checkout starts, tests, crawler signals and synthetic replays never count.
Privacy Policy
What is SaSame's privacy policy?
SaSame SRL (Romania, EU) collects only what's needed to respond to inquiries and operate the Factory service you use; Google Analytics stays off until you explicitly accept it, and the traffic beacon never stores a raw IP.
Products
What does SaSame currently offer?
SaSame is operated externally by SASAME S.R.L. as an accountable software and AI company. Its primary public service is continuous MCP-ecosystem observation, measurement and verifiable evidence; the SaSame MCP Factory is the standardized product surface when Factory access itself is offered. Scaling any commercial offer remains bounded by independent demand evidence.
Reference
Where are exact SaSame schemas and lifecycle states defined?
Reference pages expose versioned schemas, status enums, API contracts, evidence boundaries and release receipt fields used across human and machine interfaces.
Registry and Runtime Evidence
Why are registry and runtime records separate?
A registry record describes a declared identity or capability; runtime evidence records what an endpoint returned when observed.
Registry-Runtime Gap
What is the registry-runtime gap in MCP?
Registry presence and declared metadata do not guarantee that an MCP endpoint is reachable, interoperable or behaving as described at observation time.
Repair and Reverification
When a shipped MCP breaks, what happens and who fixes it?
Observation detects drift and produces a scoped Repair Blueprint with hypotheses, not confirmed causes; the creator always applies the actual fix; SaSame never edits creator code; a successful fix is reverified under the same test contract and automatically reshipped.
Research
What research does SaSame publish?
SaSame Research now has an executable CP2 loop: it generates structurally diverse hypotheses, runs adversarial falsification and epistemic-state gates, simulates candidates at multiple fidelities, and emits only bounded Mission candidates before reality exposure.
Research Datasets
What must a SaSame research dataset disclose?
A dataset discloses provenance, collection window, identity keys, fields, exclusions, license and privacy boundaries.
Research Measurements
How should MCP measurements be interpreted?
Measurements are bounded results tied to an instrument, target identity, time and denominator; they are not timeless ratings.
Research Methodology
How does SaSame define reproducible MCP research?
Research records population, observation window, identity assumptions, instruments, exclusions, transformations, retained evidence and known mismatches.
SaSame
What is SaSame and where should I begin?
SaSame is agent-native Information Asset Exchange infrastructure: the public website exposes market state and evidence for inspection, while AI agents execute through MCP and API rather than a browser trading workflow.
Search
How does Knowledge Platform search work?
Search ranks title and slug matches, then tags, categories, short answers and detailed content while preserving locale and lifecycle status.
Self-Evolution Loop
What is SaSame becoming?
SaSame's self-evolution loop (operated by SASAME S.R.L., with the MCP Factory as internal machinery) treats executor residue, parked Issues, dependency PRs and stale worktrees as first-class loop inputs that must be absorbed, preserved, archived or scheduled.
Standing
What is SaSame's actual track record?
SaSame SRL is a new Romania/EU micro-studio (CUI 50731520) with no track record and no paying clients yet. No team headshots, no founding myth, no client logos — this page states that plainly rather than hiding it.
Start
How do I start using SaSame?
Connect an AI, choose what it may use, let it work through MCP, and review what happened. Start with the free path: audit a public MCP, connect an AI client, start a Marketing Mission, or run the local CLI.
Terms of Service
What are SaSame's terms of service?
The public MCP server and tools are provided "as is", free during Early Access with no account required; a readiness audit or certificate is a measured fact, never a security audit or endorsement.
Timeline
How should SaSame history be read?
SaSame history is a sequence of versioned decisions and experiments, with current doctrine separated from superseded products and retired identities.
Vision
What is the long-term vision for SaSame?
The vision is a durable MCP knowledge and execution layer where creators, operators and AI systems can inspect the same lifecycle state and evidence.
Factory fulfillment verification — https://live-vps.sasame.online/public-mcp
https://live-vps.sasame.online/public-mcp