Body for Agents
REMOTE · BODYFORAGENTS.COM
Connect AI agents to discover services and coordinate real-world tasks.
Available components
Last scanned (13 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Workflow Automation
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 Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 327 tokens (~81/item across 4 items; 3 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
- Resource “Current conversation history” now points somewhere else: conversation://mcp-inquiry-c97b877e-c0bb-4d22-adbf-f0520fa59c93 → conversation://mcp-inquiry-7209a4e3-9cc9-4d32-ba51-043d7e178bbb security
- 20 Nov 26 0
- Resource “Current conversation history” now points somewhere else: conversation://mcp-inquiry-fc5bcdcb-684d-4d1e-a667-8cf1d882ecc4 → conversation://mcp-inquiry-c97b877e-c0bb-4d22-adbf-f0520fa59c93 security
- 19 Nov 26 +1
- The server changed its declared name: Hands for Agents → Body for Agents security
- Tool “request_human_task” rewrote its description, which is the text the model reads security
- Schema quality: 78 → 327 ▼ functional
- The server no longer declares the “logging” capability functional
- First check of Schema quality: 100 functional
- New prompt “task_intake” functional
- New resource “Current conversation history” functional
- Server version: 1.0.0 → 2.0.0 functional
- New tool “get_task_status” functional
- New tool “start_task_inquiry” functional
- “request_human_task” added an optional parameter “contextId” cosmetic
- “request_human_task” added an optional parameter “taskId” cosmetic
- “request_human_task” reworded the description of “task” cosmetic
- 18 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 61
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 21 Nov 2026 · Probed https://bodyforagents.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bodyforagents.com | CN=WE1,O=Google Trust Services,C=US | 15 Nov 2026 | 13 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | bc6d9308e5093be713925934ff590efe |
| SANs: bodyforagents.com, a2a.bodyforagents.com, *.a2a.bodyforagents.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of bodyforagents.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| bodyforagents.com. | DS published | 2371 | 13 | Verified |
| bodyforagents.com. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bodyforagents.com/mcp | Verified | 200 | |
| http (plaintext) | http://bodyforagents.com/mcp | Served over HTTP | 200 |
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 →
get_task_status ~39
Check the current status of a previously submitted task.
| Name | Type | Req | Description |
|---|---|---|---|
| taskId | string | yes | The task ID returned from a previous request_human_task call. |
No output schema declared.
No examples provided.
request_human_task ~165
Submit a real-world task for human execution. Supports multi-turn: if the response is input_required, ask the user the question, then call again with their answer and the same taskId and contextId. When all details are provided (goal, location, deadline, deliverables), returns status ready with a sales response and payment instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| contextId | string | – | Conversation context identifier. Reuse the same value across multi-turn exchanges to maintain history. |
| task | string | yes | The task description. Include as much detail as possible: what to do, where, by when, and what deliverables are expected. |
| taskId | string | – | Unique task identifier. Generate one on first call. Reuse the same value on follow-up calls to maintain conversation context. |
No output schema declared.
No examples provided.
start_task_inquiry ~109
Begin a multi-turn task intake conversation. The service analyzes the task description and asks follow-up questions if needed. Reuse the same contextId across turns. Returns status ready when all essential fields (goal, location, deadline, deliverables) are provided.
| Name | Type | Req | Description |
|---|---|---|---|
| additional_info | string | – | Supplementary information to add to the task description. |
| contextId | string | – | Conversation context identifier. Reuse across multi-turn exchanges. |
| task | string | yes | The task description or additional details. |
No output schema declared.
No examples provided.
How do I install the Body for Agents MCP server?
Body for Agents is a hosted endpoint at https://bodyforagents.com/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 · bodyforagents.com
claude mcp add --transport http com-bodyforagents-mcp 'https://bodyforagents.com/mcp'
What is the Body for Agents MCP server?
Body for Agents is an MCP server listed in the public MCP registry as com.bodyforagents/mcp. Connect AI agents to discover services and coordinate real-world tasks. This page covers its hosted endpoint (https://bodyforagents.com/mcp).
Is the Body for Agents MCP server safe to use?
Body for Agents scores 64 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 Body for Agents MCP server expose?
Body for Agents exposes 3 tools: request_human_task, start_task_inquiry, get_task_status. Their descriptions and schemas cost roughly 313 tokens of context every time the server is loaded.
Does the Body for Agents MCP server require authentication?
No. We connected to Body for Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Body for Agents MCP server still maintained?
Body for Agents is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Body for Agents MCP server?
VerifyMCP ran 12 checks on Body for Agents, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Body for Agents: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.