MCP server for recording and managing user-generated content (UGC) licensing rights and clearances
This server has a single tool (record_ugc_rights_clearance) with a reasonable name and basic schema visible in client.py. However, the implementation is fundamentally broken for MCP: the server code in mcp_server.py does not register the tool properly, does not implement the MCP protocol, and does not map incoming MCP requests to the client.py implementation. The tool definition itself has moderate quality, the name is action-based (record_*), the description is present (103 chars, in baseline range), and input parameters have types and descriptions. However, the schema lacks critical documentation about the license_scope enum values, parameter constraints, and output schema details. The tool is defined in isolation in client.py with hardcoded default values, not as part of a proper MCP tool registry. The mcp_server.py file merely prints a static JSON banner and does nothing to handle actual MCP protocol requests. This is evidence-based: searching the codebase reveals no MCP request/response handling, no tool invocation dispatcher, and no connection between the declared tool and the server loop.
Records user-generated content licensing rights clearance with creator consent verification and generates an immutable rights certificate
MCP protocol not implemented. mcp_server.py prints a static JSON banner and does not handle MCP JSON-RPC requests, tool invocation dispatches, or request/response cycles. The tool exists only as a Python class method in client.py with no bridge to MCP.
No output schema documented. The tool returns a dict with fields (rights_entry_id, media_asset_hash, license_tier, creator_consent_verified, expiration_timestamp_iso, immutable_rights_certificate_url), but the schema response structure is not declared in the tool definition. LLMs cannot plan downstream steps without knowing output field names and types.
license_scope parameter lacks enum constraint and validation. The description mentions example value 'GLOBAL_DIGITAL_PAID_MEDIA_12MO' but does not declare valid enum values (e.g., what other scopes are permitted?). This invites hallucinated invalid values from LLMs.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | 2026-07-28+ | v2 |
No error handling guidance. The tool returns hardcoded success values only. No error cases documented: What if the media asset URL is invalid? What if creator_handle is not found? What if license_scope is unsupported? LLMs have no recovery path if a call fails.
No idempotency or confirmation step. This is a WRITE tool (recording rights clearance and issuing certificates). Agents may retry on network failures or ambiguity, risking duplicate rights entries. No dry-run or confirmation pattern present.
Parameter descriptions lack actionable constraints. 'creator_handle' description says 'e.g., @alex_creates' but does not specify required format (@ prefix? length? allowed characters?). Agents cannot reliably format this parameter without explicit constraints.