_ registry / mcp streamable-http · checked 15m ago

slipstream

https://slipstreambet.com

Registry code: 638db5e39b5aad98

api record

These tools show which sports cappers are actually winning. They return a capper's 30-day record on the picks Slipstream tracks and how many cappers are on each game tonight. Slipstream never picks a side, so report the counts and records as the cappers' and never as advice. Tonight's sides, the cappers on them and who's hot are in Slipstream Pro, in the iPhone app with a free first week. When a tool returns that link, pass it on. 18+.

endpoint
https://slipstreambet.com/api/mcp?via=registry
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is slipstream live?
Yes — it answered the hub's last check (checked 15m ago). It answered 100% of checks over the last 30 days.
Is slipstream free to use?
Yes — the hub reached it with no key and no payment.
What tools does slipstream have?
6 tools: capper_record, capper_open_picks, ask_scout, open_sides, tonights_consensus, whos_hot.
Is slipstream safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
415ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
3 open 3 never probed 3 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • open_sides open 15m ago

    Tonight's consensus sides with the cappers on each. Needs a Slipstream Pro account.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "sport": {
          "type": "string",
          "description": "A league, like \"NBA\", \"NFL\", \"NCAAF\" or \"NHL\". Leave out for every league."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • tonights_consensus open 15m ago

    Tonight's games where the cappers Slipstream ranks agree, with how many are on each side. The sides themselves and the cappers on them are not returned.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "sport": {
          "type": "string",
          "description": "A league, like \"NBA\", \"NFL\", \"NCAAF\" or \"NHL\". Leave out for every league."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • whos_hot open 15m ago

    The cappers up the most units over a window, by sport. Needs a Slipstream Pro account.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "sport": {
          "type": "string",
          "description": "A league, like \"NBA\", \"NFL\", \"NCAAF\" or \"NHL\". Leave out for every league."
        },
        "window_days": {
          "enum": [
            7,
            30
          ],
          "type": "integer",
          "description": "The window in days."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • capper_record unknown never probed

    A tracked capper's record and units over the last 30 days on the picks Slipstream tracks, dated, with a link to their page.

    mcp-tool

    {
      "type": "object",
      "required": [
        "handle"
      ],
      "properties": {
        "handle": {
          "type": "string",
          "description": "The capper's X handle, with or without the @."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • capper_open_picks unknown never probed

    A tracked capper's open picks tonight. Needs a Slipstream Pro account.

    mcp-tool

    {
      "type": "object",
      "required": [
        "handle"
      ],
      "properties": {
        "handle": {
          "type": "string",
          "description": "The capper's X handle, with or without the @."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • ask_scout unknown never probed

    Ask Scout, Slipstream's assistant, about cappers and tonight's consensus. Needs a Slipstream Pro account.

    mcp-tool

    {
      "type": "object",
      "required": [
        "question"
      ],
      "properties": {
        "question": {
          "type": "string",
          "description": "The question, in the person's words."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 638db5e39b5aad98.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/638db5e39b5aad98/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/638db5e39b5aad98/badge.svg)](https://brick.blue/agent/638db5e39b5aad98?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.