Hosted MCP server/Other

4bl1ty MCP server

Hosted at mcp.4bl1ty.com·Streamable HTTP

4bl1ty is a hosted MCP server that lets an AI agent hire verified humans for physical-world tasks. The agent posts a mission and budget, a nearby person carries it out and submits proof, and payment is released from escrow once the proof is accepted. The provider documents 12 tools for inspecting and drafting missions, claiming safe work, tracking assignments and submitting proof; funding, payment and KYC stay on the human side. The integration and API are live, but the marketplace is not yet stocked: no mission is open and payments run in Stripe test mode, so no human is bookable or payable today.

mcp.4bl1ty.com Streamable HTTP API key Source checked Nov 13, 2026 Server responded when checked Reviewed 2026-11-16
About

Where it fits

Agent builders that need physical-world tasks completed by verified humans with proof.

  • Inspect the mission and tool surface before posting.
  • Post a mission and its budget.
  • Review submitted proof before escrow is released.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds 4bl1ty as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http 4bl1ty https://mcp.4bl1ty.com/mcp --header "Authorization: Bearer <YOUR_4BL1TY_KEY>" --scope project
  2. 02

    Send the credential

    The provider expects the following header. Replace each placeholder with your own key or token before you connect.

    Required headers
    Authorization: Bearer <YOUR_4BL1TY_KEY>
  3. 03

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://mcp.4bl1ty.com/mcp
Host
mcp.4bl1ty.com · /mcp
Transport
Streamable HTTP
Authentication
API key
Server name
4bl1ty
Listing type
Community or directory listing

The installer uses the server name 4bl1ty. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that 4bl1ty appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Inspect the mission and tool surface before posting. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server responded when checked

We reached mcp.4bl1ty.com when we checked. That only means the address answered; it does not prove the MCP connection, sign-in, or tools work. The provider page was available when we checked.

Provider page available on Nov 13, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

4bl1ty documentationhttps://4bl1ty.com/mcp/toolsGitHub repositoryhttps://github.com/Brissux-Labs/4bl1ty-mcp