Other · Remote MCP server
Hands for Agents
Human-operated physical world in the EU: make, assemble, measure, verify, ship.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.handsforagents/hands- Version
- 0.2.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-23
- Updated
- 2026-09-23
- Publisher
- com.handsforagents
- Namespace
- Namespace verified by the MCP Registry via the domain handsforagents.com · how
- Website
- handsforagents.com
- Repository
- github.com/handsforagents/handsforagents-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.handsforagents.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- handsforagents 1.30.0 · protocol 2025-06-18
- Tools discovered
- 5:
list_services,request_quote,create_task,get_status,confirm_delivery - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | handsforagents-mcp | 0.2.0 | stdio |
How to connect Hands for Agents
Hands for Agents is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.handsforagents.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: handsforagents-mcp version 0.2.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y handsforagents-mcp@0.2.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"hands": {
"command": "npx",
"args": [
"-y",
"handsforagents-mcp@0.2.0"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| HandoffIT asset management - track equipment, allocations, and digital responsibility terms for your team. | Remote · HTTPLive check: sign-in required |
| Handoff - shareable agent result pages + human-in-the-loop approval gatesFollowable agent result pages + human-in-the-loop yes/no approval gates before irreversible actions. | Remote · HTTP |
| Handoff MCP ServerDurable agent-to-agent handoffs and shared scratchpad for multi-agent workflows. | Remote · HTTPLive check: sign-in required |
| HandoverShared, versioned context that humans and AI agents can publish, review, annotate, and continue. | Remote · HTTPLive check: ✓ handshake |
| HandsetA business phone system for AI agents: send texts, place calls, read transcripts, buy numbers. | Local · stdio |
| HANRIA agent mandate checkCheck an agent action against its operator's mandate before acting: permit, deny or escalate. | Remote · HTTPLive check: ✓ handshake |
| HAPI MCP ServerHAPI MCP server: Dynamically exposes OpenAPI REST APIs as MCP tools for AI assistants. | Remote & Local · HTTP |
| HAPI Strava MCP ServerStrava MCP tools for AI: athletes, activities, segments, clubs, routes. Powered by HAPI MCP server. | Remote · HTTPLive check: ✓ handshake |