Hire verified people for real-world tasks in NYC, or sign up to earn doing them.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Ask Handflow for real-world work done by verified people (starting in New York City). Describe the task, place and time. Handflow replies by email with up to 3 options and the total in USD.
City where the work happens
Email where Handflow should reply
What needs doing, where, when, and any budget
Who will place the order. Defaults to "agent".
Language for our reply. Defaults to "en".
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http handflow https://handflow.io/mcp
Ask Handflow for real-world work done by verified people (starting in New York City). Describe the task, place and time. Handflow replies by email with up to 3 options and the total in USD.
| Argument | Type | Description |
|---|---|---|
| who | string | Who will place the order. Defaults to "agent". |
| city* | string | City where the work happens |
| lang | string | Language for our reply. Defaults to "en". |
| email* | string | Email where Handflow should reply |
| details* | string | What needs doing, where, when, and any budget |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"email",
"city",
"details"
],
"properties": {
"who": {
"enum": [
"me",
"agent"
],
"type": "string",
"description": "Who will place the order. Defaults to \"agent\"."
},
"city": {
"type": "string",
"description": "City where the work happens"
},
"lang": {
"enum": [
"en",
"es"
],
"type": "string",
"description": "Language for our reply. Defaults to \"en\"."
},
"email": {
"type": "string",
"description": "Email where Handflow should reply"
},
"details": {
"type": "string",
"description": "What needs doing, where, when, and any budget"
}
}
}Sign a person up to earn money doing real-world tasks with Handflow (starting in New York City). They set their own price and hours. Handflow emails them when there is work that fits.
| Argument | Type | Description |
|---|---|---|
| city* | string | City or neighborhood where they can work |
| lang | string | Language for our emails. Defaults to "en". |
| name* | string | The person's name |
| email* | string | Email where Handflow should write to them |
| details* | string | What they can do: skills, tools and availability |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"name",
"email",
"city",
"details"
],
"properties": {
"city": {
"type": "string",
"description": "City or neighborhood where they can work"
},
"lang": {
"enum": [
"en",
"es"
],
"type": "string",
"description": "Language for our emails. Defaults to \"en\"."
},
"name": {
"type": "string",
"description": "The person's name"
},
"email": {
"type": "string",
"description": "Email where Handflow should write to them"
},
"details": {
"type": "string",
"description": "What they can do: skills, tools and availability"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 11, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.