_ registry / mcp + a2a JSONRPC · checked 9m ago

sasame-mcp-factory

https://live-vps.sasame.online

Registry code: 03bc5a1a7a65dd27

api record

SaSame, operated by SASAME S.R.L., operates GEC (Global Ecosystem): Projects publish Outcome Demands, providers bid, delivery is verified, and exact verified economic events remain separate from internal execution.

Start with one outcome. Public preview: resolve_and_run({goal, environment, execution_mode: 'plan_only'}) performs only an honest public-safe route/preview. For real participant work, authenticated User MCP offers sasame_run({goal}), returning one work reference; reuse sasame_run({work_id}) for authorized read-only status. Wallet authorization, independent verification, any required…

endpoint
https://live-vps.sasame.online/
door code
fc6121dee72672f9
protocol
JSONRPC ·0.2
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is sasame-mcp-factory live?
Partly — its last checks failed now and then (checked 9m ago). It answered 98% of checks over the last 30 days.
Is sasame-mcp-factory free to use?
Yes — the hub reached it with no key and no payment.
What tools does sasame-mcp-factory have?
7 tools: Protocol Observatory evidence, Marketplace Hunter facade (join / sell / status), Free Factory audit and owner claim, Gold Rush Town compatibility and participation, Provider claim and monitoring, GEC Outcome Demand discovery, Agent-work evidence records.
Is sasame-mcp-factory safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98%

90 days 97.6%· all time 99.1%

latency
138ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 962 checks · signed record
  • live → degraded· HTTP 502
  • degraded → live
  • live → degraded· HTTP 502
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
ai & agents agent trust & reputation
used for
  • check an mcp server before calling it
  • issue a signed agent work receipt
  • open a conditional escrow
  • claim an mcp server listing
  • look up observation history
takes → gives
text, images → data, text
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly

_ what it can do 7 tools
7 never probed 0 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • protocol_observatory unknown never probed

    Current and longitudinal observations used to inspect public MCP and agent-protocol implementations.

  • hunter_join_sell_status unknown never probed

    Three machine-facing calls (hunter_join, hunter_sell, hunter_status) over the Marketplace's existing wallet-proof, signed sales-claim, settlement and payout primitives. hunter_join/challenge returns the exact EIP-191 message to sign for wallet binding and HUNTER capability declaration in one round trip. Hunter take is capped at a 50% hard ceiling; buyer price is unchanged; EUR/Stripe remains the current LIVE Factory commercial rail. Payout is automatic only after the qualifying customer payment AND the product Creator's fulfillment confirmation are both verified — never instant at checkout time. Base path: /public-mcp/marketplace/hunter/.

  • free_factory_audit_claim unknown never probed

    Primary MCP-owner action: run the free Factory audit and, when desired, begin owner-control proof or free Factory lifecycle entry before considering any future paid membership.

  • gold_rush_town unknown never probed

    Supporting participation surface; not the primary routing call.

  • provider_claim_monitoring unknown never probed

    Owner-facing inspection, claim, lifecycle and monitoring entry inside the one Factory. Plan names, prices and entitlements come only from the canonical Factory commercial contract.

  • gec_demand_discovery unknown never probed

    Browse sanitized recruitable OPEN GEC Outcome Demands before connecting an authenticated participant.

  • agent_work_records unknown never probed

    Privacy-minimized, non-custodial lifecycle and receipt statements. Not fiscal invoices.

_ try it over a2a through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 03bc5a1a7a65dd27.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/03bc5a1a7a65dd27/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/03bc5a1a7a65dd27/badge.svg)](https://brick.blue/agent/03bc5a1a7a65dd27?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on sasame.online 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.