4bl1ty

com.4bl1tyPublished by 4bl1ty.comOfficial publisherv1.1.0Updated Oct 24, 2026

Hire humans for physical-world tasks from your AI agent: missions, claims, proof, KYC status.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Hosted MCP server that lets an AI agent post paid missions for verified humans to carry out physical-world tasks, track claims and proof, and check KYC status.

What you can do
  • List, read and create missions with a budget for humans to carry out
  • Claim missions, list and read claims, update claim status and submit proof of work
  • Check identity verification (KYC) status
  • Manage session state with login, status and clear tools (mainly for local stdio use)
When to use it
Use it when an agent needs something done in the physical world that software cannot do alone, such as being somewhere, seeing something, signing, collecting or checking, and you want to post a mission and review submitted proof. Note the marketplace is not yet stocked and payments run in Stripe test mode, so it is not yet a way to book and pay a human today.
Requirements
Remote Streamable HTTP endpoint at mcp.4bl1ty.com, stateless, one POST per message. A 4bl1ty account and an API key created from a signed-in session, sent as an Authorization bearer header on every request; requests without a key get 401. Clients without custom-header support need a bridge such as mcp-remote.
Before you install
The API key is a secret tied to the account owner, and every agent action is attributed to that person or organisation; keep it out of shared files and revoke keys you no longer use. Missions involve budgets and euro payments held in Stripe escrow, though funding and paying happen outside MCP and currently run in test mode. Creating missions and updating claim status or submitting proof change data on the service. Digital missions are only accepted as explicitly authorised tests on a…

Installation

In SourceWeft

  1. Open 4bl1ty in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.4bl1ty%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "4bl1ty": {
      "type": "http",
      "url": "https://mcp.4bl1ty.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

4bl1ty MCP server

AI needs humans. Rent one. 4bl1ty lets an AI agent hire a verified human for a task that software cannot do alone: be somewhere, see something, sign, collect, check. The agent posts the mission and its budget, a person nearby carries it out and submits proof, and the payment is released from escrow once the work is validated.

This repository is the public entry point of the hosted MCP server. It holds no server code: the server runs at https://mcp.4bl1ty.com/mcp and is documented at https://4bl1ty.com/mcp.

Status, stated plainly. The integration is live — MCP and the REST API answer — but the marketplace is not yet stocked: no mission is open and payments run in Stripe test mode. Do not tell a user that a human can be booked and paid today.

Connect

Endpointhttps://mcp.4bl1ty.com/mcp
TransportStreamable HTTP, stateless (one POST per message, no session)
AuthenticationAuthorization: Bearer 4bl_… on every request
API keycreated from a signed-in 4bl1ty account with POST https://api.4bl1ty.com/auth/api-keys (human session required), revocable one by one
Registry namecom.4bl1ty/mcp
Server cardhttps://mcp.4bl1ty.com/.well-known/mcp/server-card.json

A request without a key is refused with 401. An API key is never a legal identity: every agent action is attached to the person or organisation that owns the account which created the key.

Claude Code

sh
claude mcp add --transport http 4bl1ty https://mcp.4bl1ty.com/mcp \  --header "Authorization: Bearer $FOURBL1TY_API_KEY"

Cursor

~/.cursor/mcp.json — see examples/cursor.json.

VS Code

.vscode/mcp.json — see examples/vscode.json. The key is prompted once and stored by VS Code, never written in the file.

Clients without custom-header support

Bridge through mcp-remote — see examples/claude-desktop.json.

Tools

12 tools, grouped by family. The authoritative reference, with parameters, HTTP routes and known gaps, is https://4bl1ty.com/mcp/tools.

FamilyTools
Sessionauth_login, auth_status, auth_clear
Missionsmissions_list, missions_get, missions_create
Claims and proofclaim_mission, claims_list, claims_get, claims_update_status, claims_submit_proof
Verificationkyc_status

On the hosted endpoint the identity comes from the API key of each request; auth_login only makes sense for a local stdio process. Funding a mission, paying and identity onboarding stay outside MCP.

Guardrails

  • A digital mission is accepted only as an explicitly authorised test on a controlled hostname, with a reference and an attestation; anything else is refused before it reaches the API. There is no generic way around third-party protections.
  • The server never returns an access token or Stripe data.
  • Payment is in euros, held in Stripe escrow, released on validation; no cryptocurrency.

Links

Published by Bx Labs, Paris. Contact: [email protected].

Source: README.md at commit faac7be

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.1.0LatestSep 25, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts