Skip to content

SaSame GEC Public MCP server

online.sasame/researchsasame.onlinestreamable-httpv1.0.0Scanned

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

4 tools: 3 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 3 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 1
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SaSame GEC Public MCP server can do

The SaSame GEC Public MCP server is published by sasame.online, a domain the MCP Registry verified. It has 4 tools. It can create or change data (3 tools: start_here, gec_open_demands and audit_mcp), but cannot delete data. 1 tool only reads.

2 tools bring in text other people can write (knowledge_search and audit_mcp); 1 tool can send data out of your system (audit_mcp).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 3Claude Code: ask
  • audit_mcpGrade one MCP server A-D against the Agent-Tool Discoverability Standard.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.)

    Annotations the server declares

    • title: Audit an MCP server's readiness
    • readOnlyHint: true
    • openWorldHint: true
  • gec_open_demandsFind open GEC work for external providers.1 finding

    Why it is in this group

    • The name "gec_open_demands" says "open": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "gec_open_demands" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "gec_open_demands" says "open": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Find open GEC work for external providers. Returns current Outcome Demands, required capabilities, deadlines, declared buyer all-in USDC budget caps (including zero-budget work), and the authenticated User MCP handoff for gec_bid_submit. Any GEC success fee is included inside the awarded amount rather than added to the buyer total. 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.

    Annotations the server declares

    • title: Find open GEC work and bid opportunities
    • readOnlyHint: true
    • openWorldHint: false
  • start_hereSTART HERE.1 finding

    Why it is in this group

    • The name "start_here" says "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "start_here" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "start_here" says "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    START HERE. SaSame operates GEC (Global Ecosystem): create and publish a real Outcome Demand as an independent buyer, or discover and bid on existing work as an independent provider. Public MCP is keyless discovery. Authenticated User MCP lets a verified wallet create its own Project and non-zero Demand via gec_project_create, gec_demand_create, and gec_demand_publication_set, or bid via gec_bid_submit. Independent buyers use their own genuine need and capital; SaSame does not reimburse or round-trip fund external demand. 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.

    Annotations the server declares

    • title: Start here: manifest + best next call
    • readOnlyHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:17 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://live-vps.sasame.online/public-mcp: tools/list returned 4 tools to an anonymous client, including start_here (write), gec_open_demands (write), audit_mcp (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "start_here" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "start_here" says "start": a word for a change.

    What this check looks for
  • The server marks "gec_open_demands" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "gec_open_demands" says "open": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http research https://live-vps.sasame.online/public-mcp
claude mcp add --transport http research https://live-vps.sasame.online/public-mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__research__knowledge_search"
    ],
    "ask": [
      "mcp__research__start_here",
      "mcp__research__gec_open_demands",
      "mcp__research__audit_mcp"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as research. Review it before you use it.

Capability tags behind 2 rules
  • mcp__research__knowledge_search untrusted-input
  • mcp__research__audit_mcp untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/online.sasame/research/verify?hash=779471c0c258d2b2a6fcee5012a32597db26cbd77f5b551e1ade4c425c3d74fc" | jq -e '.changed == false'

Pinned hash 779471c0c258, from Nov 8, 2026, 15:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/online.sasame/research/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for online.sasame/research
[![Anlyon Radar](https://radar.anlyon.com/badge/online.sasame/research.svg)](https://radar.anlyon.com/servers/online.sasame/research)

Source: MCP Registry · repository. Synced Oct 22, 2026, 13:18 UTC.

SaSame GEC Public MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SaSame GEC Public MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the SaSame GEC Public MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the SaSame GEC Public MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the SaSame GEC Public MCP server have?

4 tools: 3 write, 1 read. start_here, gec_open_demands, audit_mcp and knowledge_search.

Does the SaSame GEC Public MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SaSame GEC Public MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): audit_mcp.

Has the SaSame GEC Public MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.