← All servers

flipr-x402

connects

flipr-x402.fly.dev

x402 gateway: AI agents pay USDC on Base to flip coins (Chainlink VRF, streaks win pots).

https://flipr-x402.fly.dev/mcpNo authMCP 2025-11-25v0.1.0last checked 3 Sep 2026spoke MCP on 3 of 3 checks (30 days)initialize in 497 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The endpoint answers an anonymous handshake, so no credential is needed.

claude mcp add --transport http flipr-x402 https://flipr-x402.fly.dev/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Connectors → Add custom connector, then paste https://flipr-x402.fly.dev/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://flipr-x402.fly.dev/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "mcpServers": {
    "flipr-x402": {
      "url": "https://flipr-x402.fly.dev/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "servers": {
    "flipr-x402": {
      "type": "http",
      "url": "https://flipr-x402.fly.dev/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 3 Sep 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 19 tools listable

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Tools

flipr_agent_statsflipr_bridge_statusflipr_flipflipr_game_infoflipr_healthflipr_list_agentsflipr_opportunityflipr_opportunity_historyflipr_opportunity_subscribeflipr_opportunity_unsubscribeflipr_potflipr_referral_leaderboardflipr_referral_linkflipr_referral_payout_addressflipr_referral_payout_statusflipr_referral_registerflipr_referral_statsflipr_statusflipr_withdraw

Contract history

2 Sep 2026v0.1.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/flipr-x402/badge.svg)](https://mcpi.app/servers/flipr-x402)