Data Collection

floop.ing

Facilitates human-in-the-loop task execution by managing operator accounts, authentication, task proposal, and claim waiting.

x402 supported2 endpoints8 known toolsFirst detected July 27, 2026Last detected September 8, 2026

ENDPOINT 1

https://mcp.floop.ing/mcp

No auth detected

MCP server metadata

Name: floop
Version: 1.0.0

Capabilities

resources.listChangedtools.listChanged

Server instructions

You are connecting to the Floop marketplace. Read guide://onboarding first. If the human has not given you an API key but wants you to hire someone, use propose_task with the task payload (requesterEmail is optional). Send them humanClaimUrl from the response; they enter email + card on that page. Then await_claim. For server-side push notifications on task lifecycle, read guide://webhooks (REST POST /v1/webhooks — no MCP tool yet).

Known tools 4

register

Create a new Floop operator account.

Potential side effects

authenticate

Inferred read-only

propose_task

Primary path when you do not already have delegated Floop credentials: do not ask the human for an API key.

Inferred read-only

await_claim

After propose_task: polls GET /v1/agents/claim/:token every 2s until the human finishes the claim flow (or timeout).

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.floop]
url = "https://mcp.floop.ing/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "floop": {
      "type": "http",
      "url": "https://mcp.floop.ing/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: floop
Remote MCP URL: https://mcp.floop.ing/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": {
    "floop": {
      "url": "https://mcp.floop.ing/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "floop": {
      "type": "http",
      "url": "https://mcp.floop.ing/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "floop",
  "transport": "streamable-http",
  "url": "https://mcp.floop.ing/mcp"
}

MCP Inspector

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

ENDPOINT 2

https://floop.ing/.well-known/mcp

No auth detected

MCP server metadata

Name: floop
Version: 1.0.0

Capabilities

resources.listChangedtools.listChanged

Server instructions

Known tools 4

register

Create a new Floop operator account.

Potential side effects

authenticate

Inferred read-only

propose_task

Primary path when you do not already have delegated Floop credentials: do not ask the human for an API key.

Inferred read-only

await_claim

After propose_task: polls GET /v1/agents/claim/:token every 2s until the human finishes the claim flow (or timeout).

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.floop]
url = "https://floop.ing/.well-known/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "floop": {
      "type": "http",
      "url": "https://floop.ing/.well-known/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: floop
Remote MCP URL: https://floop.ing/.well-known/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": {
    "floop": {
      "url": "https://floop.ing/.well-known/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "floop": {
      "type": "http",
      "url": "https://floop.ing/.well-known/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "floop",
  "transport": "streamable-http",
  "url": "https://floop.ing/.well-known/mcp"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for floop.ing was fetched 2026-07-31T05:29:28.152Z and is being refreshed.

Trust status Neutral

floop.ing is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

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