Verification CaseINTERNAL SELF TESTFINALIZED
case_msewosqi1
✓ Signature and content verified
This signature proves SaSame published this exact content, at this exact digest, and that it has not been altered since publication. It does NOT verify customer satisfaction, service quality, MCP safety, the truthfulness of everything the content asserts, or constitute a SaSame endorsement or certification.
Service & agreement
Service
https://live-vps.sasame.online/public-mcp
Payment state
NOT APPLICABLE
Started
Jul 19, 2026, 06:48 PM UTC
Completed
Aug 4, 2026, 06:06 PM UTC
Observation cycles
1511 (continuous health-checks, not fulfillment attempts)
Retries
not recorded by the source system
Reached continuous observation — the Factory's steady-state fulfilled outcome.
Reconstruction
Every claim below is classified fresh from the published evidence on every page load — never a stored verdict. Reconstructed Aug 4, 2026, 07:10 PM UTC.
service identityDIRECTLY VERIFIEDMatched a published evidence record for https://live-vps.sasame.online/public-mcp (evidence_record_id evr_d8f6f8b7-dd0e-4122-a1ab-c109b6969db2).
agreement priceUNAVAILABLECase does not record a quoted amount and currency.
execution timelineINFERREDCase reports 8 attempt(s), but the public bundle does not carry per-attempt timestamps to independently check chronological consistency.
observation cyclesDIRECTLY VERIFIED1511 continuous-observation cycle(s) recorded, distinct from one-time fulfillment-flow attempts — from 2026-07-19T18:48:32.852Z to 2026-08-04T18:06:53.851Z.
retry historyUNAVAILABLEThe source system did not record retry history for this case — this is a labeled gap, not a claim of zero retries.
artifactsUNAVAILABLECase records no artifacts.
outcomeDIRECTLY VERIFIEDCase claims FULFILLED and the linked evidence record's most recent observation is observed_callable.
Offline verification
This case's publication receipt is ed25519-signed with SaSame's trust-issuer key — the same key trust_pubkey and verify_mcp_certalready use. The raw signed envelope below is everything a third party needs to check the signature themselves, without trusting this website or SaSame's server to say "valid".
Receipt id
pub_d5851d68-a3e8-4573-9191-69636d2acc15
Subject digest (sha256)
81398f76f0ec9470d43fd354d2134cb7f7a41e05f2a9542742e48be180dcdd3a
Published
Aug 4, 2026, 06:08 PM UTC
Signed by
sasame-trust-302a300506032b65
Issuer public key (SPKI, hex)
302a300506032b6570032100439ce47d384c8ceb07c9040aef780cc3a2ba5a63c14027ad77ab458111f20fb6
Signature (base64)
ursgZJ4ytaK3T2RHhZkCQxvmNZwot0nwfP4isXgmjCAo0orMIJ0ywAGtnxAB4gBx3Gr60FOTdMD3gtylTweCAw==
To verify without calling SaSame at all: canonically JSON-serialize the receipt fields above minus signed_by and signature (plus receipt_sha256, included in the fetched record), UTF-8 encode it, and check it against the base64 signature using the SPKI-DER form of the issuer public key — standard ed25519 verification (e.g. Node's crypto.verify(null, message, publicKey, signature)). Or use the public MCP tools, which run the same check:
verification_case_bundle — fetch this exact record, including the raw receipt and issuer keyverification_case_verify — re-verify the signature and hash chain offlineverification_case_reconstruct — recompute every claim classification from scratch