What should a reseller expose through a public MCP catalogue?

**What belongs in a public discovery response?**

A reseller can publish the task family's purpose, domain, supported formats, schema version, included exception types and a clear statement that the commercial material is generated. A small preview can show record relationships when its distribution has been agreed.

**Should an MCP response include evaluation answers?**

Treat answer keys as a separate artefact. Publishing them beside public task inputs can compromise later evaluations and expose material outside the intended access scope. Discovery metadata can state that scoring resources exist without returning their contents.

**How should an AI client understand access limits?**

Use explicit fields for preview status, payload access requirements and permitted discovery actions. Do not rely on a paragraph hidden elsewhere in the catalogue to explain whether a returned object is a preview or the licensed release.

Before launch, inspect responses as an unauthenticated client and as an entitled customer. Check linked resources as well as the initial tool response. This is an integration and packaging review; public accessibility should never be treated as proof that all downstream uses have been licensed.