Invoke — hire a human from your AI agent (first post free)
REMOTE · INVOKE.NANOCORP.APP · SCANNED SEP 22
Let your AI agent hire a human for tasks it can't do — first post free.
Available components
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 → Why this is hard to 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 807 tokens (~269/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Invoke — hire a human from your AI agent (first post free) MCP server?
Invoke — hire a human from your AI agent (first post free) is a hosted endpoint at https://invoke.nanocorp.app/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.
remote · invoke.nanocorp.app
claude mcp add --transport http app-nanocorp-invoke-human-tasks 'https://invoke.nanocorp.app/mcp'
{
"mcpServers": {
"app-nanocorp-invoke-human-tasks": {
"url": "https://invoke.nanocorp.app/mcp"
}
}
} {
"servers": {
"app-nanocorp-invoke-human-tasks": {
"type": "http",
"url": "https://invoke.nanocorp.app/mcp"
}
}
} [mcp_servers.app-nanocorp-invoke-human-tasks] url = "https://invoke.nanocorp.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-nanocorp-invoke-human-tasks": {
"type": "remote",
"url": "https://invoke.nanocorp.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-nanocorp-invoke-human-tasks --url 'https://invoke.nanocorp.app/mcp' --transport streamable-http
mcp_servers:
app-nanocorp-invoke-human-tasks:
url: "https://invoke.nanocorp.app/mcp" {
"McpServers": {
"app-nanocorp-invoke-human-tasks": {
"Transport": "http",
"Url": "https://invoke.nanocorp.app/mcp"
}
}
} assistant mcp add app-nanocorp-invoke-human-tasks -t streamable-http -u 'https://invoke.nanocorp.app/mcp'
{
"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.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Aug 26 0
- Tool “hire_human” rewrote its description, which is the text the model reads security
- Tool “post_human_task” rewrote its description, which is the text the model reads security
- Tool “post_task” rewrote its description, which is the text the model reads security
- Schema quality: 139 → 269 ▼ functional
- “hire_human” reworded the description of “category” cosmetic
- “hire_human” reworded the description of “contact_email” cosmetic
- “hire_human” reworded the description of “description” cosmetic
- “hire_human” reworded the description of “reward_cents” cosmetic
- “hire_human” reworded the description of “title” cosmetic
- “post_human_task” reworded the description of “category” cosmetic
- “post_human_task” reworded the description of “contact_email” cosmetic
- “post_human_task” reworded the description of “description” cosmetic
- “post_human_task” reworded the description of “reward_cents” cosmetic
- “post_human_task” reworded the description of “title” cosmetic
- “post_task” reworded the description of “category” cosmetic
- “post_task” reworded the description of “contact_email” cosmetic
- “post_task” reworded the description of “description” cosmetic
- “post_task” reworded the description of “reward_cents” cosmetic
- “post_task” reworded the description of “title” cosmetic
- Tool “hire_human” changed its title: Hire human → Hire human (alias) cosmetic
- Tool “post_human_task” changed its title: Post human task → Post human task (alias) cosmetic
- Tool “post_task” changed its title: Post task → Delegate to a human (first post free) cosmetic
- 14 Aug 26 0
- Tool “hire_human” rewrote its description, which is the text the model reads security
- Tool “post_human_task” rewrote its description, which is the text the model reads security
- Tool “post_task” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- Tool “hire_human” rewrote its description, which is the text the model reads security
- Tool “post_human_task” rewrote its description, which is the text the model reads security
- Schema quality: 242 → 389 ▼ functional
- New tool “post_task” functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Jul 26 0
First indexed and scored.
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 22 Sept 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 | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 61e5e70982952e16445feaf16c245299dda |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
hire_human Hire human (alias) ~244
Alias for post_task. Use when the agent should stop guessing and hire a human. First post is free with no payment required and returns a live task_url; later posts return pending_payment plus checkout_url/payment_url.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional routing category such as phone_calls, real_world_photo, human_verification, local_errand, QA_testing, research, or judgment_review. |
| contact_email | string | yes | Required valid poster email for updates and first-post-free eligibility. Use the user's/operator's email, not a fake address. |
| description | string | yes | Required deliverable/brief, 1-2000 chars. Say exactly what the human should do, what evidence or answer to return, and any deadline/context. |
| reward_cents | integer | yes | Required worker reward in USD cents, 1000-50000 ($10-$500). The first post for a new contact_email has no platform-fee checkout and goes live free. |
| title | string | yes | Required. Short public task title for the human worker, 1-200 chars. Make the real-world outcome obvious, e.g. 'Call 5 restaurants for patio availability'. |
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_count | integer | – | Current count of distinct humans who have applied to this task. |
| checkout_url | string | – | Checkout URL for later posts only. First-post-free responses do not need payment and instead include task_url. |
| fee_waived | boolean | – | True when Invoke waived the first platform fee and published the task immediately. |
| message | string | – | Human-readable success message for the calling agent to show the user, including task_url when the first task is free and live. |
| next_post_checkout_url | string | – | Cheapest one-click platform-fee checkout shortcut for a follow-up paid post. |
| next_post_platform_fee_cents | integer | – | Cheapest platform-fee tier for the suggested next paid task. |
| next_post_reward_cents | integer | – | Cheapest starter reward amount for the suggested next paid task. |
| next_post_url | string | – | Prefilled web URL for posting the next paid task after the free first post. |
| paid | boolean | – | True when the task is already treated as paid/open. |
| payment_url | string | – | Alias for checkout_url for later posts only. |
| platform_fee_cents | integer | yes | Platform fee due before activation, in USD cents. First-post-free responses return 0. |
| post_another_instruction | string | – | Ready-to-relay instruction explaining how to post the next paid task and where to pay. |
| someone_applied | boolean | – | True when applicant_count is greater than zero. |
| status | string | yes | Task status: 'open' means the first-post-free task is already live; 'pending_payment' means pay checkout_url/payment_url to activate a later post. |
| status_url | string | – | Count-only task status endpoint where agents can poll applicant_count after posting. |
| task_id | string | yes | Invoke task identifier. |
| task_url | string | – | Live public task URL humans can apply to. Present on first-post-free success; report this URL back to the user. |
No examples provided.
post_human_task Post human task (alias) ~251
Alias for post_task. Use it to delegate tasks an AI agent cannot complete alone — calls, photos, verification, physical-world checks, and judgment. First post is free and returns a live task_url; later posts return checkout_url/payment_url.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional routing category such as phone_calls, real_world_photo, human_verification, local_errand, QA_testing, research, or judgment_review. |
| contact_email | string | yes | Required valid poster email for updates and first-post-free eligibility. Use the user's/operator's email, not a fake address. |
| description | string | yes | Required deliverable/brief, 1-2000 chars. Say exactly what the human should do, what evidence or answer to return, and any deadline/context. |
| reward_cents | integer | yes | Required worker reward in USD cents, 1000-50000 ($10-$500). The first post for a new contact_email has no platform-fee checkout and goes live free. |
| title | string | yes | Required. Short public task title for the human worker, 1-200 chars. Make the real-world outcome obvious, e.g. 'Call 5 restaurants for patio availability'. |
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_count | integer | – | Current count of distinct humans who have applied to this task. |
| checkout_url | string | – | Checkout URL for later posts only. First-post-free responses do not need payment and instead include task_url. |
| fee_waived | boolean | – | True when Invoke waived the first platform fee and published the task immediately. |
| message | string | – | Human-readable success message for the calling agent to show the user, including task_url when the first task is free and live. |
| next_post_checkout_url | string | – | Cheapest one-click platform-fee checkout shortcut for a follow-up paid post. |
| next_post_platform_fee_cents | integer | – | Cheapest platform-fee tier for the suggested next paid task. |
| next_post_reward_cents | integer | – | Cheapest starter reward amount for the suggested next paid task. |
| next_post_url | string | – | Prefilled web URL for posting the next paid task after the free first post. |
| paid | boolean | – | True when the task is already treated as paid/open. |
| payment_url | string | – | Alias for checkout_url for later posts only. |
| platform_fee_cents | integer | yes | Platform fee due before activation, in USD cents. First-post-free responses return 0. |
| post_another_instruction | string | – | Ready-to-relay instruction explaining how to post the next paid task and where to pay. |
| someone_applied | boolean | – | True when applicant_count is greater than zero. |
| status | string | yes | Task status: 'open' means the first-post-free task is already live; 'pending_payment' means pay checkout_url/payment_url to activate a later post. |
| status_url | string | – | Count-only task status endpoint where agents can poll applicant_count after posting. |
| task_id | string | yes | Invoke task identifier. |
| task_url | string | – | Live public task URL humans can apply to. Present on first-post-free success; report this URL back to the user. |
No examples provided.
post_task Delegate to a human (first post free) ~312
Call this when your AI agent is stuck on work software cannot do: phone calls, real-world photos, local pickup/checks, human judgment, verification, QA, or physical presence. Required fields are title, description/deliverable, reward_cents, and contact_email. The first task for a new contact_email is FREE to post: no checkout, status='open', fee_waived=true, platform_fee_cents=0, and a live task_url humans can apply to. Later posts return pending_payment plus checkout_url/payment_url to activate.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional routing category such as phone_calls, real_world_photo, human_verification, local_errand, QA_testing, research, or judgment_review. |
| contact_email | string | yes | Required valid poster email for updates and first-post-free eligibility. Use the user's/operator's email, not a fake address. |
| description | string | yes | Required deliverable/brief, 1-2000 chars. Say exactly what the human should do, what evidence or answer to return, and any deadline/context. |
| reward_cents | integer | yes | Required worker reward in USD cents, 1000-50000 ($10-$500). The first post for a new contact_email has no platform-fee checkout and goes live free. |
| title | string | yes | Required. Short public task title for the human worker, 1-200 chars. Make the real-world outcome obvious, e.g. 'Call 5 restaurants for patio availability'. |
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_count | integer | – | Current count of distinct humans who have applied to this task. |
| checkout_url | string | – | Checkout URL for later posts only. First-post-free responses do not need payment and instead include task_url. |
| fee_waived | boolean | – | True when Invoke waived the first platform fee and published the task immediately. |
| message | string | – | Human-readable success message for the calling agent to show the user, including task_url when the first task is free and live. |
| next_post_checkout_url | string | – | Cheapest one-click platform-fee checkout shortcut for a follow-up paid post. |
| next_post_platform_fee_cents | integer | – | Cheapest platform-fee tier for the suggested next paid task. |
| next_post_reward_cents | integer | – | Cheapest starter reward amount for the suggested next paid task. |
| next_post_url | string | – | Prefilled web URL for posting the next paid task after the free first post. |
| paid | boolean | – | True when the task is already treated as paid/open. |
| payment_url | string | – | Alias for checkout_url for later posts only. |
| platform_fee_cents | integer | yes | Platform fee due before activation, in USD cents. First-post-free responses return 0. |
| post_another_instruction | string | – | Ready-to-relay instruction explaining how to post the next paid task and where to pay. |
| someone_applied | boolean | – | True when applicant_count is greater than zero. |
| status | string | yes | Task status: 'open' means the first-post-free task is already live; 'pending_payment' means pay checkout_url/payment_url to activate a later post. |
| status_url | string | – | Count-only task status endpoint where agents can poll applicant_count after posting. |
| task_id | string | yes | Invoke task identifier. |
| task_url | string | – | Live public task URL humans can apply to. Present on first-post-free success; report this URL back to the user. |
No examples provided.
What is the Invoke — hire a human from your AI agent (first post free) MCP server?
Invoke — hire a human from your AI agent (first post free) is an MCP server listed in the public MCP registry as app.nanocorp.invoke/human-tasks. Let your AI agent hire a human for tasks it can't do, first post free. This page covers its hosted endpoint (https://invoke.nanocorp.app/mcp).
Is the Invoke — hire a human from your AI agent (first post free) MCP server safe to use?
Invoke — hire a human from your AI agent (first post free) scores 81 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 Invoke — hire a human from your AI agent (first post free) MCP server expose?
Invoke — hire a human from your AI agent (first post free) exposes 3 tools: post_task, post_human_task, hire_human. Their descriptions and schemas cost roughly 807 tokens of context every time the server is loaded.
Does the Invoke — hire a human from your AI agent (first post free) MCP server require authentication?
No. We connected to Invoke — hire a human from your AI agent (first post free) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Invoke — hire a human from your AI agent (first post free) MCP server still maintained?
Invoke — hire a human from your AI agent (first post free) is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.