← flowstake.com

INDIVIDUAL MCP TOOL

get_challenge

Look up one public challenge by UUID or FlowStake URL.

flowstake.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://flowstake.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_challenge and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • A tool name or description suggests retrieving external content.

Parent server

flowstake.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.flowstake]
url = "https://flowstake.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "flowstake": {
      "type": "http",
      "url": "https://flowstake.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: flowstake
Remote MCP URL: https://flowstake.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "flowstake": {
      "url": "https://flowstake.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "flowstake": {
      "type": "http",
      "url": "https://flowstake.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "flowstake",
  "transport": "streamable-http",
  "url": "https://flowstake.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • search_athletes — Find public FlowStake athletes by username or display name.
  • get_athlete — Look up one athlete by exact username and return their public verification record.
  • list_stakes_board — Open crowd-proposed challenges, most-backed first.
  • list_races — Events FlowStake athletes train for and are verified at.
  • explain_verification — How FlowStake decides an activity is real: the checks applied, what each tier means, and the limits of the claim.
  • list_ledger_anchors — Published Merkle roots for closed UTC days of the activity ledger.
  • verify_inclusion — Return the sibling path to a published daily root.
  • check_record — Look up proof metadata for one PUBLIC activity: handle, type, UTC day, rounded distance, verification flag, data_root, tier, and the daily ledger root if that day is anchored.