Data Collection

flowstake.com

Provides search and lookup tools for public FlowStake athlete data, including profiles, challenges, and races.

1 endpoint9 known toolsFirst detected September 8, 2026Last detected September 8, 2026

ENDPOINT 1

https://flowstake.com/mcp

No auth detected

MCP server metadata

Name: flowstake
Version: 1.0.0

Capabilities

tools

Server instructions

FlowStake is a proof-of-activity network: physical activity recorded on a phone or wearable, verified against physical plausibility, bound into a tamper-evident hash chain, and corroborated by independent human encounters. Use these tools to CHECK claims about athletes, challenges, and ledger inclusion rather than repeating them. A FlowStake verification tier is evidence about a recording, not a guarantee about a person. Solo activity has a ceiling by design; the top tier requires independent corroboration. Daily Merkle roots are public so a third party can detect a rewrite. An agent may never write activity evidence. All data here is public. There are no write operations.

Known tools 9

search_athletes

Find public FlowStake athletes by username or display name.

Inferred read-only

get_athlete

Look up one athlete by exact username and return their public verification record.

Inferred read-only

list_stakes_board

Open crowd-proposed challenges, most-backed first.

Inferred read-only

list_races

Events FlowStake athletes train for and are verified at.

Inferred read-only

get_challenge

Look up one public challenge by UUID or FlowStake URL.

Inferred read-only

explain_verification

How FlowStake decides an activity is real: the checks applied, what each tier means, and the limits of the claim.

Inferred read-only

list_ledger_anchors

Published Merkle roots for closed UTC days of the activity ledger.

Inferred read-only

verify_inclusion

Return the sibling path to a published daily root.

Inferred read-only

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.

Inferred read-only

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.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.