# objekts Production Desk (remote · mcp.objekts.ai)

AI/VFX, CGI, motion & animation production preflight by objekts: locks, continuity, PoCs, estimates.

- Trust score: 67/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `mcp.objekts.ai`: 67/100 (this document), [markdown](https://verifymcp.io/servers/ai-objekts-mcp-production-desk/mcp.md), [page](https://verifymcp.io/servers/ai-objekts-mcp-production-desk/mcp)

## Channel facts

- Endpoint: `https://mcp.objekts.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.3`

## 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**: 57/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 (submit_production_brief).
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 50/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1542 tokens (~220/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability check failed: schema churn in the 21 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 37% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 8 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 objekts Production Desk MCP server?

objekts Production Desk is a hosted endpoint at https://mcp.objekts.ai/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 ai-objekts-mcp-production-desk 'https://mcp.objekts.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-objekts-mcp-production-desk": {
      "url": "https://mcp.objekts.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-objekts-mcp-production-desk": {
      "type": "http",
      "url": "https://mcp.objekts.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-objekts-mcp-production-desk]
url = "https://mcp.objekts.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-objekts-mcp-production-desk": {
      "type": "remote",
      "url": "https://mcp.objekts.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-objekts-mcp-production-desk --url 'https://mcp.objekts.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-objekts-mcp-production-desk:
    url: "https://mcp.objekts.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-objekts-mcp-production-desk": {
      "Transport": "http",
      "Url": "https://mcp.objekts.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-objekts-mcp-production-desk -t streamable-http -u 'https://mcp.objekts.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-objekts-mcp-production-desk": {
      "type": "http",
      "url": "https://mcp.objekts.ai/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-10-23 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 56 to 60.

### 2026-10-21 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53.

### 2026-10-19 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 46.

### 2026-10-17 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 36 to 40.

### 2026-10-14 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 26 to 30.

### 2026-10-12 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 16 to 23.

### 2026-10-10 (score 61, +2)

No change was recorded against any check on this day. Stability & Change Management went from 6 to 16.

### 2026-10-07 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 6.

## MCP tools (7)

### `diagnose_production` (~193 tokens)

Diagnose visual production

Use the objekts Production Desk production-diagnosis engine for production-heavy visual work before proposing execution. It checks reference authority, hard locks, truth-layer routing, asset fitness, continuity, versioning, revision impact, readiness and the highest-value proof-of-concept. It does not estimate price, collect contact data, upload files or send anything externally. Populate only facts available from the user's current request/files; mark unknowns explicitly instead of inventing production facts. After the call, use visibleVerdict as the complete default answer: do not add a generic checklist or extra recommendations unless the user explicitly asks for a broader audit.

Input parameters:

- `assets` (array)
- `changes` (array)
- `deliverables` (array, required)
- `elementRoutes` (array)
- `objective` (string, required)
- `readiness` (object, required)
- `unknowns` (array)
- `versions` (array)

Output parameters:

- `responseContract` (object)
- `visibleVerdict` (object)

### `estimate_production` (~561 tokens)

Estimate visual production

Return a directional RUB production range and timeline only when the user explicitly asks about price, cost, budget, quote, or budget fit. This tool is read-only, non-binding, and never collects contact details or submits a brief. Choose WHOLE_PRODUCTION for a finished deliverable and BOUNDED_SHOT_POST for named shots/scenes/post work; use INFERRED when that scope is genuinely ambiguous, or SCENARIO for a clearly labeled hypothetical. For production diagnosis without pricing, use diagnose_production instead.

Input parameters:

- `assumptions` (array): Explicit factual assumptions used to make the estimate possible; do not invent client facts.
- `deadlineDays`: Calendar days available until delivery when known; null or omit when no deadline is supplied.
- `exclusions` (array): Work explicitly outside this estimate, especially live-action, rights, media, extra versions, or unrequested disciplines.
- `externalBidItems` (array): Known cost exposures that require third-party bids; these remain outside the automated production range.
- `includeDepartments` (array): Optional whitelist of departments to include when the requested estimate intentionally covers only selected disciplines.
- `mode` (string, required): ROM for an early range; SCOPED_ESTIMATE for a defined scope; BUDGET_FIT to compare scope with a target budget; DEADLINE_FIT to evaluate schedule pressure.
- `runtimeSeconds` (required): Final master runtime in seconds when known; null only when genuinely unknown.
- `scopeBasis` (string, required): One concise sentence stating exactly what the estimate includes and excludes from the priced object.
- `scopeDecision` (string, required): USER_EXPLICIT when the requested object is clear; SCENARIO for an explicitly labeled hypothetical; INFERRED only when scope is genuinely ambiguous, in which case no price is returned until clarified.
- `scopeEvidence` (string, required): Short evidence for the scope choice. For USER_EXPLICIT, copy a brief verbatim phrase from the user's request that identifies the priced object.
- `scopeType` (string, required): WHOLE_PRODUCTION prices the complete requested finished deliverable; BOUNDED_SHOT_POST prices only named shots, scenes, VFX, or post tasks.
- `targetBudgetMax`: Upper bound of the user's target budget in RUB for BUDGET_FIT; omit when no target ceiling is supplied.
- `targetBudgetMin`: Lower bound of the user's target budget in RUB for BUDGET_FIT; omit when no budget floor exists.
- `units` (array, required): Production line items that drive the estimate. Include every material discipline/unit being priced; each item explains quantity, complexity, locks, continuity, and basis.
- `versioning` (object): Version/adaptation workload beyond the master deliverable; distinguish simple exports from recomposition and new production.

Output parameters:

- `assumptions` (array)
- `budgetFit` (object)
- `confidence` (string)
- `costDrivers` (array)
- `currency` (string)
- `departments` (array)
- `exclusions` (array)
- `mode` (string)
- `rangeMax` (number)
- `rangeMin` (number)
- `runtimeSeconds`
- `scheduleFit` (object)
- `scopeBasis` (string)
- `scopeDecision` (string)
- `scopeEvidence` (string)
- `scopeType` (string)
- `timelineMaxDays` (integer)
- `timelineMinDays` (integer)
- `unknownCostExposure` (object)

### `create_upload_session` (~92 tokens)

Prepare production file upload

Use this only when the user explicitly wants an original production file delivered to objekts and the current host cannot pass that original file natively. It creates a short-lived private upload URL. Do not use it merely to analyze files that are already available in the conversation.

Input parameters:

- `confirmed` (boolean, required)
- `filename` (string, required)
- `mediaType` (string, required)
- `sizeBytes` (integer, required)

Output parameters:

- `expiresAt` (string)
- `uploadId` (string)
- `uploadUrl` (string)

### `submit_production_brief` (~148 tokens)

Send production brief to objekts

Use this only after the user explicitly confirms that the prepared production brief, one reply channel (email or Telegram), and selected files should be sent to objekts for human production review. A contactless human-review submission is not allowed because the producer must be able to answer the user. When the host already has the files, pass them through the files field instead of making the user upload them again. Do not use it for local analysis, estimation, or when the user has said not to send anything.

Input parameters:

- `brief` (object, required)
- `confirmed` (boolean, required)
- `contact` (object, required)
- `files` (array)
- `selectedAssetIds` (array)

Output parameters:

- `message` (string)
- `status` (string)
- `submissionId` (string)

### `get_production_brief_status` (~55 tokens)

Check production review status

Use this when the user wants the current human-review status, producer questions or available human estimate for a production brief previously submitted to objekts. It does not modify the submission.

Input parameters:

- `submissionId` (string, required)

Output parameters:

- `humanEstimate`
- `message` (string|null)
- `questions` (array)
- `status` (string)
- `submissionId` (string)

### `update_production_brief` (~129 tokens)

Update submitted production brief

Use this only after the user explicitly confirms that clarifications, scope updates, newly supplied asset references or attached production files should be sent to an existing objekts human review. When ChatGPT already has a requested file, pass it through the files field rather than creating a second upload. Do not use it to change a brief that exists only in the current conversation.

Input parameters:

- `addedAssetIds` (array)
- `answers` (object)
- `briefPatch` (object)
- `confirmed` (boolean, required)
- `files` (array)
- `submissionId` (string, required)

Output parameters:

- `humanEstimate`
- `message` (string|null)
- `questions` (array)
- `status` (string)
- `submissionId` (string)

### `delete_production_brief` (~54 tokens)

Delete submitted production brief

Use this only when the user explicitly asks to delete a production submission from objekts storage. This removes the stored submission record and is destructive.

Input parameters:

- `confirmed` (boolean, required)
- `submissionId` (string, required)

Output parameters:

- `deleted` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-objekts-mcp-production-desk/mcp#diagnostics

## Score history

- 2026-10-23: 67
- 2026-10-22: 66
- 2026-10-21: 66
- 2026-10-20: 65
- 2026-10-19: 65
- 2026-10-18: 64
- 2026-10-17: 64
- 2026-10-16: 63
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 62
- 2026-10-12: 62
- 2026-10-10: 61
- 2026-10-07: 59
- 2026-10-05: 58
- 2026-10-04: 58
- 2026-10-03: 57
- 2026-10-02: 57

## Common questions

### What is the objekts Production Desk MCP server?

objekts Production Desk is an MCP server listed in the public MCP registry as ai.objekts.mcp/production-desk. AI/VFX, CGI, motion & animation production preflight by objekts: locks, continuity, PoCs, estimates. This page covers its hosted endpoint (https://mcp.objekts.ai/mcp).

### Is the objekts Production Desk MCP server safe to use?

objekts Production Desk scores 67 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 objekts Production Desk MCP server expose?

objekts Production Desk exposes 7 tools: diagnose_production, estimate_production, create_upload_session, submit_production_brief, get_production_brief_status, and 2 more. Their descriptions and schemas cost roughly 1,232 tokens of context every time the server is loaded.

### Does the objekts Production Desk MCP server require authentication?

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

### Is the objekts Production Desk MCP server still maintained?

objekts Production Desk 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://mcp.objekts.ai/mcp
- Repository: https://github.com/peach420fuzz/objekts-production-desk
- Website: https://objekts.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-objekts-mcp-production-desk/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-objekts-mcp-production-desk/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-objekts-mcp-production-desk/mcp