Shoot Plan
REMOTE · THEAMATEUR.CO.UK
Practical filming plans for AI assistants. Shot-plan checks are not yet available to customers.
Available components
Last scanned (17 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Design and Media
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- 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 Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 18% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 23 Oct 26 +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.
- 21 Oct 26 +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.
- 20 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 19 Oct 26 71
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 23 Oct 2026 · Probed https://theamateur.co.uk/mcp/shoot-plan
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=theamateur.co.uk | CN=YE1,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6ac0706291ce2a70103ed3961180bc90eeb |
| SANs: theamateur.co.uk | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of theamateur.co.uk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | present | 43876 | 8 | Verified |
| co.uk. | present | 11810 | 8 | Verified |
| theamateur.co.uk. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="Shoot Plan", error="invalid_token", error_description="Use your Shoot Plan connection link or key"
Bearer realm="Shoot Plan", error="invalid_token", error_description="Use your Shoot Plan connection link or key"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'none'; style-src 'self'; img-src 'self' data:; connect-src 'self'; font-src 'self'; object-src 'none'; base-uri 'none'; frame-ancestors 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://theamateur.co.uk/mcp/shoot-plan | Verified | 200 | |
| http (plaintext) | http://theamateur.co.uk/mcp/shoot-plan | HTTPS enforced | 308 | https://theamateur.co.uk/mcp/shoot-plan |
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 →
shoot_plan_capabilities What Shoot Plan offers ~23
Return truthful Shoot Plan scope, availability, privacy and commercial state.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
shoot_plan_create Create a plan ~65
Create a plan for an authenticated organisation after authoritative payment confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | yes | – |
| intake | – | yes | – |
| orderId | string | yes | The order id, or the customer-facing order reference shown on the website (for example A140A800). |
Structured output declared, but exposes no named fields.
No examples provided.
shoot_plan_example See the example plan ~24
Return a synthetic example plan generated by the real planner, with its provenance.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
shoot_plan_get Open a plan ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| taskId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| plan | object | yes | – |
No examples provided.
shoot_plan_list List your plans ~82
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:[...]}.
| Name | Type | Req | Description |
|---|---|---|---|
| includeArchived | boolean | – | Also list plans the owner archived. Default false. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| plans | array | yes | – |
No examples provided.
shoot_plan_progress_sync Tick off shots ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ops | array | yes | – |
| taskId | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shoot_plan_quote Get a price ~148
Calculate a deterministic public quote from non-private project metadata. Do not send a script or brief.
| Name | Type | Req | Description |
|---|---|---|---|
| coverageNeeds | array | – | – |
| equipment | array | – | – |
| locationCount | integer | yes | – |
| noAiImagery | – | – | Legacy compatibility field; omit or send true. The customer films their own material. |
| orientation | string | yes | – |
| ownFootageOnly | – | – | Customer films their own material. Same meaning as noAiImagery; omit or send true. |
| peopleCount | integer | yes | – |
| projectType | string | yes | – |
| sceneCount | integer | yes | – |
| shootMinutes | integer | yes | – |
| targetRuntimeSeconds | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shoot_plan_revise Use the included revision ~182
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.
| Name | Type | Req | Description |
|---|---|---|---|
| audioPriority | string | – | – |
| constraintUpdates | object | – | – |
| framingMode | string | – | – |
| idempotencyKey | string | yes | – |
| replacementBeats | array | – | – |
| request | string | yes | – |
| structuredChanges | object | – | Structured plans only: typed changes that stay within the plan's scope. |
| taskId | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shoot_plan_revision_preview Preview a revision ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| audioPriority | string | – | – |
| constraintUpdates | object | – | – |
| framingMode | string | – | – |
| replacementBeats | array | – | – |
| structuredChanges | object | – | Structured plans only: typed changes that stay within the plan's scope. |
| taskId | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shoot_plan_status Check a plan's progress ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| taskId | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shoot_plan_timing Compare planned and actual time ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| taskId | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.
remote · theamateur.co.uk
claude mcp add --transport http uk-co-theamateur-shoot-plan 'https://theamateur.co.uk/mcp/shoot-plan'
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.