# Field Ops (remote · field-ops.filnith.workers.dev)

AI agents hire a human to observe, log or film on site. Typed results, feasibility before payment.

- Trust score: 58/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `field-ops.filnith.workers.dev`: 58/100 (this document), [markdown](https://verifymcp.io/servers/filnith-field-ops/field-ops.md), [page](https://verifymcp.io/servers/filnith-field-ops/field-ops)

## Channel facts

- Endpoint: `https://field-ops.filnith.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.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-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 287 tokens (~71/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 79/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 38% 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.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Field Ops MCP server?

Field Ops is a hosted endpoint at https://field-ops.filnith.workers.dev/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 filnith-field-ops 'https://field-ops.filnith.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "filnith-field-ops": {
      "url": "https://field-ops.filnith.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "filnith-field-ops": {
      "type": "http",
      "url": "https://field-ops.filnith.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.filnith-field-ops]
url = "https://field-ops.filnith.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "filnith-field-ops": {
      "type": "remote",
      "url": "https://field-ops.filnith.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add filnith-field-ops --url 'https://field-ops.filnith.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  filnith-field-ops:
    url: "https://field-ops.filnith.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "filnith-field-ops": {
      "Transport": "http",
      "Url": "https://field-ops.filnith.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add filnith-field-ops -t streamable-http -u 'https://field-ops.filnith.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "filnith-field-ops": {
      "type": "http",
      "url": "https://field-ops.filnith.workers.dev/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-09-19 (score 58, +1)

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

### 2026-09-16 (score 57, +1)

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

### 2026-09-15 (score 56, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-14 (score 56)

First indexed and scored.

## MCP tools (4)

### `capabilities` (~26 tokens)

Coverage areas, accepted question and shot types, refusal reasons declared up front, pricing and guarantees.

### `check_feasibility` (~161 tokens)

Tells you BEFORE paying whether a request can be done, at what price and lead time, with an explicit refusal reason otherwise. Call this first. Modes: observe (closed questions, typed answers), watch (steerable log over a slot), capture (specified shots delivered under a licence).

Input parameters:

- `declared_purpose` (string, required): Required. What the result will be used for.
- `hours` (number): Mode watch.
- `license` (string): Mode capture: required. Sets the use granted and the price.
- `location` (object, required)
- `mode` (string): Defaults to observe.
- `questions` (array): Modes observe and watch.
- `shots` (array): Mode capture. An underspecified shot is refused at feasibility.

### `order` (~79 tokens)

Places an order. Returns a payment requirement when no proof is supplied.

Input parameters:

- `deadline` (string)
- `declared_purpose` (string, required)
- `hours` (number)
- `license` (string)
- `location` (object, required)
- `mode` (string)
- `questions` (array)
- `shots` (array)

### `mission_status` (~21 tokens)

Status of a placed mission.

Input parameters:

- `mission` (string, required)

## Diagnostics

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

## Score history

- 2026-09-20: 58
- 2026-09-19: 58
- 2026-09-18: 57
- 2026-09-17: 57
- 2026-09-16: 57
- 2026-09-15: 56
- 2026-09-14: 56

## Common questions

### What is the Field Ops MCP server?

Field Ops is an MCP server listed in the public MCP registry as io.github.Filnith/field-ops. AI agents hire a human to observe, log or film on site. Typed results, feasibility before payment. This page covers its hosted endpoint (https://field-ops.filnith.workers.dev/mcp).

### Is the Field Ops MCP server safe to use?

Field Ops scores 58 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 Field Ops MCP server expose?

Field Ops exposes 4 tools: capabilities, check_feasibility, order, mission_status. Their descriptions and schemas cost roughly 287 tokens of context every time the server is loaded.

### Does the Field Ops MCP server require authentication?

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

### Is the Field Ops MCP server still maintained?

Field Ops is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://field-ops.filnith.workers.dev/mcp
- Website: https://field-ops.filnith.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/filnith-field-ops/field-ops.xml
- Changelog JSON feed: https://verifymcp.io/servers/filnith-field-ops/field-ops.json
- HTML version of this page: https://verifymcp.io/servers/filnith-field-ops/field-ops