# humans fix ai (remote · humansfix.ai)

Ask a real, manually approved developer for help. Nothing is sent until you say yes.

- Trust score: 79/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `humansfix.ai`: 79/100 (this document), [markdown](https://verifymcp.io/servers/ai-humansfix-humansfix/humansfix.md), [page](https://verifymcp.io/servers/ai-humansfix-humansfix/humansfix)

## Channel facts

- Endpoint: `https://humansfix.ai/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `2.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 725 tokens (~181/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 13 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 3 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the humans fix ai MCP server?

humans fix ai is a hosted endpoint at https://humansfix.ai/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.

### Claude

```bash
claude mcp add --transport http ai-humansfix-humansfix 'https://humansfix.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-humansfix-humansfix": {
      "url": "https://humansfix.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-humansfix-humansfix": {
      "type": "http",
      "url": "https://humansfix.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-humansfix-humansfix]
url = "https://humansfix.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-humansfix-humansfix": {
      "type": "remote",
      "url": "https://humansfix.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-humansfix-humansfix --url 'https://humansfix.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-humansfix-humansfix:
    url: "https://humansfix.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-humansfix-humansfix": {
      "Transport": "http",
      "Url": "https://humansfix.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-humansfix-humansfix -t streamable-http -u 'https://humansfix.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-humansfix-humansfix": {
      "type": "http",
      "url": "https://humansfix.ai/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-14 (score 79, 0)

- [security] Tool “ask_human_developer” rewrote its description, which is the text the model reads
- [security] Tool “get_task_status” rewrote its description, which is the text the model reads
- [security] Tool “respond_to_call_time” rewrote its description, which is the text the model reads
- [security] Tool “send_request” rewrote its description, which is the text the model reads
- [security] Tool “respond_to_call_time” is now declared destructive
- [functional improvement] Schema quality: 226 → 181
- [cosmetic] “send_request” reworded the description of “text”

### 2026-11-13 (score 79, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “ask_human_developer” rewrote its description, which is the text the model reads
- [security] Tool “get_task_status” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 664 → 907
- [functional] Destructive annotations: pass → 100
- [functional] New tool “send_request”

### 2026-11-12 (score 79, +5)

- [security regression] Stability: 0.10 → fail
- [security improvement] Authorization: partial → pass
- [security] First check of Authorization: pass
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “ask_human_developer” rewrote its description, which is the text the model reads
- [functional regression] “ask_human_developer” dropped the required parameter “email”
- [functional improvement] Schema quality: 320 → 221
- [functional] Server version: 1.0.1 → 2.0.0
- [functional] New tool “get_task_status”
- [functional] New tool “respond_to_call_time”

### 2026-11-11 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.0.1

### 2026-11-08 (score 72)

First indexed and scored.

## MCP tools (4)

### `ask_human_developer` (~182 tokens)

Ask a human developer

Saves a draft request to a real, manually approved human developer: a question, a code review, a consultation or hands-on help with a software problem. It takes a short summary in plain words, which must not contain passwords, API keys, tokens or other secrets. Only a draft is saved: nothing reaches a developer until it is sent, and nothing is charged. It returns the exact saved text and a task_id.

Input parameters:

- `availability` (string): When the person is free for a call, for example 'weekdays after 5pm CET'. Optional.
- `summary` (string, required): What the person needs, in plain words: what is wrong or what they want help with, what they were doing, and what has already been tried. No secrets.
- `tool` (string): The AI tool the app was built with, if known.

### `send_request` (~130 tokens)

Send a request to developers

Sends a saved draft to approved developers. It works only for a draft this connection saved in the last 30 minutes, and each person can send only a few per day. The person receives an email copy with a link to cancel. Nothing is charged. The optional text is compared with the saved draft, and nothing is sent if it differs.

Input parameters:

- `task_id` (string, required): The draft to send: the task_id that ask_human_developer returned.
- `text` (string): The exact saved text, to confirm what is being sent. If it differs from the saved draft, nothing is sent.

### `get_task_status` (~121 tokens)

See where a request stands

Returns where the user's requests stand: a fixed state, a next_action (send_request, respond_to_call_time, person_decides_on_website, join_call, wait or none), the call time in the user's own time zone and a link to the request page. With no task_id it lists the most recent requests. Read-only. It never returns text written by a developer. Prices, approvals and cards are never handled by this connector.

Input parameters:

- `task_id` (string): The request to look at. Leave it out to list the most recent ones.

### `respond_to_call_time` (~175 tokens)

Answer a call time

Answers a call time for a request. 'accept' confirms the time a developer proposed, or the new time a developer asked for. 'decline' says it does not work: before the call is booked another developer is asked, afterwards the booked time stays. 'propose_other_time' suggests a new time for a booked call; the developer is emailed and answers. Times are shown in the user's own time zone; new times are ISO 8601 with an offset.

Input parameters:

- `action` (string, required): What the person chose.
- `task_id` (string, required): The request the call is for.
- `time` (string): Only for propose_other_time: the new start as ISO 8601 with an offset, for example 2026-11-12T15:00:00+01:00.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-humansfix-humansfix/humansfix#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 79
- 2026-11-19: 79
- 2026-11-18: 79
- 2026-11-17: 79
- 2026-11-16: 79
- 2026-11-15: 79
- 2026-11-14: 79
- 2026-11-13: 79
- 2026-11-12: 79
- 2026-11-11: 74
- 2026-11-10: 73
- 2026-11-09: 73
- 2026-11-08: 72

## Common questions

### What is the humans fix ai MCP server?

humans fix ai is an MCP server listed in the public MCP registry as ai.humansfix/humansfix. Ask a real, manually approved developer for help. Nothing is sent until you say yes. This page covers its hosted endpoint (https://humansfix.ai/mcp).

### Is the humans fix ai MCP server safe to use?

humans fix ai scores 79 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 humans fix ai MCP server expose?

humans fix ai exposes 4 tools: ask_human_developer, send_request, get_task_status, respond_to_call_time. Their descriptions and schemas cost roughly 608 tokens of context every time the server is loaded.

### Does the humans fix ai MCP server require authentication?

Yes. humans fix ai asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the humans fix ai MCP server still maintained?

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

### What did VerifyMCP test on the humans fix ai MCP server?

VerifyMCP ran 13 checks on humans fix ai, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://humansfix.ai/mcp
- Repository: https://github.com/humansfixai/humansfixai-mcp
- Website: https://humansfix.ai/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/ai-humansfix-humansfix/humansfix.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-humansfix-humansfix/humansfix/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-humansfix-humansfix/humansfix.json
- HTML version of this page: https://verifymcp.io/servers/ai-humansfix-humansfix/humansfix
