Skip to content

objekts Production Desk MCP server

ai.objekts.mcp/production-deskmcp.objekts.aistreamable-httpv0.1.3Scanned

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

7 tools: 3 can delete or cancel things, 2 change things and 2 only read.

Tools: 3 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the objekts Production Desk MCP server can do

The objekts Production Desk MCP server is published by mcp.objekts.ai, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (3 tools: submit_production_brief, update_production_brief and delete_production_brief) and create or change data (2 tools: diagnose_production and create_upload_session). 2 tools only read.

3 tools bring in text other people can write (submit_production_brief, get_production_brief_status and update_production_brief).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 0.1.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Deletes or cancels 3Claude Code: deny
  • delete_production_briefUse this only when the user explicitly asks to delete a production submission from objekts storage.No findings

    Why it is in this group

    • The name "delete_production_brief" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • submit_production_briefUse 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 p…Reads text others writeNo findings

    Why it is in this group

    • The name "submit_production_brief" says "submit": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • update_production_briefUse 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 obje…Reads text others writeNo findings

    Why it is in this group

    • The name "update_production_brief" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 2Claude Code: ask
  • create_upload_sessionUse this only when the user explicitly wants an original production file delivered to objekts and the current host cannot pass that original file natively.No findings

    Why it is in this group

    • The name "create_upload_session" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • diagnose_productionUse the objekts Production Desk production-diagnosis engine for production-heavy visual work before proposing execution.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
Only reads 2Show 2 read-only tools
  • estimate_productionReturn a directional RUB production range and timeline only when the user explicitly asks about price, cost, budget, quote, or budget fit.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • get_production_brief_statusUse this when the user wants the current human-review status, producer questions or available human estimate for a production brief previously submitted to objekts.Reads text others writeNo findings

    Why it is in this group

    • The name "get_production_brief_status" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:26 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (3 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.objekts.ai/mcp: tools/list returned 7 tools to an anonymous client, including submit_production_brief (destructive), update_production_brief (destructive), delete_production_brief (destructive), diagnose_production (write), create_upload_session (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http production-desk https://mcp.objekts.ai/mcp
claude mcp add --transport http production-desk https://mcp.objekts.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__production-desk__estimate_production",
      "mcp__production-desk__get_production_brief_status"
    ],
    "ask": [
      "mcp__production-desk__diagnose_production",
      "mcp__production-desk__create_upload_session"
    ],
    "deny": [
      "mcp__production-desk__submit_production_brief",
      "mcp__production-desk__update_production_brief",
      "mcp__production-desk__delete_production_brief"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as production-desk. Review it before you use it.

Capability tags behind 3 rules
  • mcp__production-desk__submit_production_brief untrusted-input
  • mcp__production-desk__get_production_brief_status untrusted-input
  • mcp__production-desk__update_production_brief untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.objekts.mcp/production-desk/verify?hash=921e2407441c89278dfb3376e4fb0c1a3265d0f05e4bab4af45f151c3a8126e8" | jq -e '.changed == false'

Pinned hash 921e2407441c, from Nov 10, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.objekts.mcp/production-desk/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.objekts.mcp/production-desk
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.objekts.mcp/production-desk.svg)](https://radar.anlyon.com/servers/ai.objekts.mcp/production-desk)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:42 UTC.

objekts Production Desk MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the objekts Production Desk MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the objekts Production Desk MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: submit_production_brief, update_production_brief and delete_production_brief.

Can the objekts Production Desk MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the objekts Production Desk MCP server have?

7 tools: 3 destructive, 2 write, 2 read. submit_production_brief, update_production_brief, delete_production_brief, diagnose_production, create_upload_session, estimate_production and get_production_brief_status.

Does the objekts Production Desk MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the objekts Production Desk MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the objekts Production Desk MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.