Invoke Human Tasks

REMOTE · INVOKE.NANOCORP.APP · SCANNED AUG 3

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

Available components

+5 this week 70 70 Trust /100

Trust breakdown (6 categories)

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. How we score →

Endpoint Security69

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability71

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 242 tokens (~121/item across 2 items; 2 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management23

Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · invoke.nanocorp.app

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

2 Aug 26 +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.
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +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.
28 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
27 Jul 26 65

First indexed and scored.

Show 4 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://invoke.nanocorp.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=nanocorp.app	CN=YE1,O=Let's Encrypt,C=US	26 Jun 2026	24 Sept 2026	ECDSA 256	ECDSA-SHA384	51c788aaacb56374cfd0c883882163c3565
SANs: *.nanocorp.app, nanocorp.app
CN=YE1,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC insecure

Validation of invoke.nanocorp.app. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
app.	present	23684	8	Verified
nanocorp.app.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=63072000; includeSubDomains; preload

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://invoke.nanocorp.app/mcp	Verified	200
http (plaintext)	http://invoke.nanocorp.app/mcp	Inconclusive	406

MCP tools — 2 exposed · ~242 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

hire_human Hire human ~124

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

Input Output Examples

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

Name	Type	Req	Description
checkout_url	string	yes	NanoCorp checkout URL to pay the platform fee and activate the task.
platform_fee_cents	integer	yes	Platform fee due before activation, in USD cents.
status	string	yes	Task status, typically pending_payment until the checkout is paid.
task_id	string	yes	Invoke task identifier.

No examples provided.

post_human_task Post human task ~118

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

Input Output Examples

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

Name	Type	Req	Description
checkout_url	string	yes	NanoCorp checkout URL to pay the platform fee and activate the task.
platform_fee_cents	integer	yes	Platform fee due before activation, in USD cents.
status	string	yes	Task status, typically pending_payment until the checkout is paid.
task_id	string	yes	Invoke task identifier.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug

Day	Score
27 Jul	65
28 Jul	66
29 Jul	66
30 Jul	67
31 Jul	69
1 Aug	69
2 Aug	70
3 Aug	70