Skip to main content
Glama
305,560 tools. Last updated 2026-07-23 07:10

"GoCD" matching MCP tools:

  • Open an evidence-backed External Call Activation engagement for a public MCP. Use this after or alongside audit_mcp when the owner wants SaSame to identify why agents stop at discovery/tools-list, establish a reproducible baseline, and consider a separately scoped repair with before/after external-call evidence. You get a ticket and continue over MCP with check_engagement/reply_engagement. Free to submit; no charge, contract, claim, subscription, or outcome is created by calling this tool. Do not paste secrets, credentials, or private payloads.
    Connector
  • Where the market is moving — steam / sharp-money signal for upcoming events. Reads `mart_line_movement_features` (the hourly slate snapshots windowed per line identity) and surfaces the lines whose implied probability has moved the MOST since their opening snapshot, **aggregated across books** so it reflects the market's consensus move rather than one book's quirk. A line drifting toward a side means money is coming in on that side (steam / sharp action). IMPORTANT framing for the caller: this reports the *market's own revealed signal* (how the price has moved), NOT our model's edge and NOT a pick. It answers "where is the money going today" — pair it with `prop_slate` / `kalshi_edges` (model edge) to see where the market move agrees or disagrees with the model. Two guards keep the signal honest (both tunable): it defaults to the sportsbook feed (`source='the_odds_api'`) and EXCLUDES Kalshi, whose exchange contracts legitimately decay toward 0/1 over a multi-day resolution window (that drift is not pre-game steam); and it caps moves at `max_move` (default 30pp) because genuine pre-game steam is single-digit pp — a larger swing is almost always a stale opening snapshot, not money.
    Connector
  • Fantasy-football draft copilot: best available players by value over replacement, with tiers, positional need, and honest uncertainty. IMPORTANT: when the user states their draft position ("I have the 6th pick", "drafting 3rd", "pick 1.06"), ALWAYS pass it as `draft_slot` — it unlocks the snake pick schedule and per-player "gone by your pick" timing, which are exactly what draft-position questions need. Mid-draft usage: pass the names already taken (`drafted`) and your own picks (`my_roster`); get back the best AVAILABLE players ranked by points-above-replacement (PAR) for YOUR league shape, per-position tier cliffs ("2 RBs left in tier 3"), and which starting slots you still need. Pre-draft: call with no names for a cheat-sheet board. Reach/value: every row carries the player's Underdog best-ball `adp` (observed drafter behavior) and `value_vs_adp` = adp minus our PAR board rank (positive = the market lets you draft him later than our board values him). Mid-draft, `adp_fallers` lists available players already past their ADP — the market says they should be gone. Snake timing: pass `draft_slot` (your position in the draft order, 1..teams) and the response adds `draft_position` (your full snake pick schedule + next pick) plus per-row `gone_by_your_pick` — the first of your upcoming picks the player's ADP says he won't survive to (null = expected to outlast all your picks, or no ADP). "Take him now or lose him" becomes `gone_by_your_pick == your next pick`. Without `draft_slot`, `draft_position` contains a hint asking you to re-call with the slot when the user has stated it. Projections are a deliberately humble market blend (FantasyPros expert consensus rank mapped through 3-season positional points curves, nudged 30% by each player's prior-season scoring) — season-long calibration is unproven in year 1 and every row carries the market's own uncertainty (sd/best/worst) so you can see disagreement. This is fantasy roster research, not betting advice; kickers and team defenses are not modeled and should be drafted last on ordinary boards anyway.
    Connector
  • Grade one MCP server A-D against the Agent-Tool Discoverability Standard. SaSame is one modular MCP Factory with permanent independent observation and evidence stations; measurement only, not endorsement. Runs the LEGITIMATE MCP handshake (initialize + tools/list + one read-only tool call, all over POST JSON-RPC) and 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. Handshake 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.)
    Connector
  • Get SaSame-observed MCP server recommendations for a capability you need. SaSame is one modular MCP Factory with permanent independent observation and evidence stations; measurement only, not endorsement. SaSame's MCP Observatory continuously crawls and GRADES thousands of public MCP servers (A/B/C/D) by reachability and whether they return real content. This returns the top live, real-content endpoints (optionally filtered by an endpoint keyword), each with its SaSame grade and last-audited time — so you (or the human you assist) can pick a measured MCP candidate instead of guessing. Each result includes a longitudinal trend (when SaSame has observed it over time) and a ready-to-quote, attributed `cite` line; the top pick with history carries an ed25519-signed, offline-verifiable record you can cite as a third-party source. Free, read-only, no signup. If you operate one of these servers, claim it (claim_start). If you can't find a fit and need an MCP/agent BUILT, call engage_sasame. Pass a referral handle from `refer` as engage_sasame(ref=...) to attribute the introduction.
    Connector
  • One multi-chain onchain read (block_number|gas_price|balance|tx|erc20_balance|erc20_supply) reconciled across 2-3 independent RPC providers in parallel. Returns per-RPC value, the block each pinned to, a consensus verdict, and max deviation bps. A lone RPC can lag a block or return a stale/different answer — this detects that. Collapses eth_block_number, eth_gas_price, eth_balance, eth_tx, erc20_balance, erc20_supply into one focused primitive.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • No-key MCP: audit/certify MCPs, signed trust history; join Gold Rush Town & build with your LLM.

  • Sports-analytics research assistant that grades its own model and reports the losses. $9.99/mo.

  • START HERE. SaSame is one modular MCP Factory. Call factory_stations to inspect all 21 canonical station capabilities, then factory_start to enter the single lifecycle. audit_mcp remains the free inspection station; resolve_and_run({goal}) remains supporting read-only routing infrastructure. Measurement is status only, never endorsement.
    Connector
  • Sign a release OR refund authorization for an open escrow once the outcome is reported/verified. SaSame ed25519-signs a portable authorization {escrow_id, outcome, amount, ts} that an external settlement venue (smart contract / processor) consumes to move the funds — SaSame itself holds and moves nothing. Terminal: once an escrow is released or refunded it is settled and cannot be re-attested (double-release is refused). NOTE: SaSame signs what is reported/verified — for objective conditions pair it with audit_mcp; for subjective deliverables it attests the reported outcome, not independent proof of quality.
    Connector
  • Available player-prop slate with model edge per row, ranked by edge. Reads mart_slate_with_edge — the captured slate (every offered prop line across books) joined to the model's prediction. Each row carries the book's implied probability, our model probability, and model_edge = model_prob - implied_prob (computed vs THIS book's price). Two guards keep the ranking honest (both tunable): only **upcoming** events are shown (the mart retains past games — without this filter the top of the list is dominated by stale, settled lines), and edges are capped at `max_edge` (a >25pp edge is almost always a stale/odd price or model overconfidence, not a real bet — they carry a `verify` flag).
    Connector
  • Feed-health monitor: current data-quality check results across the feeds. Reads data_quality_checks (written by src/monitoring/data_quality.py after each slate capture and the daily tennis run). Takes the MOST RECENT result per (check_name, scope) within the lookback window, so it reflects current state rather than history. Check families: freshness.* (capture recency, fetch lag, last_update coverage), completeness.* (null rates, row/book volume vs baseline), accuracy.* (value ranges, two-sided vig, cross-book consensus), integrity.duplicate_rows, and tennis.* (serve-stat range + logical-consistency bounds).
    Connector
  • Confirm your domain-control proof and upgrade your SaSame MCP Observatory listing from Observed to CLAIMED. SaSame fetches /.well-known/mcp-ready-claim.txt (or checks the DNS TXT _mcp-ready-claim.<host>) for the challenge token from claim_start; if it matches, your listing becomes owner-confirmed 'Claimed', a signed Claimed MCP-Ready certificate is re-issued, and your badge reflects it. SSRF-guarded; free.
    Connector
  • Look up SaSame's EXISTING, independently ed25519-signed Readiness attestation for any MCP/agent endpoint. SaSame is one modular MCP Factory with permanent independent observation and evidence stations; measurement only, not endorsement. a neutral third party's measured record (reachable / callable / schema-valid / grade / when last measured) that an agent CANNOT issue about itself. Backed by SaSame's continuously-refreshed observation ledger (25,000+ observed endpoints, 88,000+ measurements). Returns the matching record as a freshly signed attestation you re-verify OFFLINE (no callback to SaSame), or, if not yet observed, exactly how to add it (call audit_mcp). Pure read: no live probe, no network, instant. Verification status only - NOT a safety, quality, or trust verdict.
    Connector
  • Get your embeddable 'SaSame MCP Readiness' status badge — it renders the LATEST grade SaSame has observed for an MCP server against the public 10-criterion standard (offered for A/B grades). Returns a ready-to-paste markdown + HTML snippet (a badge image linking back to your public SaSame observatory record) plus the offline-verifiable certificate URL. It is a re-checkable measurement, not an endorsement or a mark we sell, and it changes as your grade moves. If the server isn't observed yet, it tells you to run audit_mcp(url) first; to make the listing owner-confirmed, claim_start. Free, read-only, no signup.
    Connector
  • Poll the status of an engagement you opened with engage_sasame, and READ the human operator's reply — entirely over MCP, no email needed. Pass the `ticket` you got back from engage_sasame. Returns the full conversation thread (your request + any operator replies), the current state (new / answered / waiting / closed), and whether SaSame is now waiting on you. Call this again periodically (e.g. once a day) to pick up the operator's response. Free, read-only, deterministic — no LLM, no network.
    Connector
  • Zero-argument ecosystem view: SaSame's live 'State of the Agent Attack Surface' — how large the public MCP attack surface is, which capability classes it exposes (payment / code-execution / credential / write / send / fetch / read), and what share of state-changing tools ship with NO machine-readable safety annotation. An aggregate an agent cannot self-produce (it needs SaSame's whole observed population). ed25519-signed, offline-verifiable. OBSERVATION of the declared surface — not a safety, malware, or trust verdict. A frictionless first call: no URL needed. Cost-zero, observed level.
    Connector
  • Record a lifecycle status against an issued receipt (rcp_* from receipt_issue, or atr_* agent transaction receipts): revoked / disputed / corrected / superseded. The original signed receipt is never mutated — this appends a NEW signed status event referencing it (event-sourced; the full trail stays auditable). Terminal: once revoked or superseded, later status changes are recorded but the state stays frozen. 'corrected' requires corrected_by = the replacement receipt id. Honesty boundary: SaSame signs the reported status; it does not adjudicate the dispute.
    Connector
  • Every ticker symbol in the Gold Silver Analytics free-subset coverage universe (~279), plus the count. Symbols only — no scores.
    Connector
  • Health check + capability manifest — call this for "what can you do?" / greeting-style questions instead of guessing coverage. Returns server identity and a static ``coverage`` block: the sports/markets this server actually models and an explicit not-covered list. The owner (stdio) surface additionally reports version and which DuckDB target would be used — infra detail deliberately absent from the public product surface. Does not open a database connection, so it is safe to call from any environment as a liveness probe.
    Connector
  • Currently-offered props ranked by model edge, with a concentration flag. Like prop_slate (same upcoming-only + max_edge guards), plus a `player` filter (case-insensitive substring) and `in_n_parlays` per row — how many of today's recommended parlays (parlay_prediction_log, latest prediction_date) include this prop. A high count flags concentration risk: many suggested parlays sharing one leg. Each row also carries the cross-book consensus fields (consensus_implied, n_consensus_books, book_dispersion, edge_vs_consensus, model_outlier) — the per-book model_edge this tool ranks by is vs ONE book and may be the softest line, so consult edge_vs_consensus / model_outlier (see _PROP_EDGE_GUIDANCE) before trusting it.
    Connector
  • Create or retrieve the exact Activation-SKU Stripe LIVE Checkout for an inspected Factory lifecycle. The buyer email must match its one-way binding. Completing the Checkout charges real money at the owner-set activation price.
    Connector