Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Floatout

REMOTE · FLOATOUT.XYZ · SCANNED SEP 28

Launch a branded Hyperliquid perps and prediction market DEX. Read plans, guides and fee research.

Available components

70 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 153 tokens (~51/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Floatout MCP server?

Floatout is a hosted endpoint at https://floatout.xyz/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · floatout.xyz

# add to Claude Code
claude mcp add --transport http xyz-floatout-public 'https://floatout.xyz/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "xyz-floatout-public": {
      "url": "https://floatout.xyz/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "xyz-floatout-public": {
      "type": "http",
      "url": "https://floatout.xyz/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.xyz-floatout-public]
url = "https://floatout.xyz/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-floatout-public": {
      "type": "remote",
      "url": "https://floatout.xyz/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add xyz-floatout-public --url 'https://floatout.xyz/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  xyz-floatout-public:
    url: "https://floatout.xyz/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "xyz-floatout-public": {
      "Transport": "http",
      "Url": "https://floatout.xyz/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add xyz-floatout-public -t streamable-http -u 'https://floatout.xyz/api/mcp'
// mcp.json
{
  "mcpServers": {
    "xyz-floatout-public": {
      "type": "http",
      "url": "https://floatout.xyz/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 26 Sept 26 69

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 28 Sept 2026 · Probed https://floatout.xyz/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=floatout.xyz CN=WE1,O=Google Trust Services,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA256 f33ecafa79f5248a13c2331d68f20f56
SANs: floatout.xyz, app.floatout.xyz, *.app.floatout.xyz
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of floatout.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
floatout.xyz. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
content-security-policy frame-ancestors 'self' https://floatout.xyz https://*.floatout.xyz https://floatout.trade https://*.floatout.trade

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://floatout.xyz/api/mcp Verified 200
http (plaintext) http://floatout.xyz/api/mcp HTTPS enforced 301 https://floatout.xyz/api/mcp
MCP tools · 3 exposed · ~153 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list_floatout_plans ~48

Read current publicly purchasable Floatout activation plans, prices, revenue-share terms and browser purchase links. Checkout requires the owner's wallet. Does not create an order or make a payment.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_builder_fee_study ~54

Read Floatout's fixed September 10–23, 2026 archive sample of gross Hyperliquid builder fees in USDC, including daily data and coverage limitations. Not Floatout revenue or expected customer earnings.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_floatout_page ~51

Read a public Floatout product, pricing, security or operator guide as Markdown. Returns current published content with its source URL. Does not sign in or change a platform.

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

Common questions

What is the Floatout MCP server?

Floatout is an MCP server listed in the public MCP registry as xyz.floatout/public. Launch a branded Hyperliquid perps and prediction market DEX. Read plans, guides and fee research. This page covers its hosted endpoint (https://floatout.xyz/api/mcp).

Is the Floatout MCP server safe to use?

Floatout scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Floatout MCP server expose?

Floatout exposes 3 tools: list_floatout_plans, read_floatout_page, read_builder_fee_study. Their descriptions and schemas cost roughly 153 tokens of context every time the server is loaded.

Does the Floatout MCP server require authentication?

No. We connected to Floatout without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Floatout MCP server still maintained?

Floatout is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.