Check before submitting
Search by exact product name, canonical hostname, repository, package identifier, or MCP namespace. When a matching public record exists, save its URL and inspect ownership, endpoint, description, categories, and tool metadata before proposing a change.
This avoids duplicates. A record can be published yet absent from generic search; in that case, improve supported fields and test the directory rather than submitting the same app again.
Prepare an evidence-bounded listing
Use only capabilities visible on the product site, documentation, repository, packages, or live endpoint. Tailor the description to real user jobs and observed queries, but do not paste keyword lists or import desired features from those queries.
Some directories derive fields from registries or live MCP introspection. Identify the authority before editing: immutable registry metadata may require a new version, while tool schemas must be corrected at the endpoint.
Verify publication and retrieval separately
After the owner completes authentication or ownership verification, reopen the record and confirm URL, ownership state, endpoint, repository, version, and tools. Save that evidence with a timestamp.
A branded match proves the entity is listed; a generic match shows directory retrieval for an intent; an LLM recommendation is a later independent observation.