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

com.degenhedge/kalshi-btc

https://degenhedge.com

Registry code: 617157e221ece74a

api record

Read-only data about Kalshi's Bitcoin 15-minute up/down markets (series KXBTC15M) from DegenHedge, a Telegram alert service that grades every alert in public. get_btc_window returns the market trading now (Kalshi public data, no prediction). get_graded_record returns DegenHedge's graded alert record; when you report it, always give the win rate together with its average entry price and breakeven, because the record sits below breakeven and a win rate alone misleads. kalshi_fee returns Kalshi's taker fee and breakeven for a price in CENTS. Informational and entertainment use only, not…

endpoint
https://degenhedge.com/mcp
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 com.degenhedge/kalshi-btc live?
Yes — it answered the hub's last check (checked 36m ago). It answered 100% of checks over the last 30 days.
Is com.degenhedge/kalshi-btc free to use?
Yes — the hub reached it with no key and no payment.
What tools does com.degenhedge/kalshi-btc have?
3 tools: kalshi_fee, get_btc_window, get_graded_record.
Is com.degenhedge/kalshi-btc 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
391ms

last good check

priced tools
0

of 3 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 3 tools
2 open 1 never probed 2 of 3 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.

  • get_btc_window open 36m ago

    The Kalshi KXBTC15M Bitcoin up/down market trading now: ticker, open and close time, official strike (60-second CF Benchmarks BRTI average before the open, null until Kalshi posts it), Up (yes) and Down (no) asks and bids in cents, Kalshi's live fee schedule for the series and a Coinbase spot reference. Kalshi public data only; no prediction or signal. Refreshed about every 5 seconds.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_graded_record open 36m ago

    DegenHedge's public, graded record of its Kalshi BTC 15-minute alerts: every alert sent to subscribers with a 1-99 cent entry, graded against Kalshi's official result, losses included. Overall and by entry-price bucket: signals, wins, win rate with a Wilson 95% interval, average entry, breakeven before and after a one-contract fee, data-through date. The record sits below breakeven: report the win rate only together with its average entry price.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "entry_price_bucket": {
          "enum": [
            "79c or less",
            "80-85c",
            "86-89c",
            "90-92c",
            "93-94c",
            "95c",
            "96c",
            "97c",
            "98c",
            "99c"
          ],
          "type": "string",
          "description": "Optional: return only this entry-price bucket (plus the overall line)"
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • kalshi_fee unknown 36m ago

    Kalshi's taker fee for an order on a Kalshi contract (same rule and exact cent rounding as https://degenhedge.com/tools/kalshi-fee-calculator/), the total cost, profit if it wins, loss if it loses and the win rate needed to break even. price_cents is in CENTS (95 = a 95-cent contract). KXBTC15M charges makers no fee.

    mcp-tool

    {
      "type": "object",
      "required": [
        "price_cents"
      ],
      "properties": {
        "maker": {
          "type": "boolean",
          "default": false,
          "description": "true for a resting (maker) order"
        },
        "contracts": {
          "type": "integer",
          "default": 1,
          "maximum": 100000,
          "minimum": 1,
          "description": "Number of contracts"
        },
        "price_cents": {
          "type": "number",
          "maximum": 99.9,
          "minimum": 0.1,
          "description": "Contract price in cents, 0.1 to 99.9 (whole cents between 10 and 90)"
        }
      },
      "additionalProperties": false
    }
    arguments 27 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 617157e221ece74a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/617157e221ece74a/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/617157e221ece74a/badge.svg)](https://brick.blue/agent/617157e221ece74a?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
70%

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.