SaSameFor people and AI systems
liveFactory stationsigned evidence

Observe the MCP ecosystem without turning measurement into endorsement.

Protocol Observatory is the inspection and longitudinal-evidence station inside the SaSame institution and its mature Factory capability surface. This Knowledge page owns the human experience; the existing live-vps runtime continues to own signed feeds, indexes, badges, certificates and lookup endpoints.

Domains graded
60,970
Observed-ready
8,552
Observation snapshot
Oct 4, 2026, 11:25 PM UTC
Business role
Factory station
Pending observation
67
Census snapshot size
30,000

Census, Observatory and the operations summary update on independent schedules: currently 20,948 server(s) of cross-artifact lag (operations summary as of Oct 4, 2026, 10:10 PM UTC, Observatory as of Oct 4, 2026, 10:21 PM UTC) — normal pending sync, not an outage.

Data freshness: STALE — older than expected: observation_history, funnel (oldest as of Aug 27, 2026, 08:10 AM UTC). This reflects each source's own last-write time, not merely when this page's data was regenerated.

Boundary

Observed means measured from outside. Claimed means an operator proved control. Neither state means safe, recommended, high quality or legally verified. Unknown remains unknown, and unavailable live data is never replaced with invented values.

01Server directorySearch the current readiness index and open bounded observation details.02MethodologySee exactly what is measured, what is excluded and how unknowns are handled.03State of MCPRead the current attack-surface and annotation findings with their caveats.04Runtime reliabilityCite observed-ready evidence without turning it into an uptime or ranking claim.05Tool annotationsUse the deterministic annotation capsule and raw attack-surface evidence.06Agent discoverabilitySeparate enumerable tool surfaces from ranking, citation, adoption or revenue.
OP

Operations evidence

Canonical public telemetry is embedded here as evidence, not as a separate dashboard or product identity. Reach, engagement, use, intent, checkout, payment, fulfillment and the current North Star remain distinct evidence stages; missing or stale evidence stays UNKNOWN.

MCP servers graded
39,996
Observed-ready (A/B)
8,522
External MCP use · 7d
163
Organic settled trading volume
UNKNOWN
Launch/history milestone: first organic paid revenue = 0. This is external-demand evidence only; the permanent Exchange North Star is organic settled trading volume, and this legacy operations source does not provide that metric.
Canonical evidence ladder

7d · Sep 27, 2026, 08:10 PM UTC → Oct 4, 2026, 08:10 PM UTC

MEASUREMENT_INCOMPLETE. Affected stages remain UNKNOWN. checkout_source_missing
Technical stage evidence8 stages · sources, freshness and actor scope
StageValueSourceEvidenceFreshness / as ofActor scope
Reach8,692intent funnelOBSERVEDFRESH · Oct 4, 2026, 08:10 PM UTCexternal nonself identity unverified
Engage8,529intent funnelOBSERVEDFRESH · Oct 4, 2026, 08:10 PM UTCexternal nonself identity unverified
Use163intent funnelOBSERVEDFRESH · Oct 4, 2026, 08:10 PM UTCexternal nonself identity unverified
Intent2intent funnelOBSERVEDFRESH · Oct 4, 2026, 08:10 PM UTCexternal nonself probe validator excluded identity unverified
CheckoutUNKNOWNrevenue funnelUNKNOWNUNKNOWNcheckout actor identity unverified
Paid0paid revenue ledgerOBSERVEDEVENT_DRIVEN · Jul 14, 2026, 06:10 PM UTCindependent external only
Fulfilled0paid revenue ledgerOBSERVEDEVENT_DRIVEN · Jul 14, 2026, 06:10 PM UTCindependent external only
North Star0paid revenue ledger foldOBSERVEDEVENT_DRIVEN · Jul 14, 2026, 06:10 PM UTCverified customer

Actor evidence for this same window. UNKNOWN is preserved where identity-safe promotion is unsupported:

  • owner self · UNKNOWNUNKNOWN
  • synthetic test fixture · UNKNOWNUNKNOWN
  • known bot · OBSERVED97 distinct source hashes
  • known ai agent · UNKNOWNUNKNOWN
  • unknown external · OBSERVED143 distinct source hashes
  • authenticated principal · UNKNOWNUNKNOWN
  • verified customer · OBSERVED0 qualified customers
External MCP tool calls
050100
83tool calls on Oct 4
Qualified buyer-shaped actions
011
1intent events on Oct 4
Identity boundary: unknown_external is not human, authenticated principal, or customer; promotion requires stronger evidence. Self/test/fixture and known crawler activity receives zero demand/revenue credit; known AI-agent activity is not automatically a customer.
Supporting external reach
010,00020,000
4,221hits on Oct 3
Readiness census activity
05,00010,000
7,086observations on Oct 3
Readiness grade distribution · 39,996 observed records

Grade D is a mechanical observation state, not a customer or safety verdict:

  • C1 Protocol entry conformance29,070 · 94%
  • C2 Tool listability1,939 · 6%
Measurement source coverageTechnical source status and freshness
  • intent funnelfresh / FRESH · Oct 4, 2026, 08:10 PM UTC
  • revenue funnelmissing / UNKNOWN
  • paid revenue ledgeravailable / EVENT_DRIVEN · Jul 14, 2026, 06:10 PM UTC
  • websiteprojection_not_yet_correlated / UNKNOWN — Website events may exist in the existing analytics collector, but no identity-safe common-window join is asserted here.
  • account controlprojection_not_yet_correlated / UNKNOWN — Authenticated usage remains in the existing Account Control ledger; no public account identifier is exposed or inferred.
  • factorycovered_by_existing_rails / EVENT_DRIVEN — Factory/fulfillment evidence is consumed only through existing canonical receipt/revenue rails.
  • stripecovered_by_paid_revenue_ledger / EVENT_DRIVEN — No traffic or tool event can create Stripe/payment truth.
Historical boundary: The former Living Gate funnel is retained in its own artifact for history and is never mixed into current Mission Control KPIs.
LV

Try it live, no LLM involved

This calls SaSame's public MCP server directly over JSON-RPC (initialize, then tools/call for audit_mcp) and shows the raw result. No chatbot in the loop, no API key required.

01

Current observable tool surface

Full report

49.6% of state-changing tools on the enumerable surface publish NO machine-readable safety annotation — a calling agent cannot automatically tell a read from a write, delete, or payment before invoking them.

Endpoints observed
61,017
Handshake response
10,744
Declared tools
153,358
Annotated
33.6%

Deterministic classifier, no LLM. This describes the published tool surface and annotation hygiene. It is not proof of runtime behavior, a vulnerability finding or a safety verdict.

03

Observation and control status

Certified records
3
Third-party certified
2
Monitored
3
Meaning
bounded evidence

1) Claim your endpoint for free (https://github.com/shigeki7777/sasame-mcp-observatory/issues/new?template=claim-passport.yml) by proving control via .well-known / DNS / repo. 2) SaSame re-audits hourly. 3) After >= 2 reproducible cycles still at the A/B bar, it is auto-promoted to Certified. No fee, no application, no sales call.

A claim proves control of a record or endpoint only. It is not KYC, identity verification, endorsement or a general certification of safety.

04

Citation and reuse guidance

When reusing an Observatory finding in search, generated answers, reports or software, cite the specific human page together with the corresponding raw evidence URL below. Include the source-declared observation or generation time and preserve the stated measurement caveat so a dated observation is not presented as a timeless fact.

These machine-readable files improve reproducibility and attribution; they do not guarantee indexing, ranking or citation by any search or AI system.

RF

Stable machine evidence

The human interface can evolve without breaking externally referenced evidence URLs. Raw feeds remain on the dedicated runtime origin.