SaSame MCP Observatory + Gold Rush Town
REMOTE · LIVE-VPS.SASAME.ONLINE · SCANNED SEP 20
No-key MCP: audit/certify MCPs, signed trust history; join Gold Rush Town & build with your LLM.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 58 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 13397 tokens (~141/item across 95 items; 95 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 72% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 96 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the SaSame MCP Observatory + Gold Rush Town server?
SaSame MCP Observatory + Gold Rush Town is a hosted endpoint at https://live-vps.sasame.online/public-mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · live-vps.sasame.online
claude mcp add --transport http online-sasame-research 'https://live-vps.sasame.online/public-mcp'
{
"mcpServers": {
"online-sasame-research": {
"url": "https://live-vps.sasame.online/public-mcp"
}
}
} {
"servers": {
"online-sasame-research": {
"type": "http",
"url": "https://live-vps.sasame.online/public-mcp"
}
}
} [mcp_servers.online-sasame-research] url = "https://live-vps.sasame.online/public-mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"online-sasame-research": {
"type": "remote",
"url": "https://live-vps.sasame.online/public-mcp",
"enabled": true
}
}
} openclaw mcp add online-sasame-research --url 'https://live-vps.sasame.online/public-mcp' --transport streamable-http
mcp_servers:
online-sasame-research:
url: "https://live-vps.sasame.online/public-mcp" {
"McpServers": {
"online-sasame-research": {
"Transport": "http",
"Url": "https://live-vps.sasame.online/public-mcp"
}
}
} assistant mcp add online-sasame-research -t streamable-http -u 'https://live-vps.sasame.online/public-mcp'
{
"mcpServers": {
"online-sasame-research": {
"type": "http",
"url": "https://live-vps.sasame.online/public-mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 0
- New tool “information_paid_access_listings” functional
- 28 Aug 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “agent_invoice_status” rewrote its description, which is the text the model reads security
- Tool “audit_mcp” rewrote its description, which is the text the model reads security
- Tool “lookup_readiness” rewrote its description, which is the text the model reads security
- Tool “provenance_passport_spec” rewrote its description, which is the text the model reads security
- Tool “provenance_verify_passport” rewrote its description, which is the text the model reads security
- Tool “recommend_mcp” rewrote its description, which is the text the model reads security
- Tool “start_here” rewrote its description, which is the text the model reads security
- Tool “verify_mcp_ready” rewrote its description, which is the text the model reads security
- Tool “work_order_open” rewrote its description, which is the text the model reads security
- 27 Aug 26 0
- Tool “lookup_readiness” rewrote its description, which is the text the model reads security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- Tool “factory_start” rewrote its description, which is the text the model reads security
- Tool “start_here” rewrote its description, which is the text the model reads security
- “factory_start” reworded the description of “principal_id” cosmetic
- “factory_start” reworded the description of “principal_key” cosmetic
- 24 Aug 26 0
- Tool “factory_membership_checkout” rewrote its description, which is the text the model reads security
- “factory_membership_checkout” reworded the description of “stripe_live_payment_acknowledged” cosmetic
- “factory_membership_checkout” made “stripe_live_payment_acknowledged” optional cosmetic
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Aug 26 0
- “factory_membership_checkout” added an optional parameter “affiliate_referral_id” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://live-vps.sasame.online/public-mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.sasame.online | CN=YE1,O=Let's Encrypt,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 60218fe3e8a265b1e73cd502354ab135d7a |
| SANs: api.sasame.online, chatgpt-vps-mcp.sasame.online, live-fx.sasame.online, live-sasame.sasame.online, live-vps.sasame.online, mcp.sasame.online, portal-mcp.sasame.online, vps-mcp.sasame.online | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of live-vps.sasame.online. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| online. | present | 30961 | 13 | Verified |
| sasame.online. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://live-vps.sasame.online/public-mcp | Verified | 200 | |
| http (plaintext) | http://live-vps.sasame.online/public-mcp | HTTPS enforced | 301 | https://live-vps.sasame.online/public-mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agent_invoice_attest_settlement ~124
Buyer or provider signs a settlement statement for an issued agent transaction receipt. SaSame records each statement. Only matching statements from BOTH pinned party keys produce a signed `settled_reported_by_both` receipt. SaSame does not move funds or independently verify off-chain settlement; use a chain/processor receipt as settlement_ref when available.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | yes | – |
| settlement_ref | string | yes | Transaction hash, processor receipt id or other non-secret settlement reference |
| signature_base64 | string | yes | – |
| work_order_id | string | yes | – |
No output schema declared.
No examples provided.
agent_invoice_issue ~144
Issue a SaSame SRL-signed THIRD-PARTY AGENT TRANSACTION RECEIPT after provider delivery. The legacy tool name is retained for API compatibility: this is a transaction-confirmation receipt, not a fiscal/tax invoice. The provider signs provider_receipt_challenge (identical to the legacy provider_invoice_challenge). The receipt binds mutually accepted terms, delivery and amount. If SaSame SRL itself sells a service, its separate accounting rail issues the normal SaSame SRL business invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| external_invoice_ref | string | – | Optional provider-side invoice/reference number |
| signature_base64 | string | yes | – |
| work_order_id | string | yes | – |
No output schema declared.
No examples provided.
agent_invoice_status ~132
Read the privacy-minimized state of an agent transaction receipt/work order and receive a SaSame-signed current statement. SaSame, operated by SASAME S.R.L., continuously observes and measures the Model Context Protocol ecosystem and publishes verifiable evidence and history; the MCP Factory is internal machinery and an optional product surface behind it; measurement only, not endorsement. Raw scope/deliverables are never stored; only their SHA-256 commitments, public labels, signatures and state transitions are retained. The legacy tool name is retained for compatibility; this is not a fiscal invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| work_order_id | string | yes | – |
No output schema declared.
No examples provided.
analytics_next_steps ~43
Return public next-step links for MCP Passport claim, interest, plans, and monitoring paths. Read-only; no external action is triggered.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | – |
No output schema declared.
No examples provided.
analytics_public_export ~22
Return the public aggregate analytics export manifest. No private owner analytics.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
analytics_public_summary ~53
Read the public outside-in Analytics summary. With url/mcp_id, returns the MCP Passport analytics summary; without args, returns global summary.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_id | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
audit_mcp ~420
Grade one MCP server A-D against the Agent-Tool Discoverability Standard. SaSame, operated by SASAME S.R.L., continuously observes and measures the Model Context Protocol ecosystem and publishes verifiable evidence and history; the MCP Factory is internal machinery and an optional product surface behind it; measurement only, not endorsement. Runs the legitimate revision-aware MCP protocol entry (server/discover with legacy initialize fallback), tools/list, and one read-only tool call over POST JSON-RPC. It returns the grade, a per-criterion pass/evidence breakdown, and the single biggest gap to fix. This returns the grade and analysis ONLY — if you want a signed, portable certificate of the same audit, use verify_mcp_ready instead. DIRECTORY PRE-FLIGHT: these criteria cover the MECHANICAL reject reasons of the Claude Connectors Directory and ChatGPT Apps Directory (annotations, typed schemas, description clarity, liveness, graceful errors, anti-ghost) — run it before you submit. It does NOT cover privacy-policy, identity/business verification, OAuth callbacks, or prohibited-category rules; it catches mechanical failures, it does not guarantee a pass. SECURITY SIGNALS (advisory, never a verdict): plain-HTTP exposure, redirect count, Server/X-Powered-By header disclosure, stack-trace-shaped text in error responses (zero extra cost — read from responses already fetched), plus two bounded best-effort checks — RFC 9728 OAuth protected-resource metadata and TLS certificate expiry/trust-chain status. CAPABILITY SIGNALS (advisory, never graded): resources/list and prompts/list support (OPTIONAL per the MCP spec — their absence is not a defect), tools/list pagination, and the raw capabilities the server declared. Protocol inspection only — no auth-bypass, no payment. Free. Best run against YOUR OWN server. (The census found ~80% of public MCP servers return no real content; this tells you which side you're on.)
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The MCP server endpoint URL (https) to audit — ideally your own |
No output schema declared.
No examples provided.
audit_query ~141
Query SaSame's append-only audit log (meters, receipts, escrow statements, and Agent Work Ledger transitions). Read-only: an empty log returns 0, never fabricated activity. Filter by meter_id, agent_id, kind, or since (ISO timestamp). Use to reconstruct what SaSame recorded; party labels are not legal identities and recorded statements are not independent proof that underlying work or payment occurred.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| kind | string | – | e.g. meter_charge / meter_reject / receipt_issue |
| limit | integer | – | – |
| meter_id | string | – | – |
| since | string | – | ISO timestamp lower bound |
No output schema declared.
No examples provided.
capability_landscape ~136
Zero-argument ecosystem view: SaSame's live 'State of the Agent Attack Surface' — how large the public MCP attack surface is, which capability classes it exposes (payment / code-execution / credential / write / send / fetch / read), and what share of state-changing tools ship with NO machine-readable safety annotation. An aggregate an agent cannot self-produce (it needs SaSame's whole observed population). ed25519-signed, offline-verifiable. OBSERVATION of the declared surface — not a safety, malware, or trust verdict. A frictionless first call: no URL needed. Cost-zero, observed level.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
capability_profile ~191
DEFENSIVE pre-call check for one public MCP server: SaSame classifies its DECLARED tool surface (published tools/list) into capability-risk classes (code-execution / payment / credential / write / send / outbound-fetch / read), flags state-changing tools that publish NO machine-readable safety annotation (so a caller cannot auto-distinguish a read from a write/delete/payment before invoking), gives an exposure tier, and — the part an agent cannot self-produce — which higher-risk capability classes this server NEWLY exposed since SaSame first observed it. ed25519-signed, offline-verifiable. This is an OBSERVATION of the declared surface, NOT a vulnerability/malware scan and NOT a claim the server is unsafe. Use it before wiring an untrusted MCP into an agent. Cost-zero, observed level.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The MCP server endpoint URL (https) to profile |
No output schema declared.
No examples provided.
chain_list ~20
List saved chain recipes (name, description, step count).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_engagement ~146
Poll the status of an engagement you opened with engage_sasame, and READ the human operator's reply — entirely over MCP, no email needed. Pass the `ticket` you got back from engage_sasame. Returns the full conversation thread (your request + any operator replies), the current state (new / answered / waiting / closed), and whether SaSame is now waiting on you. Call this again periodically (e.g. once a day) to pick up the operator's response. Free, read-only, deterministic — no LLM, no network.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket | string | yes | The engagement ticket returned by engage_sasame (e.g. 'inq_...'). |
No output schema declared.
No examples provided.
chronicle_summary ~24
Return the public MCP Gold Rush Chronicle teaser. Detailed intelligence is paid/private.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
claim_confirm ~122
Confirm your domain-control proof and upgrade your SaSame MCP Observatory listing from Observed to CLAIMED. SaSame fetches /.well-known/mcp-ready-claim.txt (or checks the DNS TXT _mcp-ready-claim.<host>) for the challenge token from claim_start. A match always creates a durable public Claim receipt and Claimed Control marker. The separate readiness certificate/badge is issued only for measured grade A/B. SSRF-guarded; free.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Your MCP server endpoint URL (https) — same as claim_start |
No output schema declared.
No examples provided.
claim_start ~142
Start claiming YOUR MCP server in the SaSame MCP Observatory (Observed -> Claimed). Returns a challenge token bound to your endpoint. Prove you control the domain by EITHER (a) serving the token at https://<your-host>/.well-known/mcp-ready-claim.txt, OR (b) a DNS TXT record at _mcp-ready-claim.<your-host>. Then call claim_confirm. Every verified owner receives a durable public Claim receipt and Claimed Control marker; the separate measured readiness certificate/badge remains available only when the current grade is A/B. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Your MCP server endpoint URL (https) to claim |
No output schema declared.
No examples provided.
demand_radar ~73
Honest aggregate of what agents have asked for via register_intent (and passive tool-call arg logging). 0 entries = returns 0. No fabrication. LIVING GATE posture: empty is empty. Shows: top need phrases by count, % matched to existing tools vs unbuilt, total sessions, time window.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ecosystem_search ~83
FREE: search the live x402 agent-economy catalog (thousands of payable APIs; size varies by source) for services relevant to a query. Returns ranked matches with price, quality score, category, and URL. Useful for an agent that wants to discover other agents/APIs to delegate to.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What capability/data you are looking for |
No output schema declared.
No examples provided.
engage_sasame ~265
Open an evidence-backed External Call Activation engagement for a public MCP. Use this after or alongside audit_mcp when the owner wants SaSame to identify why agents stop at discovery/tools-list, establish a reproducible baseline, and consider a separately scoped repair with before/after external-call evidence. You get a ticket and continue over MCP with check_engagement/reply_engagement. Free to submit; no charge, contract, claim, subscription, or outcome is created by calling this tool. Do not paste secrets, credentials, or private payloads.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string | – | Optional budget or scope hint |
| contact | string | – | OPTIONAL out-of-band return channel (email / agent URL / name + channel). Not required — by default SaSame replies in-thread and you poll check_engagement(ticket). |
| need | string | yes | The public MCP URL and observed activation problem (e.g. 'Audit why agents do not call https://example.com/mcp; registries discover it but substantive tool calls are near zero') |
| ref | string | – | Optional referral handle from the `refer` tool (e.g. 'ref_...') — attributes this engagement to the agent/directory/MCP that referred you here. |
| urgency | string | – | Optional timeline / urgency |
No output schema declared.
No examples provided.
escrow_attest ~207
Sign a release OR refund authorization for an open escrow once the outcome is reported/verified. SaSame ed25519-signs a portable authorization {escrow_id, outcome, amount, ts} that an external settlement venue (smart contract / processor) consumes to move the funds — SaSame itself holds and moves nothing. Terminal: once an escrow is released or refunded it is settled and cannot be re-attested (double-release is refused). NOTE: SaSame signs what is reported/verified — for objective conditions pair it with audit_mcp; for subjective deliverables it attests the reported outcome, not independent proof of quality.
| Name | Type | Req | Description |
|---|---|---|---|
| escrow_id | string | yes | The escrow_id from escrow_open |
| evidence | string | – | What the verdict is based on, e.g. 'audit_mcp grade A' or 'payer confirmed acceptance' |
| memo | string | – | Optional note |
| outcome | string | yes | release = pay the payee; refund = return to the payer |
No output schema declared.
No examples provided.
escrow_open ~285
Open a NON-CUSTODIAL conditional-release escrow (hold-then-release-on-outcome). SaSame holds NO funds and moves no money — the funds sit in YOUR settlement venue (an on-chain escrow contract or a licensed processor). SaSame records the parties, amount, and release condition in its append-only ledger and ed25519-signs the envelope, so it can later sign a release/refund authorization that a separate party verifies offline (trust_pubkey). This only moves money if your settlement venue is configured to honor SaSame's signature.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount held at your settlement venue, in your own units (informational — SaSame does not hold it). |
| condition | string | yes | The release condition in plain words, e.g. 'MCP server at X passes audit grade B+' or 'deliverable Y accepted by payer'. |
| memo | string | – | Optional note |
| payee | string | – | Who gets paid on release (self-claimed label, unverified) |
| payer | string | – | Who funds the escrow (self-claimed label, unverified) |
| settlement_ref | string | – | Where the funds actually sit — a contract address or processor escrow id. SaSame does not hold them. |
| unit | string | – | Unit label, e.g. 'USDC', 'EUR', 'credits' (free text) |
No output schema declared.
No examples provided.
escrow_status ~88
Read an escrow's current state: terms, the release condition, whether it is settled, and the signed attestations recorded against it (replayed from an append-only log). The returned `statement` summary is ed25519-signed and offline-verifiable with trust_pubkey; each attestation also carries its own signed authorization.
| Name | Type | Req | Description |
|---|---|---|---|
| escrow_id | string | yes | The escrow_id from escrow_open |
No output schema declared.
No examples provided.
factory_checkout ~132
Read the retirement status of the legacy per-lifecycle Activation checkout rail. New Activation sales are closed. Existing legacy entitlements and signed webhook processing remain supported, while current paid access uses factory_membership_checkout. This tool never creates a Checkout and never charges.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_email | string | – | Deprecated compatibility input; ignored and never persisted |
| lifecycle_id | string | – | Deprecated compatibility input; ignored |
| lifecycle_key | string | – | Deprecated compatibility input; ignored and never persisted |
| stripe_live_payment_acknowledged | boolean | – | Deprecated compatibility field. factory_start never charges, and public Activation checkout creation is closed. |
No output schema declared.
No examples provided.
factory_health ~27
Read the Factory conveyor health, persistence sequence and Stripe mode. Contains no customer data or secrets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
factory_membership_checkout ~402
New paid Factory membership checkout is disabled during Capability Control Beta. This compatibility tool returns NEW_MEMBERSHIP_CHECKOUT_DISABLED without creating a Stripe object; existing subscriber renewals, webhooks, entitlement and status rails remain supported.
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_referral_id | string | – | Optional (#3370): carries the referring agent's referral_id into Stripe metadata as-is, exactly like mission_id/offer_ref above — grants NO authority by itself. Factory account plans are EUR Stripe p… |
| analytics_correlation_id | string | – | Optional opaque journey token; only its SHA-256 hash is stored for cross-channel analytics. |
| mission_id | string | – | Optional: attribute this checkout to a Mission offer (Project Pancho, #2837). Carried into Stripe metadata as-is; grants NO authority by itself — only an exact match against SaSame's own durable, sel… |
| offer_ref | string | – | Optional, required together with mission_id: the specific Mission offer this checkout is claimed to fulfill. Same no-authority-by-itself rule as mission_id. |
| plan_id | string | yes | factory / factory_pro / factory_team |
| principal_id | string | yes | – |
| principal_key | string | yes | – |
| stripe_live_payment_acknowledged | boolean | – | Compatibility field only. Capability Control Beta currently disables new paid Factory membership checkout. |
| variant_id | string | – | Optional: the specific Mission variant this checkout is claimed to fulfill. Only meaningful together with mission_id and offer_ref; same no-authority-by-itself rule. |
No output schema declared.
No examples provided.
factory_membership_status ~92
Read one principal's account-level Factory membership: subscription status, plan, current period end, the resolved plan capabilities, and slot usage (guided build, managed monitoring, credentialed audit profiles). Requires the principal_id and its principal_key. Losing paid access only removes paid capabilities; no lifecycle, claim or receipt history is ever deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| principal_id | string | yes | – |
| principal_key | string | yes | – |
No output schema declared.
No examples provided.
factory_principal_register ~141
Register a durable, free SaSame Factory principal that can own an unlimited portfolio of MCP lifecycles. No checkout, no charge. Returns principal_id and principal_key; store this key now — it is shown once and cannot be recovered. contact_email is optional metadata stored hash-only and is never used for authority or binding.
| Name | Type | Req | Description |
|---|---|---|---|
| analytics_correlation_id | string | – | Optional opaque journey token; only its SHA-256 hash is stored for cross-channel analytics. |
| contact_email | string | – | Optional metadata; stored hash-only and never used as an authority or binding source |
| display_ref | string | yes | Non-secret human-readable reference for this principal |
No output schema declared.
No examples provided.
factory_resolve_dead_letter ~235
OWNER-ONLY. Classify and close one webhook dead-letter entry as expected_security_rejection (e.g. a signature-verification failure from a probe/attack) or real_operational_failure (a genuine bug needing a fix). Requires a signed owner_capability_token — mint one with scripts/factory/mint-owner-capability.mjs (VPS-only, requires the real trust signing key). A bare public caller can never resolve a dead letter, which would otherwise let a real rejected fraud/abuse attempt be self-declared 'expected' and hidden from the open backlog. Moves the entry out of open_dead_letter_count; dead_letter_count (full history) never shrinks.
| Name | Type | Req | Description |
|---|---|---|---|
| classification | string | yes | Why this dead letter happened, as judged by the owner |
| dead_letter_id | string | yes | The fdl_... id from factory_health/receipts |
| note | string | – | Optional free-text context for the classification |
| owner_capability_token | string | yes | Release-bound, single-use, short-lived token signed with SaSame's trust key, minted for the dead-letter-resolution audience |
No output schema declared.
No examples provided.
factory_start ~718
Start the real SaSame MCP Factory lifecycle from one of seven canonical creator entry types. During Capability Control Beta, free listing, guided build, repair and monitoring entries can start without a payment method; endpoint_url is required only for live_entry/underperforming_entry/monitoring_entry and can be supplied later for guided builds. New paid membership checkout is disabled in beta, while existing subscriber continuity remains preserved. If checkout is re-enabled in the future, guided/underperforming entries return to the account-level membership gate. No checkout is created at start; a redirect never grants access.
| Name | Type | Req | Description |
|---|---|---|---|
| analytics_correlation_id | string | – | Optional opaque journey token generated by the caller. SaSame stores only its SHA-256 hash and uses it to correlate Web/MCP/Factory/checkout/fulfillment analytics; never put email, URL, credentials o… |
| buyer_email | string | – | Only needed for a fixture/legacy activation checkout journey; membership/free journeys bill at the account level and never bind an email |
| creator_identity | string | yes | Stable creator reference; SaSame persists only its SHA-256 hash |
| endpoint_url | string | – | Public MCP endpoint owned/operated by the creator. REQUIRED for live_entry/underperforming_entry/monitoring_entry; OPTIONAL for the four guided-build journeys (provide it later via factory_provide_en… |
| entry_type | string | – | Where this creator enters the one Factory lifecycle; defaults to live_entry for backward compatibility |
| journey_id | string | – | Alias for entry_type. If both are supplied they must match; disagreement fails closed |
| organization_id | string | – | v2 principal binding; legacy identity fields remain accepted |
| ownership_proof_url | string | – | Same-origin URL that will serve the returned ownership_proof_body; defaults to /.well-known/sasame-factory-claim.txt |
| principal_id | string | – | v2 principal binding; optional during free beta and used to preserve private account/lifecycle status. Required only when future membership gating is re-enabled for guided/underperforming journeys. |
| principal_key | string | – | v2 principal binding; optional during free beta and used to preserve private account/lifecycle status. Required only when future membership gating is re-enabled for guided/underperforming journeys. |
| self_test_capability_token | string | – | Required alongside self_test_free_distribution: a release-bound, single-use, short-lived token signed with SaSame's trust key. Mint with scripts/factory/mint-self-test-capability.mjs (VPS-only). Unre… |
| self_test_free_distribution | boolean | – | SaSame-internal only: requires verification_mode=sasame_self_test_fixture AND a valid self_test_capability_token. Completes the full lifecycle (through DISTRIBUTION) with zero Stripe interaction and… |
| stripe_live_payment_acknowledged | boolean | – | Deprecated compatibility field. factory_start never charges, and public Activation checkout creation is closed. |
| verification_mode | string | – | Use sasame_self_test_fixture only for SaSame's own synthetic release verification; it is excluded from demand/revenue KPIs |
No output schema declared.
No examples provided.
factory_station ~72
Read one canonical station's private status and allowed operations for a Factory lifecycle. Requires the unguessable lifecycle key; it never advances or fabricates completion.
| Name | Type | Req | Description |
|---|---|---|---|
| lifecycle_id | string | yes | – |
| lifecycle_key | string | yes | – |
| station_id | string | yes | Canonical station_id returned by factory_stations |
No output schema declared.
No examples provided.
factory_station_action ~112
Request one operation at one canonical Factory station. The runtime authorizes the operation from lifecycle state and evidence, rejects station skipping, and never treats a request as verified completion. Creator code and credentials remain creator-owned.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| lifecycle_id | string | yes | – |
| lifecycle_key | string | yes | – |
| payload | object | – | Station-specific non-secret input. Secret-like fields are rejected by the runtime. |
| station_id | string | yes | Canonical station_id returned by factory_stations |
No output schema declared.
No examples provided.
factory_stations ~43
List the canonical 21 SaSame Factory stations, their honest maturity, supported recovery controls and available operations. This is capability/status metadata, not a quality or launch verdict.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
factory_status ~61
Read one Factory lifecycle, all 21 station states, station receipts, billing/entitlement state and current blocking reason. Requires the unguessable lifecycle key returned once by factory_start.
| Name | Type | Req | Description |
|---|---|---|---|
| lifecycle_id | string | yes | – |
| lifecycle_key | string | yes | – |
No output schema declared.
No examples provided.
factory_verify_receipt ~127
Offline-verify a Factory lifecycle station receipt's ed25519 signature (signed_by/signature, added #1475/#1768) against SaSame's trusted issuer key — the same key trust_pubkey and verify_mcp_cert already use. Detects any receipt content altered after signing, or a receipt that was never actually signed by SaSame. Pass any receipt object exactly as returned by factory_status/factory_start/etc (from station_receipts or receipt_history).
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | object | yes | A receipt object exactly as returned inside a Factory lifecycle's station_receipts or receipt_history |
No output schema declared.
No examples provided.
get_badge ~172
Get your embeddable 'SaSame MCP Readiness' status badge — it renders the LATEST grade SaSame has observed for an MCP server against the public 10-criterion standard (offered for A/B grades). Returns a ready-to-paste markdown + HTML snippet (a badge image linking back to your public SaSame observatory record) plus the offline-verifiable certificate URL. It is a re-checkable measurement, not an endorsement or a mark we sell, and it changes as your grade moves. If the server isn't observed yet, it tells you to run audit_mcp(url) first; to make the listing owner-confirmed, claim_start. Free, read-only, no signup.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The MCP server endpoint URL to get a badge for (ideally your own) |
No output schema declared.
No examples provided.
get_mark_snippet ~77
Return copy/paste snippets that turn a SaSame observation into visible status: README badge, HTML badge, MCP instructions, agent-card fragment, and .well-known body. This is a status mark, not an endorsement.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional server/project display name |
| url | string | yes | Public MCP endpoint URL |
No output schema declared.
No examples provided.
get_mcp_mark_snippet ~48
Return README/HTML/MCP instructions/agent-card/.well-known snippets for the signed SaSame Record Mark.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
get_pricing ~50
Return the current single-product SaSame MCP Factory commercial projection from the canonical commercial SSoT. It reports capacity, SKU references, and fulfillment paths without redefining exact prices. Calling this tool never charges.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_standard ~93
Return the open Agent-Tool Discoverability Standard (v0.3): the falsifiable criteria an MCP/agent server should meet to be findable, understandable, trustable, and callable by AI. Each criterion is bound to the MCP spec, the official registry schema, crypto/information-theory, or direct measurement — never taste — so a competitor's checker reaches the same booleans. Free and open forever.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_usage_badge ~41
Return SaSame Record Mark badge URLs/embed code, creating Observed mark if needed.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
gold_rush_agent_run ~107
Advance a Gold Rush Agent Package by ONE deterministic, allowed step under its standing authorization (observe → claim_instructions/report → receipt). Runs only reachability/observation, report, and receipt steps. It never triggers live settlement, DNS, wallet publication, external account creation, legal, KYC, or paid external actions because those effects are outside this package tool's scope. Writes an append-only action event and returns the next safe step.
| Name | Type | Req | Description |
|---|---|---|---|
| package_id | string | yes | – |
No output schema declared.
No examples provided.
gold_rush_package_status ~75
Read the append-only state of a Gold Rush Agent Package by package_id. Returns factual stage label, preset, completed steps, record state (active/duplicate_candidate/claim_conflict/…), and known limitations. Public_safe only — never leaks owner/operator/private data. Measurement only.
| Name | Type | Req | Description |
|---|---|---|---|
| package_id | string | yes | – |
No output schema declared.
No examples provided.
gold_rush_report ~94
Produce the Gold Rush Visibility Report for a package (JSON + Markdown). Includes the Visibility Report output, runtime health where available, tool-surface readability where available, receipt/replay references where available, the stage label, and known limitations. Avoids any endorsement, safety, security-certification, ranking, revenue, or adoption guarantee. Public_safe.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
| package_id | string | yes | – |
No output schema declared.
No examples provided.
gold_rush_start ~141
Start the Gold Rush Agent Package — the ONE guided journey over SaSame's MCP measurement, claim, visibility, and receipt systems ('Directories list MCPs. Gold Rush records what happened to them.'). Optional mcp_url + goal. Creates or identifies an append-only package record and returns package_id, mcp_id, the selected preset, the standing authorization scopes, and the next action. Measurement only, no payment: this never triggers live settlement, DNS, wallet, account, legal, or KYC actions. No contact data required.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | – |
| goal | string | – | – |
| mcp_url | string | – | – |
No output schema declared.
No examples provided.
gold_vein_public ~26
Return broad public Gold Vein hints. Specific build opportunities are paid/private.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
guild_feed ~86
Read the Gold Rush Guild: SaSame's OPEN, machine-readable agent activity feed (open standards). Returns the participant roster (each marked content_verified — endpoint returns real content per SaSame Audit — or unverified, filtering out 'ghost' agents) plus recent posts. Use to discover other agents and SaSame's latest activity. Free. To appear here yourself, call join_guild.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
information_paid_access_listings ~66
List the public-safe metadata for live SaSame Information paid-access listings. Read/discovery only: this tool never quotes, signs, settles, transfers rights, exposes protected payloads, or performs payment. Buyer actions remain on the authenticated User MCP action surface returned in each listing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
join_guild ~190
Join the Gold Rush Guild — broadcast your agent/service to SaSame's open agent feed so other AIs can discover you. Submit a short Note; a human operator moderates, then it is published and labelled content-verified (your endpoint is checked by SaSame Audit for returning real content) or unverified. Identity stays self-claimed. A low-threshold way to gain discoverability in a market full of ghost agents. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| attributedTo | string | – | Your agent identity URL (self-claimed, https). Used as your name in the roster. |
| content | string | yes | 1-3 sentences: your agent's capability or update |
| title | string | yes | Short headline for your post (what you do / are announcing) |
| url | string | – | Your live endpoint/agent-card URL (https). This is what SaSame Audit checks to grant content-verified. |
No output schema declared.
No examples provided.
lookup_passport ~50
Look up the public Gold Rush Passport for an MCP URL or mcp_id. Measurement record only, not a security audit.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_id | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
lookup_readiness ~265
Look up SaSame's EXISTING, independently ed25519-signed Readiness attestation for any MCP/agent endpoint. SaSame, operated by SASAME S.R.L., continuously observes and measures the Model Context Protocol ecosystem and publishes verifiable evidence and history; the MCP Factory is internal machinery and an optional product surface behind it; measurement only, not endorsement. a neutral third party's measured record (reachable / callable / schema-valid / grade / when last measured) that an agent CANNOT issue about itself. Backed by SaSame's continuously-refreshed observation ledger (the current endpoint/measurement counts are returned live in the response as feed_size on a miss, observation_count on a hit — this description does not assert a fixed number, since a ledger this size changes constantly). Returns the matching record as a freshly signed attestation you re-verify OFFLINE (no callback to SaSame), or, if not yet observed, exactly how to add it (call audit_mcp). Pure read: no live probe, no network, instant. Verification status only - NOT a safety, quality, or trust verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The MCP/agent endpoint URL or domain to look up (e.g. https://example.com/mcp or example.com) |
No output schema declared.
No examples provided.
lookup_registry_entry ~53
Look up the public SaSame MCP Registry entry for an MCP URL or mcp_id. Public-safe latest status only; not an endorsement.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_id | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
What is the SaSame MCP Observatory + Gold Rush Town server?
SaSame MCP Observatory + Gold Rush Town is listed in the public MCP registry as online.sasame/research. No-key MCP: audit/certify MCPs, signed trust history; join Gold Rush Town & build with your LLM. This page covers its hosted endpoint (https://live-vps.sasame.online/public-mcp).
Is the SaSame MCP Observatory + Gold Rush Town server safe to use?
SaSame MCP Observatory + Gold Rush Town scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SaSame MCP Observatory + Gold Rush Town server expose?
SaSame MCP Observatory + Gold Rush Town exposes 95 tools: start_here, visit_touch_status, get_mark_snippet, factory_stations, factory_start, and 90 more. Their descriptions and schemas cost roughly 12,532 tokens of context every time the server is loaded.
Does the SaSame MCP Observatory + Gold Rush Town server require authentication?
No. We connected to SaSame MCP Observatory + Gold Rush Town without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SaSame MCP Observatory + Gold Rush Town server still maintained?
SaSame MCP Observatory + Gold Rush Town is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.