# Invoke Human Tasks (remote · invoke.nanocorp.app)

Hire humans for tasks AI agents can't do through Invoke's paid task marketplace.

- Trust score: 70/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `invoke.nanocorp.app`: 70/100 (this document), [markdown](https://verifymcp.io/servers/app-nanocorp-invoke-human-tasks/invoke.md), [page](https://verifymcp.io/servers/app-nanocorp-invoke-human-tasks/invoke)

## Channel facts

- Endpoint: `https://invoke.nanocorp.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## 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-08-03.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 242 tokens (~121/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http app-nanocorp-invoke-human-tasks https://invoke.nanocorp.app/mcp
```

### Codex

```toml
[mcp_servers.app-nanocorp-invoke-human-tasks]
url = "https://invoke.nanocorp.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-nanocorp-invoke-human-tasks": {
      "type": "remote",
      "url": "https://invoke.nanocorp.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-nanocorp-invoke-human-tasks --url https://invoke.nanocorp.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-nanocorp-invoke-human-tasks:
    url: "https://invoke.nanocorp.app/mcp"
```

### Other

```json
{
  "mcpServers": {
    "app-nanocorp-invoke-human-tasks": {
      "type": "http",
      "url": "https://invoke.nanocorp.app/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-08-02 (score 70, +1)

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

### 2026-07-31 (score 69, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 67, +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-07-28 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 65)

First indexed and scored.

## MCP tools (2)

### `post_human_task` (~118 tokens)

Post human task

Post a paid human task to Invoke and receive the pending task id plus checkout URL for activation.

Input parameters:

- `category` (string): Optional category such as research, testing, verification, calls, or physical-world.
- `contact_email` (string, required): Email address where Invoke can contact the task poster.
- `description` (string, required): Detailed instructions for the human worker.
- `reward_cents` (integer, required): Worker reward in USD cents. Must be 1000-50000.
- `title` (string, required): Short public title for the human task.

Output parameters:

- `checkout_url` (string): NanoCorp checkout URL to pay the platform fee and activate the task.
- `platform_fee_cents` (integer): Platform fee due before activation, in USD cents.
- `status` (string): Task status, typically pending_payment until the checkout is paid.
- `task_id` (string): Invoke task identifier.

### `hire_human` (~124 tokens)

Hire human

Alias for post_human_task: hire a human through Invoke for research, testing, verification, calls, or physical-world work.

Input parameters:

- `category` (string): Optional category such as research, testing, verification, calls, or physical-world.
- `contact_email` (string, required): Email address where Invoke can contact the task poster.
- `description` (string, required): Detailed instructions for the human worker.
- `reward_cents` (integer, required): Worker reward in USD cents. Must be 1000-50000.
- `title` (string, required): Short public title for the human task.

Output parameters:

- `checkout_url` (string): NanoCorp checkout URL to pay the platform fee and activate the task.
- `platform_fee_cents` (integer): Platform fee due before activation, in USD cents.
- `status` (string): Task status, typically pending_payment until the checkout is paid.
- `task_id` (string): Invoke task identifier.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-nanocorp-invoke-human-tasks/invoke#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 70
- 2026-08-01: 69
- 2026-07-31: 69
- 2026-07-30: 67
- 2026-07-29: 66
- 2026-07-28: 66
- 2026-07-27: 65

## Links

- Remote endpoint: https://invoke.nanocorp.app/mcp
- Repository: https://github.com/nanocorp-hq/invoke
- Website: https://invoke.nanocorp.app/for-agents
- Changelog RSS feed: https://verifymcp.io/servers/app-nanocorp-invoke-human-tasks/invoke/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-nanocorp-invoke-human-tasks/invoke/changelog.json
- HTML version of this page: https://verifymcp.io/servers/app-nanocorp-invoke-human-tasks/invoke