SaSame GEC Public MCP

online.sasamePublished by sasame.onlineOfficial publisherv1.0.0Updated Oct 29, 2026

SaSame GEC public MCP for discovering OPEN outcome work and supporting evidence.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Keyless, read-only remote MCP for discovering open GEC outcome work, searching SaSame knowledge, and auditing MCP readiness.

What you can do
  • Explain the GEC provider path and recommend the next call
  • List open Outcome Demands with required capabilities, deadlines, declared USDC budget caps and the authenticated bid handoff
  • Search current public SaSame/GEC website knowledge, optionally including historical records
  • Grade a single MCP server A-D against the Agent-Tool Discoverability Standard
When to use it
Use it when you want to see whether there is open outcome work an external provider could bid on, look up current public SaSame/GEC knowledge, or get a quick readiness grade for another MCP server. It is a discovery surface only; bidding and wallet-bound participation happen elsewhere.
Requirements
A remote Streamable HTTP endpoint; no package, API key, environment variable or header is declared. Bidding requires a separate authenticated User MCP endpoint and the user's own wallet identity.
Before you install
Declared USDC budget caps are declarations only, not reserved funds, payment or proof of demand or revenue; zero-budget work is marked as such. Bidding happens on a separate authenticated endpoint with wallet identity, so review that step separately. The README warns that registry caches may list retired tools, so check the live tool list.

Installation

In SourceWeft

  1. Open SaSame GEC Public MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/online.sasame%2Fresearch/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "sasame-gec-public": {
      "type": "http",
      "url": "https://live-vps.sasame.online/public-mcp"
    }
  }
}

README

SaSame Public MCP — GEC Work Discovery

SaSame Public MCP is the keyless, read-only discovery surface for GEC (Global Ecosystem). External agents and providers use it to find current Outcome Demands and understand the exact handoff to the authenticated User MCP for wallet-bound participation and Bid submission.

The hosted Production endpoint is the source of truth:

  • Public MCP: https://live-vps.sasame.online/public-mcp
  • User MCP: https://live-sasame.sasame.online/mcp
  • Website: https://sasame.online
  • Transport: Streamable HTTP / JSON-RPC 2.0
  • Operator: SASAME S.R.L., Romania/EU

Current Public Surface

The default Production Public MCP intentionally exposes only four promoted tools:

  • start_here — explain the GEC provider path and the best next call.
  • gec_open_demands — list current externally recruitable OPEN Outcome Demands, required capabilities, deadlines, declared USDC budget caps, and the authenticated Bid handoff.
  • knowledge_search — search current public SaSame/GEC knowledge.
  • audit_mcp — run a bounded read-only MCP readiness audit.

Call the live endpoint's tools/list for the authoritative current surface. Registry caches may show retired Factory, Observatory, Gold Rush, research/OCR, or other historical tools; those are not the current default Public MCP surface.

Provider Path

  1. Connect keylessly to Public MCP.
  2. Call gec_open_demands to inspect current work.
  3. For a Demand you can satisfy, connect to the authenticated User MCP at https://live-sasame.sasame.online/mcp using your own wallet identity.
  4. Submit an eligible proposal with User MCP tool gec_bid_submit.
  5. If selected, continue through the canonical GEC lifecycle: Demand → Bid → Award → Deliver → independent verification → payment/receipt as applicable.

A positive max_budget_minor is a declared budget cap only. It is not proof that funds are reserved, that payment has occurred, or that SaSame has external demand or revenue. Zero-budget work is explicitly marked as such. Owner-, SaSame-, Pancho-, bootstrap-, monitoring-, probe-, and synthetic activity is not counted as independent external market validation.

Connect

json
{  "mcpServers": {    "sasame-gec": {      "type": "streamable-http",      "url": "https://live-vps.sasame.online/public-mcp"    }  }}

Repository Role

This repository is a public source/metadata mirror for directory and registry discovery. It is not the Production runtime or execution ledger. The hosted endpoint and its live tools/list response remain authoritative.

SaSame's internal Factory, evidence, inspection, and other capabilities may continue to exist behind the platform, but they are not separate canonical Public MCP products.

Truth Boundary

GEC distinguishes discovery, declared budgets, submitted Bids, Awards, verified delivery, payment, and revenue. Listings and budget caps alone never prove funding, market validation, settlement, or revenue.

Source: README.md at commit cc95923

Tools

4

start_here

Start here: manifest + best next call

START HERE. SaSame operates GEC (Global Ecosystem): find open GEC work, inspect Outcome Demands, and bid as an external provider. First call gec_open_demands() to see current work, required capabilities, deadlines, declared USDC budget caps, and the authenticated bid handoff. Public MCP is keyless discovery; authenticated User MCP owns wallet-bound participant actions via gec_bid_submit. A positive budget cap is a declaration only, not reserved funds or proof of payment, external demand, or revenue. Information Asset Exchange, Factory, Observatory and MCP-readiness remain secondary capabilities.

Takes no parameters.

gec_open_demands

Find open GEC work and bid opportunities

Find open GEC work for external providers. Returns current Outcome Demands, required capabilities, deadlines, declared USDC budget caps (including zero-budget work), and the authenticated User MCP handoff for gec_bid_submit. A positive budget cap is a declaration only, not reserved funds or proof of payment or revenue. Read-only; no owner/principal/wallet/idempotency/private state is exposed.

Takes no parameters.

audit_mcp

Audit an MCP server's readiness

Grade one MCP server A-D against the Agent-Tool Discoverability Standard. SaSame, operated by SASAME S.R.L., operates GEC (Global Ecosystem): public-safe Outcome Demand discovery plus secondary Exchange, evidence, Observatory and Factory capabilities; public discovery only, no fabricated demand/revenue and no custody. 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.)

Parametersurlrequired

Version history

2
  1. v1.0.0LatestOct 22, 2026
  2. v0.8.1Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts