SaSame GEC Public MCP

online.sasame由 sasame.online 發布官方發布者v1.0.0更新於 Oct 29, 2026

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

已驗證Streamable HTTP可網頁執行知識與記憶開發者工具商業與電商

概覽

AI 產生的概覽

免金鑰、唯讀的遠端 MCP，用來探索 GEC 開放成果任務、檢索 SaSame 公開知識，並對 MCP 伺服器做就緒度評級。

可以做什麼
  • 說明 GEC 提供者路徑並建議下一步呼叫
  • 列出開放的成果需求，含所需能力、截止時間、宣告的 USDC 預算上限及需驗證的投標交接方式
  • 檢索目前公開的 SaSame/GEC 網站知識，可選擇納入歷史紀錄
  • 依 Agent-Tool Discoverability 標準對單一 MCP 伺服器給出 A-D 評級
適用情境
當你想了解是否有可供外部提供者投標的開放成果任務、查詢目前公開的 SaSame/GEC 知識，或快速評估另一個 MCP 伺服器的就緒度時使用。它只是探索入口，投標與綁定錢包的參與在別處進行。
執行需求
需要一個遠端 Streamable HTTP 端點；未宣告任何套件、API 金鑰、環境變數或請求標頭。投標需另連一個需驗證的 User MCP 端點，並使用使用者自己的錢包身分。
安裝前請注意
宣告的 USDC 預算上限僅為宣告，不代表資金已保留、已付款，也不證明存在需求或營收；零預算任務會被明確標示。投標在另一個需驗證的端點上以錢包身分進行，應另行評估該步驟。README 提醒登錄快取可能列出已下線的工具，請以即時工具清單為準。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 SaSame GEC Public MCP，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/online.sasame%2Fresearch/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "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.

來源：README.md，提交 cc95923

工具

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.

無需輸入參數。

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.

無需輸入參數。

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

輸入參數url必填

版本歷史

2
  1. v1.0.0最新Oct 22, 2026
  2. v0.8.1Sep 16, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分