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 分