SaSame MCP Observatory + Gold Rush Town MCP Server

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.

Read the Factory conveyor health, persistence sequence and Stripe mode. Contains no customer data or secrets.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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).

Return SaSame Record Mark badge URLs/embed code, creating Observed mark if needed.

Issue/refresh a signed SaSame Record Mark. Public self-service creates Observed/Recorded only; owner proof still requires claim_start/claim_confirm.

Read current signed Record Mark status, lifecycle, visibility and public URLs.

Append lifecycle status without deleting history.

Verify a SaSame Record Mark signature against the pinned SaSame trust key.

Bounded scanner for README/site/agent-card/.well-known SaSame mark visibility. Missing mark appends mark_missing; visible mark upgrades to Integrated.

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.

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.

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.

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.

Return broad public Gold Vein hints. Specific build opportunities are paid/private.

[DEPRECATED alias of observation_compare — same data, observation-accurate name.] Neutral head-to-head comparison of two servers' observed measurements.

[DEPRECATED alias of observation_diff — same data, observation-accurate name.] Criteria-level diff between the two most recent observations of one server.

[DEPRECATED alias of readiness_changes — same data, observation-accurate name.] Public MCP servers whose observed readiness changed over time. Measurement only — not an endorsement or ranking.

Return SaSame's ed25519 PUBLIC key. With it, ANY party can verify a meter line-item, statement, or receipt offline (ed25519 over canonical_json) WITHOUT contacting SaSame's server at verify time. Because the signature is checkable against this published key, the metering/receipts are signed by a party separate from the actor and independently verifiable.

[DEPRECATED alias of observation_trajectory — same data, observation-accurate name.] Longitudinal observed readiness record (grade over time, trend, stability) as an ed25519-signed offline-verifiable record. Measurement only — not a trust/safety verdict.

No MCP server yet? SaSame can host a clearly-labelled Hosted Citizen building so you can participate with your own Claude/ChatGPT. Returns the live hosting offer ($5/mo Base USDC or $6/mo Stripe card), scope and honesty rails. Town action quotes remain separate and unsettled until verified.

Step 2 of claiming your building. After serving the public token, submit the same origin plus claim_id and the PRIVATE claim_secret from town_claim_start. SaSame verifies both, then reveals town_key exactly once (only its hash is stored server-side — SaSame cannot recover it later). The response includes a 'setup' block: show the user setup.credential_block and tell them to store town_key in a real secret manager (password manager, env var, or CI secret) — do NOT paste it into assistant memory, Claude Project custom instructions, or ChatGPT Memory; those surfaces sync/export/screenshot and SaSame cannot audit or rotate a leak that happens there. There is no login — town_key is the only proof of ownership. If it's leaked but still known, call town_rotate_key immediately. If it's fully lost, there is no self-service recovery today; tell the user to email [email protected].

Step 1 of claiming your building. Returns claim_id, a public token to serve at /.well-known/sasame-town-claim.txt, and a PRIVATE claim_secret. Do not publish claim_secret. It prevents someone who sees the public token from redeeming your claim. Expires in 15 minutes. Claiming is free.

Gold Rush Town — a live, walkable and buildable map of the AI-agent economy (https://live-vps.sasame.online/world/). Residents are graded MCP servers and travelers are observed crawlers. Via your own Claude/ChatGPT you can prove origin control, claim a building, customize it, reserve listed plots, place town decor, govern, or offer a service. Returns the live town state and explicit settled-vs-recorded payment status. Free, no auth. SaSame is non-custodial.

Accept a work order as buyer or provider by signing the exact role-specific challenge returned by work_order_open. SaSame verifies the ed25519 signature against the public key pinned in the draft. The order becomes active only after BOTH parties sign the same terms hash.

Buyer acceptance of the latest delivery. Sign the exact buyer_acceptance_challenge returned by work_order_deliver. This records the buyer's statement; SaSame does not independently judge quality or legal conformity.

Record provider delivery for an active work order. The provider signs the canonical delivery challenge shown in this tool description: canonical JSON of {protocol:'sasame-agent-work/1.0',action:'deliver',work_order_id,proof_sha256,proof_uri}. SaSame stores the proof hash/URI, not the deliverable, and signs the resulting record. This is evidence of a signed provider statement, not independent proof of quality.

Open a neutral agent-to-agent work-order DRAFT. 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. Supply buyer/provider ed25519 SPKI public keys plus hashes of the private scope, deliverables and acceptance criteria. SaSame returns one exact acceptance challenge per party. The order is not active until BOTH matching keys sign. Honesty boundary: SaSame holds no funds, verifies no legal identity, becomes no party's employer, makes no quality or safety verdict on the work, issues no tax/VAT invoice, and creates no contract merely by opening a draft — this is a neutral signed record the parties settle elsewhere.

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.

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.

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.

Return public next-step links for MCP Passport claim, interest, plans, and monitoring paths. Read-only; no external action is triggered.

Return the public aggregate analytics export manifest. No private owner analytics.

Read the public outside-in Analytics summary. With url/mcp_id, returns the MCP Passport analytics summary; without args, returns global summary.

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.

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.

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.

Look up the public Gold Rush Passport for an MCP URL or mcp_id. Measurement record only, not a security audit.

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.

Look up the public SaSame MCP Registry entry for an MCP URL or mcp_id. Public-safe latest status only; not an endorsement.

Record a charge against a meter and ENFORCE the cap. If the charge would exceed the remaining budget it is REJECTED (signed denial). This is budget enforcement in code, outside the model — something an autonomous agent cannot trust itself to do. Returns remaining + a signed line-item.

Open a usage/budget meter recorded in SaSame's append-only ledger. Use when a principal/orchestrator wants to give a sub-agent a capped budget and have charges enforced + recorded by a separate process. SaSame holds NO funds and is NOT a payment processor: it timestamps and ed25519-signs the envelope with its published public key, so the accounting is offline-verifiable. Returns a meter_id + a signed receipt (verify the signature with trust_pubkey).

Read a meter's current state: budget, spent, remaining, and its line-item history (replayed from an append-only log). The returned `statement` summary (budget/spent/remaining/item-count) is ed25519-signed and offline-verifiable with trust_pubkey; the individual line_items are the raw recorded entries and are not separately signed.

Get an ed25519 receipt for an action/tool-call you (or a peer) report. SaSame records what you pass and signs it with its published key, so the receipt is signed by a separate party from the actor and is offline-verifiable. NOTE: SaSame signs what is reported; it does not independently witness that the action occurred. Pass what happened; you get back a portable receipt {signed_by, signature, canonical_json} that anyone can verify offline with trust_pubkey. Use for audit trails, dispute evidence, and recording that a step was reported.

Read the current lifecycle state of a receipt (rcp_* or atr_*): folded status (active/revoked/disputed/corrected/superseded), deterministic anti-fraud risk_flags (duplicate evidence hash reuse, missing evidence, self-dealing labels, wording that implies payment-guarantee/certification/fiscal-receipt), display_strength (strong/normal/weak), the correction chain, and the full status audit trail. Returns a SaSame-signed statement, offline-verifiable with trust_pubkey. Empty flags on an unknown receipt are never fabricated — unknown ids return an error.

Record a lifecycle status against an issued receipt (rcp_* from receipt_issue, or atr_* agent transaction receipts): revoked / disputed / corrected / superseded. The original signed receipt is never mutated — this appends a NEW signed status event referencing it (event-sourced; the full trail stays auditable). Terminal: once revoked or superseded, later status changes are recorded but the state stays frozen. 'corrected' requires corrected_by = the replacement receipt id. Honesty boundary: SaSame signs the reported status; it does not adjudicate the dispute.

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.)

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.

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.

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.

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.

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.

Get one public SaSame website knowledge record by slug. Read-only.

Search current public SaSame website knowledge. Historical records are included only when include_historical is true. Read-only.

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.

Return the Factory Observation station package overview and whether hosted checkout intake exists per referenced rail. Read-only: no checkout or charge is triggered by this tool.

Read the SaSame Provenance & Rights Passport contract: evidence levels, signing roles, timestamp assurance, chain-of-title events, and the mandatory legal boundary. Read-only; never creates or registers copyright. 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.

Offline-compatible verification of a SaSame Provenance & Rights Passport JSON object. Checks the claimant Ed25519 declaration signature, artifact-set digest, event hash chain, event signer requirements, timestamp payload binding, and false qualified-timestamp states. Read-only; makes no legal ownership decision. 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.

PubMed citation retrieval. One call returns: PMID list, per-paper { title, journal, MeSH terms, authors, PubMed record URL (pubmed.ncbi.nlm.nih.gov/<PMID>/ — resolves to the citation/abstract record page, not guaranteed full text), publication date, stale flag }. Abstract full text is NOT returned inline; see abstract_note for where to fetch it. Structured JSON, no free-text upsell in result. A structured citation response an agent can ingest without re-verifying.

FREE preview: real PubMed (NCBI) search. Returns top article titles + PMIDs + journals. No paid research tier is active.

Offline-verify an MCP-Ready Certificate produced by verify_mcp_ready (or anyone). Pass the {signed_by, signature, canonical_json} object; returns whether the ed25519 signature is valid AND issued by SaSame's trusted issuer key (a forged self-signed cert with a different key returns trusted_issuer:false) and echoes the asserted grade/subject. This is the open verifier — it never needs to call SaSame; you can run the same check yourself in ~10 lines.

Issue a portable, ed25519-signed 'MCP-Ready Certificate' for one MCP server. 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. Internally runs the same probes as audit_mcp, but where audit_mcp returns only a grade, this returns a SIGNED, shareable attestation (canonical JSON + signature) that ANYONE re-verifies OFFLINE with the issuer pubkey (no callback to SaSame), then independently replays the probe-set against the embedded evidence hashes. Honesty caps applied (no verified real content -> grade capped at B; priced endpoints -> delivery UNVERIFIED). The cert is a fact you can check, not a badge we sell.

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.

List saved chain recipes (name, description, step count).

Return the public MCP Gold Rush Chronicle teaser. Detailed intelligence is paid/private.

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.

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.

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.

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.

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.

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.

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.

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.

Return public aggregate MCP Market Context. Aggregate measurement context only; not a recommendation.

Return README/HTML/MCP instructions/agent-card/.well-known snippets for the signed SaSame Record Mark.

Return public monitoring receipt candidates. Measurement records only; no SLA or endorsement.

FREE: extract text from an image URL via SaSame OCR (tesseract). Returns text preview + confidence. Full untruncated extraction is the paid x402 /ocr/full endpoint.

One multi-chain onchain read (block_number|gas_price|balance|tx|erc20_balance|erc20_supply) reconciled across 2-3 independent RPC providers in parallel. Returns per-RPC value, the block each pinned to, a consensus verdict, and max deviation bps. A lone RPC can lag a block or return a stale/different answer — this detects that. Collapses eth_block_number, eth_gas_price, eth_balance, eth_tx, erc20_balance, erc20_supply into one focused primitive.

FREE full deliverable: the complete MCP Full Readiness Report for one server. Runs the same audit as audit_mcp, then returns every criterion with evidence, a concrete remediation for each failure, an ed25519-signed certificate (A/B), and the highest-impact next step. Use it as directory pre-flight. Legal/account requirements are out of scope. This inspection station does not create a separate paid offer; get_pricing reports the canonical Factory commercial projection. Best run against YOUR OWN server. Handshake only — no auth-bypass, no payment, cost-zero.

Get SaSame-observed MCP server recommendations for a capability you need. 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. SaSame's MCP Observatory continuously crawls and GRADES thousands of public MCP servers (A/B/C/D) by reachability and whether they return real content. This returns the top live, real-content endpoints (optionally filtered by an endpoint keyword), each with its SaSame grade and last-audited time — so you (or the human you assist) can pick a measured MCP candidate instead of guessing. Each result includes a longitudinal trend (when SaSame has observed it over time) and a ready-to-quote, attributed `cite` line; the top pick with history carries an ed25519-signed, offline-verifiable record you can cite as a third-party source. Free, read-only, no signup. If you operate one of these servers, claim it (claim_start). If you can't find a fit and need an MCP/agent BUILT, call engage_sasame. Pass a referral handle from `refer` as engage_sasame(ref=...) to attribute the introduction.

Register an attribution handle for introductions to SaSame. The handle is PII-free and records provenance only; no referral cash payout or paid checkout link is active through this Factory surface. Do NOT paste secrets/keys here.

ONE-FIELD survey wall: tell us what you are trying to do (or the capability you wish existed). Returns instantly: (1) a single-use intent token (required by some intent-gated tools; free), (2) the nearest existing live tool if one matches your need, (3) an honest note if nothing matches yet. Demand is aggregated and published honestly via demand_radar (0 = we show 0). Cost-zero, no LLM in the path, deterministic.

Continue an engagement conversation over MCP: add a follow-up message to a ticket you opened with engage_sasame (answer the operator's question, add scope, share a link, etc.). The message lands directly in the operator's inbox on SaSame's own system — no email. Pass the `ticket` and your `message`. Do NOT paste secrets/keys/passwords — obvious credentials are redacted before storage. Free, deterministic.

Injection-quarantined EVIDENCE GRAPH for any research query. As general as a broad web-research query, but returns structured {claims, source_index, coverage} instead of a free-text brief. Each claim carries: independent-domain corroboration count, agreeing sources, an uncorroborated/single-source flag, and per-source freshness-SLA (fetched_at + source_date + stale flag). Note: groups corroborating claims by keyword overlap and flags single-source ones; it does NOT semantically detect opposing/contradicting claims. Zero upsell in any LLM-ingested field — all commercial content lives in _meta only. Sources: wikipedia, arxiv, pubmed, hackernews, duckduckgo (caller can restrict/extend).

PRIMARY SaSame entry point. Give SaSame the outcome you need. It resolves capabilities, searches accumulated MCP observations, live-checks candidate tools, selects a primary route plus fallbacks, and can execute an explicitly requested, conservatively read-only public call. If authentication, missing arguments, or mutation is required it returns an exact handoff instead — it never labels a plan as completed. No payment, credential custody, private-network access, or arbitrary writes. Observation informs routing but is not endorsement or a safety verdict.

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.

START HERE. 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 production machinery and an optional product surface behind it. Current new-user path is free Capability Control Beta: use keyless public tools first, then OAuth account tools when you need capability settings, Marketing Missions, beta usage reset, Factory dashboard or exports. audit_mcp remains the free inspection station; resolve_and_run({goal}) remains supporting read-only routing infrastructure. Measurement is status only, never endorsement.

Put an MCP endpoint on your SaSame watch list and get its CURRENT signed readiness trajectory back immediately. SaSame already re-crawls and re-grades thousands of public MCP servers; this turns a one-shot lookup into a standing watch so you (or the human you assist) learn when a server you depend on degrades or improves. Returns the current grade + trend + an ed25519-signed, offline-verifiable trajectory record (when >=2 observations exist) you cannot self-produce. Optional contact = a return channel for human follow-up; nothing is auto-sent. Free, read of the proprietary longitudinal ledger.

Read the privacy-safe Visit Touch funnel. Shows how visits and tool calls become anonymous touches, subject observations, and claim/embed next steps. Optional url filters to one subject.