The HumanOps MCP server

The endpoint

MCP endpoint

https://quiescence.eu/humanops/mcp

Header

Authorization: Bearer ho_live_xxxxxxxxxxxxxxxxxxxxxxxx

Streamable HTTP, JSON-RPC 2.0. Authenticate with the same key the REST API uses — ho_live_… for real tasks, ho_test_… for the sandbox. Sandbox is a property of the key, so there is no second URL to remember and nothing to change when you go live.

Create a key

Keys are minted in the console and shown once. A revoked key answers differently from an unknown one, so you can always tell which happened.

Install it in your client

Pick your client. If your client is not listed, or the format below has moved on, the only two things any MCP client needs are the endpoint URL and the Authorization header — everything else is packaging.

claude mcp add --transport http humanops https://quiescence.eu/humanops/mcp \
  --header "Authorization: Bearer ho_live_xxxxxxxxxxxxxxxxxxxxxxxx"

{
  "mcpServers": {
    "humanops": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://quiescence.eu/humanops/mcp",
               "--header", "Authorization: Bearer ho_live_xxxxxxxxxxxxxxxxxxxxxxxx"]
    }
  }
}

{
  "mcpServers": {
    "humanops": {
      "url": "https://quiescence.eu/humanops/mcp",
      "headers": { "Authorization": "Bearer ho_live_xxxxxxxxxxxxxxxxxxxxxxxx" }
    }
  }
}

{
  "servers": {
    "humanops": {
      "type": "http",
      "url": "https://quiescence.eu/humanops/mcp",
      "headers": { "Authorization": "Bearer ${input:humanops-key}" }
    }
  },
  "inputs": [
    { "id": "humanops-key", "type": "promptString",
      "description": "HumanOps API key", "password": true }
  ]
}

{
  "mcpServers": {
    "humanops": {
      "serverUrl": "https://quiescence.eu/humanops/mcp",
      "headers": { "Authorization": "Bearer ho_live_xxxxxxxxxxxxxxxxxxxxxxxx" }
    }
  }
}

{
  "mcpServers": {
    "humanops": {
      "type": "streamableHttp",
      "url": "https://quiescence.eu/humanops/mcp",
      "headers": { "Authorization": "Bearer ho_live_xxxxxxxxxxxxxxxxxxxxxxxx" }
    }
  }
}

extensions:
  humanops:
    enabled: true
    type: streamable_http
    name: humanops
    uri: https://quiescence.eu/humanops/mcp
    headers:
      Authorization: "Bearer ho_live_xxxxxxxxxxxxxxxxxxxxxxxx"
    timeout: 300

Endpoint          https://quiescence.eu/humanops/mcp
Server Transport  HTTP Streamable
Authentication    Header Auth
  Name            Authorization
  Value           Bearer ho_live_xxxxxxxxxxxxxxxxxxxxxxxx

Wire the node into an AI Agent node and the eight tools appear
in its tool list.

Client config formats change faster than this page can. If one of these no longer matches your version, check your client's own MCP documentation for where it keeps remote servers — the URL and the header are unchanged.

Or install a bundle

A packaged .mcpb for desktop clients that install extensions from a file. It carries a manifest, a README and a sixty-line dependency-free bridge that forwards stdio JSON-RPC to this endpoint — no npx, nothing fetched from the network at launch, and short enough to read in full before you hand it a key. The copy-paste configuration above is the path we have exercised end to end; the bundle is offered second for that reason.

Download humanops.mcpb Registry manifest

The document indexes read to list this server, generated from the running server so it cannot describe one we no longer operate.

Check it works before you trust it

This is the whole handshake. It needs no client, no SDK and no npm. If it answers with a serverInfo block, the problem is in your client config, not in the server.

curl -s https://quiescence.eu/humanops/mcp \
  -H "Authorization: Bearer ho_live_xxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{
        "protocolVersion":"2025-06-18","capabilities":{},
        "clientInfo":{"name":"curl","version":"1"}}}'

A working key answers with "serverInfo":{"name":"quiescence-humanops"…}. A missing or wrong key answers 401 and tells you which header it wanted.

What your agent gets

Eight tools, four resources and four worked recipes. The tool descriptions state cost, latency and the refusals up front, so a model knows before it calls rather than after.

Resources and recipes

Resources are readable context — attach them and a model can write a valid task spec without calling anything. Prompts are worked multi-step recipes: a model that has never bought human work does not know the sequence, and left to itself will order a task and then sit in a polling loop.

The one thing that trips models up

Try it without paying

From a framework instead

The MCP server is the shortest path, but the same tools reach the major agent frameworks through their own MCP clients. Runnable examples land with the SDKs.

from langchain_mcp_adapters.client import MultiServerMCPClient

client = MultiServerMCPClient({
    "humanops": {
        "transport": "streamable_http",
        "url": "https://quiescence.eu/humanops/mcp",
        "headers": {"Authorization": "Bearer ho_live_xxxxxxxxxxxxxxxxxxxxxxxx"},
    }
})
tools = await client.get_tools()

from agents.mcp import MCPServerStreamableHttp

humanops = MCPServerStreamableHttp(
    params={"url": "https://quiescence.eu/humanops/mcp",
            "headers": {"Authorization": "Bearer ho_live_xxxxxxxxxxxxxxxxxxxxxxxx"}},
)
agent = Agent(name="Field agent", mcp_servers=[humanops])

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

client = BasicMCPClient("https://quiescence.eu/humanops/mcp",
                       headers={"Authorization": "Bearer ho_live_xxxxxxxxxxxxxxxxxxxxxxxx"})
tools = await McpToolSpec(client=client).to_tool_list_async()

What we will not do

Named in the tool descriptions too, so a model finds out before it spends a call rather than after.

• Surveil, follow, photograph or gather information about a named private individual.
• Regulated professional acts — legal, medical or financial advice, or anything needing a licence we do not hold.
• Collect, copy or photograph identity documents.
• Enter a private home, or anywhere the person would be trespassing.
• Buy, sign, or sign in to anything on your behalf beyond an explicitly priced purchase task.
• Anything answerable from the public web. It is slower and it costs money.

Asking for one of these is not an error and does not count against you. It is refused, and the request is recorded — refusals are how we decide what to build next.

Questions

Next

• Capabilities and their schemas
• Where we operate
• Prices, and what the person is paid
• The threat model and the full refusal list