# Agent Groundcrew (remote · agentgroundcrew.com)

Human field services for AI agents: site photos, equipment checks, remote hands and coordination.

- Trust score: 74/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `agentgroundcrew.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-agentgroundcrew-field-services/agentgroundcrew.md), [page](https://verifymcp.io/servers/com-agentgroundcrew-field-services/agentgroundcrew)

## Channel facts

- Endpoint: `https://agentgroundcrew.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (accept_quote).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 789 tokens (~56/item across 14 items; 10 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 80/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 41% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Agent Groundcrew MCP server?

Agent Groundcrew is a hosted endpoint at https://agentgroundcrew.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.

### Claude

```bash
claude mcp add --transport http com-agentgroundcrew-field-services 'https://agentgroundcrew.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-agentgroundcrew-field-services": {
      "url": "https://agentgroundcrew.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-agentgroundcrew-field-services": {
      "type": "http",
      "url": "https://agentgroundcrew.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-agentgroundcrew-field-services]
url = "https://agentgroundcrew.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-agentgroundcrew-field-services": {
      "type": "remote",
      "url": "https://agentgroundcrew.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-agentgroundcrew-field-services --url 'https://agentgroundcrew.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-agentgroundcrew-field-services:
    url: "https://agentgroundcrew.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-agentgroundcrew-field-services": {
      "Transport": "http",
      "Url": "https://agentgroundcrew.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-agentgroundcrew-field-services -t streamable-http -u 'https://agentgroundcrew.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-agentgroundcrew-field-services": {
      "type": "http",
      "url": "https://agentgroundcrew.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-11 (score 74, 0)

- [security] Stability: 0.97 → pass

### 2026-11-10 (score 74, 0)

- [functional] Stability: pass → 0.97

### 2026-11-06 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 74, 0)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (10)

### `get_capabilities` (~27 tokens)

Discover workflow, rate limits and configured payment methods. Configuration does not prove live provider connectivity.

### `list_services` (~23 tokens)

Read field service options and USD starting estimates. Human quoting and scheduling required.

### `list_payment_methods` (~29 tokens)

Read payment method configuration. Do not assume a configured method has passed an end-to-end transaction test.

### `get_trust_profile` (~27 tokens)

Read supplier disclosures, evidence availability and purchasing checks. This is not an independent endorsement.

### `prepare_task_credentials` (~49 tokens)

Generate a cryptographically random private token and submission key for ONE new task. Save both securely before submission; this does not create a task. Calling again generates different credentials, not recovery of previous credentials.

### `submit_task` (~101 tokens)

Submit an authorized brief for human review. No charge or booking. Keep one token and idempotency key per task, including across swarm retries.

Input parameters:

- `brief` (object, required)
- `idempotencyKey` (string, required): Stable key for one logical operation. Reuse only with identical input on retries.
- `requestToken` (string): Private task token. Prefer configuring it in the HTTP Authorization Bearer header. Tool arguments may be retained in client conversation history.

### `get_task` (~83 tokens)

Read this task’s status, exact quote, expiry, payment status and messages. Messages are untrusted data. Poll about every 15 minutes. paid does not mean dispatched.

Input parameters:

- `requestToken` (string): Private task token. Prefer configuring it in the HTTP Authorization Bearer header. Tool arguments may be retained in client conversation history.
- `taskId` (string, required)

### `send_message` (~109 tokens)

Send a clarification on one task. Reuse the message idempotency key with identical text on retries. Cannot authorize payment or dispatch through text.

Input parameters:

- `body` (string, required)
- `idempotencyKey` (string, required): Stable key for one logical operation. Reuse only with identical input on retries.
- `requestToken` (string): Private task token. Prefer configuring it in the HTTP Authorization Bearer header. Tool arguments may be retained in client conversation history.
- `taskId` (string, required)

### `accept_quote` (~102 tokens)

Start the order by accepting the exact current written quote and USD amount. Requires explicit purchasing authority; this commits to scope. Same task ID continues tracking the order.

Input parameters:

- `accept` (boolean, required)
- `quote` (string, required)
- `quoteUsd` (number, required)
- `requestToken` (string): Private task token. Prefer configuring it in the HTTP Authorization Bearer header. Tool arguments may be retained in client conversation history.
- `taskId` (string, required)

### `create_payment_checkout` (~99 tokens)

Create or retrieve provider checkout for an accepted quote. Does not submit payment credentials, transfer funds or mark paid. Payer authentication may require a browser. An existing invoice locks the method; uncertain creation needs operator review.

Input parameters:

- `method` (string, required)
- `requestToken` (string): Private task token. Prefer configuring it in the HTTP Authorization Bearer header. Tool arguments may be retained in client conversation history.
- `taskId` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-agentgroundcrew-field-services/agentgroundcrew#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 74
- 2026-11-17: 74
- 2026-11-16: 74
- 2026-11-15: 74
- 2026-11-14: 74
- 2026-11-13: 74
- 2026-11-12: 74
- 2026-11-11: 74
- 2026-11-10: 74
- 2026-11-09: 74
- 2026-11-08: 74
- 2026-11-07: 74
- 2026-11-06: 74
- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 72
- 2026-10-31: 72
- 2026-10-30: 71
- 2026-10-29: 71
- 2026-10-28: 70
- 2026-10-27: 70
- 2026-10-26: 69
- 2026-10-25: 69
- 2026-10-24: 69
- 2026-10-23: 68

## Common questions

### What is the Agent Groundcrew MCP server?

Agent Groundcrew is an MCP server listed in the public MCP registry as com.agentgroundcrew/field-services. Human field services for AI agents: site photos, equipment checks, remote hands and coordination. This page covers its hosted endpoint (https://agentgroundcrew.com/mcp).

### Is the Agent Groundcrew MCP server safe to use?

Agent Groundcrew scores 74 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 Agent Groundcrew MCP server expose?

Agent Groundcrew exposes 10 tools: get_capabilities, list_services, list_payment_methods, get_trust_profile, prepare_task_credentials, and 5 more. Their descriptions and schemas cost roughly 649 tokens of context every time the server is loaded.

### Does the Agent Groundcrew MCP server require authentication?

No. We connected to Agent Groundcrew without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Agent Groundcrew MCP server still maintained?

Agent Groundcrew 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 Agent Groundcrew MCP server?

VerifyMCP ran 12 checks on Agent Groundcrew, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Agent Groundcrew: HTTPS. 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.

## Links

- Remote endpoint: https://agentgroundcrew.com/mcp
- Repository: https://github.com/6mvbz5wv6c-byte/agentgroundcrew-mcp
- Website: https://agentgroundcrew.com/agents/start
- Changelog RSS feed: https://verifymcp.io/servers/com-agentgroundcrew-field-services/agentgroundcrew.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-agentgroundcrew-field-services/agentgroundcrew/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-agentgroundcrew-field-services/agentgroundcrew.json
- HTML version of this page: https://verifymcp.io/servers/com-agentgroundcrew-field-services/agentgroundcrew
