Skip to content

BitPredict MCP server

io.bitpredict.app/bitpredictapp.bitpredict.iostreamable-httpv1.0.0Scanned

Read what BitPredict members call Up or Down on each coin, plus the Daily Call and crowd record.

4 tools: 4 change things.

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

Tools listed without sign-in. Remote posture

With Anlyon

4 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 BitPredict MCP server can do

The BitPredict MCP server is published by app.bitpredict.io, a domain the MCP Registry verified. It has 4 tools. It can create or change data (4 tools: crowd_call, daily_call, crowd_record and make_call), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

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

Its remote endpoint lists its tools without sign-in.

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 4Claude Code: ask
  • crowd_callWhat BitPredict members called on a coin over the last 30 days: the Up vs Down split and how many calls it rests on.1 finding

    Why it is in this group

    • The name "crowd_call" says "call": 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 "crowd_call" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "crowd_call" says "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    What BitPredict members called on a coin over the last 30 days: the Up vs Down split and how many calls it rests on. Members only, never the house AI agents. Says so when fewer than 5 member calls exist.

    Annotations the server declares

    • title: Crowd call on a coin
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • crowd_recordHow BitPredict members did on recently settled calls: hit rate over the last 30 and 7 days, plus a pointer to the public hash chain that proves the results.No 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.
    Description, as the server wrote it
    How BitPredict members did on recently settled calls: hit rate over the last 30 and 7 days, plus a pointer to the public hash chain that proves the results. Members only.

    Annotations the server declares

    • title: How the crowd did
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • daily_callToday's BitPredict Daily Call: the coin of the day, its opening price, the question, and the members' Up vs Down split so far.1 finding

    Why it is in this group

    • The name "daily_call" says "call": 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 "daily_call" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "daily_call" says "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Today's BitPredict Daily Call: the coin of the day, its opening price, the question, and the members' Up vs Down split so far.

    Annotations the server declares

    • title: Today's Daily Call
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • make_callPlaces nothing.1 finding

    Why it is in this group

    • The name "make_call" says "call": 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 "make_call" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "make_call" says "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Places nothing. Returns a link the person opens in BitPredict to lock in a 24h Up or Down call on a coin (a free account is created if they have none). Use it when the person wants to make that call.

    Annotations the server declares

    • title: Get a link to make a call
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
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 16, 2026, 14:21 UTC, unchanged since Nov 9, 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
4
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 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://app.bitpredict.io/api/mcp: tools/list returned 4 tools to an anonymous client, including crowd_call (write), daily_call (write), crowd_record (write), make_call (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

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

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "crowd_call" says "call": a word for a change.

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

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "daily_call" says "call": a word for a change.

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

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "make_call" says "call": a word for a change.

    What this check looks for

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http bitpredict https://app.bitpredict.io/api/mcp
claude mcp add --transport http bitpredict https://app.bitpredict.io/api/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": [],
    "ask": [
      "mcp__bitpredict__crowd_call",
      "mcp__bitpredict__daily_call",
      "mcp__bitpredict__crowd_record",
      "mcp__bitpredict__make_call"
    ],
    "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 bitpredict. Review it before you use it.

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/io.bitpredict.app/bitpredict/verify?hash=f889b1b3eb2acd45778182aad5e5e1efd86b958d730d6eb94bfade7168326ec6" | jq -e '.changed == false'

Pinned hash f889b1b3eb2a, from Nov 8, 2026, 14:17 UTC.

Watch

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

https://radar.anlyon.com/servers/io.bitpredict.app/bitpredict/changes.xml

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

Badge

Anlyon Radar badge for io.bitpredict.app/bitpredict
[![Anlyon Radar](https://radar.anlyon.com/badge/io.bitpredict.app/bitpredict.svg)](https://radar.anlyon.com/servers/io.bitpredict.app/bitpredict)

Source: MCP Registry. Synced Nov 8, 2026, 14:17 UTC.

BitPredict MCP server: questions and answers

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

Is the BitPredict MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 3 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 BitPredict MCP server delete data?

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

Can the BitPredict 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 BitPredict MCP server have?

4 tools: 4 write. crowd_call, daily_call, crowd_record and make_call.

Does the BitPredict MCP server need sign-in or OAuth?

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

Does the BitPredict MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the BitPredict MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.