# Shoot Plan (remote · theamateur.co.uk)

Practical filming plans for AI assistants. Shot-plan checks are not yet available to customers.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `theamateur.co.uk`: 73/100 (this document), [markdown](https://verifymcp.io/servers/uk-co-theamateur-shoot-plan/mcp-shoot-plan.md), [page](https://verifymcp.io/servers/uk-co-theamateur-shoot-plan/mcp-shoot-plan)

## Channel facts

- Endpoint: `https://theamateur.co.uk/mcp/shoot-plan`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `0.1.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-10-23.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1537 tokens (~139/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 76/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 18% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Shoot Plan MCP server?

Shoot Plan is a hosted endpoint at https://theamateur.co.uk/mcp/shoot-plan, 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 uk-co-theamateur-shoot-plan 'https://theamateur.co.uk/mcp/shoot-plan'
```

### Cursor

```json
{
  "mcpServers": {
    "uk-co-theamateur-shoot-plan": {
      "url": "https://theamateur.co.uk/mcp/shoot-plan"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "uk-co-theamateur-shoot-plan": {
      "type": "http",
      "url": "https://theamateur.co.uk/mcp/shoot-plan"
    }
  }
}
```

### Codex

```toml
[mcp_servers.uk-co-theamateur-shoot-plan]
url = "https://theamateur.co.uk/mcp/shoot-plan"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "uk-co-theamateur-shoot-plan": {
      "type": "remote",
      "url": "https://theamateur.co.uk/mcp/shoot-plan",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add uk-co-theamateur-shoot-plan --url 'https://theamateur.co.uk/mcp/shoot-plan' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  uk-co-theamateur-shoot-plan:
    url: "https://theamateur.co.uk/mcp/shoot-plan"
```

### Netclaw

```json
{
  "McpServers": {
    "uk-co-theamateur-shoot-plan": {
      "Transport": "http",
      "Url": "https://theamateur.co.uk/mcp/shoot-plan"
    }
  }
}
```

### Vellum

```bash
assistant mcp add uk-co-theamateur-shoot-plan -t streamable-http -u 'https://theamateur.co.uk/mcp/shoot-plan'
```

### Other

```json
{
  "mcpServers": {
    "uk-co-theamateur-shoot-plan": {
      "type": "http",
      "url": "https://theamateur.co.uk/mcp/shoot-plan"
    }
  }
}
```

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-10-23 (score 73, +1)

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

### 2026-10-21 (score 72, +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-10-20 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-19 (score 71)

First indexed and scored.

## MCP tools (11)

### `shoot_plan_capabilities` (~23 tokens)

What Shoot Plan offers

Return truthful Shoot Plan scope, availability, privacy and commercial state.

### `shoot_plan_example` (~24 tokens)

See the example plan

Return a synthetic example plan generated by the real planner, with its provenance.

### `shoot_plan_quote` (~148 tokens)

Get a price

Calculate a deterministic public quote from non-private project metadata. Do not send a script or brief.

Input parameters:

- `coverageNeeds` (array)
- `equipment` (array)
- `locationCount` (integer, required)
- `noAiImagery`: Legacy compatibility field; omit or send true. The customer films their own material.
- `orientation` (string, required)
- `ownFootageOnly`: Customer films their own material. Same meaning as noAiImagery; omit or send true.
- `peopleCount` (integer, required)
- `projectType` (string, required)
- `sceneCount` (integer, required)
- `shootMinutes` (integer, required)
- `targetRuntimeSeconds` (integer, required)

### `shoot_plan_create` (~65 tokens)

Create a plan

Create a plan for an authenticated organisation after authoritative payment confirmation.

Input parameters:

- `idempotencyKey` (string, required)
- `intake` (required)
- `orderId` (string, required): The order id, or the customer-facing order reference shown on the website (for example A140A800).

### `shoot_plan_list` (~82 tokens)

List your plans

List the authenticated organisation's Shoot Plans, most recently changed first, without returning private intake or full plan content. Archived plans are left out unless includeArchived is true. Each plan's taskId is the ID every other plan tool takes. Structured result: {plans:[...]}.

Input parameters:

- `includeArchived` (boolean): Also list plans the owner archived. Default false.

Output parameters:

- `message` (string)
- `plans` (array)

### `shoot_plan_status` (~96 tokens)

Check a plan's progress

Return a plan's status, version, whether its included revision is used, its customer-facing order reference, and progress (essential shots ticked, next shot, when the last tick was made). Read-only. Use the full taskId from shoot_plan_list (not planId). A unique eight-character task prefix or orderReference also works. Connections see only their own live or owner-test plans.

Input parameters:

- `taskId` (string, required)

### `shoot_plan_get` (~151 tokens)

Open a plan

Return a full plan: shots in filming order (priority must = essential), setup groups per location or visit, checklist, coverage risks, progress (item keys already ticked), progressSummary with counts, each tick's time and source (web, field or agent), and timeSummary when the plan has timing. Structured shots have a unique title and whole filming minutes (at least 1); older free-text shots omit both. Use a shot's shotId for progress. Read-only. Use the full taskId from shoot_plan_list (not planId). A unique eight-character task prefix or orderReference also works. Connections see only their own live or owner-test plans.

Input parameters:

- `taskId` (string, required)

Output parameters:

- `plan` (object)

### `shoot_plan_timing` (~116 tokens)

Compare planned and actual time

Structured plans only (not older free-text plans). Compare planned and actual filming time between consecutive ticks in field mode. plannedSeconds is the planned time of those measured tick-to-tick steps, not the whole plan; planPlannedSeconds is the whole plan's planned shot work when present. Read-only. Use the full taskId from shoot_plan_list (not planId). A unique eight-character task prefix or orderReference also works. Connections see only their own live or owner-test plans.

Input parameters:

- `taskId` (string, required)

### `shoot_plan_revise` (~182 tokens)

Use the included revision

Use the plan's one included revision. This cannot be undone and uses the allowance, so call shoot_plan_revision_preview first and confirm with the person. For structured plans, change filming time or transfer time (constraintUpdates.availableMinutes, locationTransferMinutes), framing, or structuredChanges. Use the full taskId from shoot_plan_list (not planId). A unique eight-character task prefix or orderReference also works. Connections see only their own live or owner-test plans.

Input parameters:

- `audioPriority` (string)
- `constraintUpdates` (object)
- `framingMode` (string)
- `idempotencyKey` (string, required)
- `replacementBeats` (array)
- `request` (string, required)
- `structuredChanges` (object): Structured plans only: typed changes that stay within the plan's scope.
- `taskId` (string, required)

### `shoot_plan_revision_preview` (~172 tokens)

Preview a revision

Structured plans only; older free-text plans cannot be previewed. Preview a revision without using it: what would change, which checked shots would be cleared, and whether it still fits. For example constraintUpdates.availableMinutes: 30 answers "what if I only had 30 minutes?". Never uses the included revision. Use the full taskId from shoot_plan_list (not planId). A unique eight-character task prefix or orderReference also works. Connections see only their own live or owner-test plans.

Input parameters:

- `audioPriority` (string)
- `constraintUpdates` (object)
- `framingMode` (string)
- `replacementBeats` (array)
- `structuredChanges` (object): Structured plans only: typed changes that stay within the plan's scope.
- `taskId` (string, required)

### `shoot_plan_progress_sync` (~184 tokens)

Tick off shots

Tick or untick shots and checklist items. Each op: itemKey "shot:<shotId>" or "check:<itemId>" from shoot_plan_get, basePlanVersion = the plan's version, a new random UUID v4 as opId, state "complete" or "incomplete". Retry-safe: resending the same opId does nothing twice. An op made against an older basePlanVersion still applies when that item is unchanged in the current version; otherwise its result is item_changed_in_current_version and nothing changes. Ticking records that the person checked the shot, not its technical quality. Use the full taskId from shoot_plan_list (not planId). A unique eight-character task prefix or orderReference also works. Connections see only their own live or owner-test plans.

Input parameters:

- `ops` (array, required)
- `taskId` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/uk-co-theamateur-shoot-plan/mcp-shoot-plan#diagnostics

## Score history

- 2026-10-23: 73
- 2026-10-22: 72
- 2026-10-21: 72
- 2026-10-20: 71
- 2026-10-19: 71

## Common questions

### What is the Shoot Plan MCP server?

Shoot Plan is an MCP server listed in the public MCP registry as uk.co.theamateur/shoot-plan. Practical filming plans for AI assistants. Shot-plan checks are not yet available to customers. This page covers its hosted endpoint (https://theamateur.co.uk/mcp/shoot-plan).

### Is the Shoot Plan MCP server safe to use?

Shoot Plan scores 73 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 Shoot Plan MCP server expose?

Shoot Plan exposes 11 tools: shoot_plan_capabilities, shoot_plan_example, shoot_plan_quote, shoot_plan_create, shoot_plan_list, and 6 more. Their descriptions and schemas cost roughly 1,243 tokens of context every time the server is loaded.

### Does the Shoot Plan MCP server require authentication?

Yes. Shoot Plan asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Shoot Plan MCP server still maintained?

Shoot Plan is still listed as active in the MCP registry. We last reached this channel on 23 October 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://theamateur.co.uk/mcp/shoot-plan
- Website: https://theamateur.co.uk/developers/shoot-plan/
- Changelog RSS feed: https://verifymcp.io/servers/uk-co-theamateur-shoot-plan/mcp-shoot-plan.xml
- Changelog JSON feed: https://verifymcp.io/servers/uk-co-theamateur-shoot-plan/mcp-shoot-plan.json
- HTML version of this page: https://verifymcp.io/servers/uk-co-theamateur-shoot-plan/mcp-shoot-plan