objekts Production Desk
REMOTE · MCP.OBJEKTS.AI
AI/VFX, CGI, motion & animation production preflight by objekts: locks, continuity, PoCs, estimates.
Available components
Last scanned (9 hours ago)
Scores higher than 56% 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (submit_production_brief). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability50
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability check failed: schema churn in the 21 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 37% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 56 to 60.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 46.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 36 to 40.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 26 to 30.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 16 to 23.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 6 to 16.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 6.
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://mcp.objekts.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=objekts.ai | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 385480bece607e5013a0ded908f772d9 |
| SANs: objekts.ai, mcp.objekts.ai, *.mcp.objekts.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.objekts.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| objekts.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.objekts.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.objekts.ai/mcp | HTTPS enforced | 301 | https://mcp.objekts.ai/mcp |
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 →
create_upload_session Prepare production file upload ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | – |
| filename | string | yes | – |
| mediaType | string | yes | – |
| sizeBytes | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| expiresAt | string | yes | – |
| uploadId | string | yes | – |
| uploadUrl | string | yes | – |
No examples provided.
delete_production_brief Delete submitted production brief ~54
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | – |
| submissionId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | yes | – |
No examples provided.
diagnose_production Diagnose visual production ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| assets | array | – | – |
| changes | array | – | – |
| deliverables | array | yes | – |
| elementRoutes | array | – | – |
| objective | string | yes | – |
| readiness | object | yes | – |
| unknowns | array | – | – |
| versions | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| responseContract | object | yes | – |
| visibleVerdict | object | yes | – |
No examples provided.
estimate_production Estimate visual production ~561
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | – | yes | Final master runtime in seconds when known; null only when genuinely unknown. |
| scopeBasis | string | yes | One concise sentence stating exactly what the estimate includes and excludes from the priced object. |
| scopeDecision | string | yes | 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 | yes | 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 | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| budgetFit | object | – | – |
| confidence | string | yes | – |
| costDrivers | array | yes | – |
| currency | string | yes | – |
| departments | array | yes | – |
| exclusions | array | yes | – |
| mode | string | yes | – |
| rangeMax | number | yes | – |
| rangeMin | number | yes | – |
| runtimeSeconds | – | yes | – |
| scheduleFit | object | – | – |
| scopeBasis | string | yes | – |
| scopeDecision | string | yes | – |
| scopeEvidence | string | yes | – |
| scopeType | string | yes | – |
| timelineMaxDays | integer | yes | – |
| timelineMinDays | integer | yes | – |
| unknownCostExposure | object | yes | – |
No examples provided.
get_production_brief_status Check production review status ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| submissionId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| humanEstimate | – | – | – |
| message | string|null | – | – |
| questions | array | yes | – |
| status | string | yes | – |
| submissionId | string | yes | – |
No examples provided.
submit_production_brief Send production brief to objekts ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | object | yes | – |
| confirmed | boolean | yes | – |
| contact | object | yes | – |
| files | array | – | – |
| selectedAssetIds | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| status | string | yes | – |
| submissionId | string | yes | – |
No examples provided.
update_production_brief Update submitted production brief ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| addedAssetIds | array | – | – |
| answers | object | – | – |
| briefPatch | object | – | – |
| confirmed | boolean | yes | – |
| files | array | – | – |
| submissionId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| humanEstimate | – | – | – |
| message | string|null | – | – |
| questions | array | yes | – |
| status | string | yes | – |
| submissionId | string | yes | – |
No examples provided.
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.
remote · mcp.objekts.ai
claude mcp add --transport http ai-objekts-mcp-production-desk 'https://mcp.objekts.ai/mcp'
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.