SHAR Production is an AI-hybrid video production studio. This MIT-licensed, read-only MCP server validates rights-aware production metadata manifests for agents and MCP-compatible clients.
It exposes validate_production_manifest. The tool accepts a manifest object, returns a releasability result, does not read local files, call networks, or publish data.
git clone https://github.com/SHARProduction/production-metadata-mcp.git
cd production-metadata-mcp
npm ci
node server.jsThe npm package name is reserved in the project metadata, but a public npm release is not currently available. Use the source installation above until a public package release is independently verifiable.
Homepage: https://sharprod.com/
The machine-readable structural contract is available at schema/production-manifest.schema.json. It mirrors the validator fields and deliberately distinguishes structural validity from the releasability policy for ights_status=unknown.
Checks required project metadata, production stage, and declared rights status. Does not read files, call networks, or publish data.
Inputs: manifest (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 1 tool
With only one tool, there is no possibility of confusing it with another. The tool's purpose is clearly defined in its description, leaving no ambiguity.
The single tool follows a clear verb_noun pattern: validate_production_manifest. There are no other tools to introduce inconsistency, so naming is perfectly coherent.
A single tool feels thin for a server named 'Metadata MCP,' which could imply a broader scope. However, the tool's narrowly defined validation purpose means one tool may be reasonable, but it falls in the borderline range.
The tool covers the core validation functionality for production metadata, checking project metadata, stage, and rights status. However, the server name suggests a broader metadata management role, so additional operations like retrieval or update might be expected, creating a minor gap.
Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
MCP compatibility and transport verification server.
