Clarify MCP manifests on Agentic Registry

[iabeurope-beis]

Context: The Agentic Registry features an MCP manifest with a list of tools per agent. This is either uploaded manually by the organization registering an agent or populated by requesting tools/list.

Issues:

• The authoritative runtime tool surface is shared by the MCP server through a tools/list request at runtime. The MCP manifest on the Registry may be stale.
• The tools available through an MCP server may change - this is why MCP supports notifications/tools/list_changed.
• It is not clear what consumers of the MCP manifest on the Registry should do with this information and there is no transparency on how fresh the manifest is (if it is collected by Tech Lab requesting the MCP server).
• There are no expectations with respect to the manually uploaded MCP manifests, e.g. stable and complete I/O models.

Suggestions:

• Clarify that the MCP manifest should not be considered an authoritative runtime tool surface, i.e. it should not be considered a "source of truth" for the tools that the MCP server exposes separate to tools/list.
• Clarify that the tool surface is subject to change and that Tech Lab does not verify it.
• Feature whether the manifest was uploaded manually or collected by Tech Lab, and in the case of the latter the timestamp of the latest request to tools/list.
• Clarify expectations with respect to manually uploaded MCP manifests.

[iabeurope-beis]

Listing some more suggestions based on testing of the registry via MCP:

• Verify that endpoint_url reflects the current production MCP path for different entries, I've found a couple of stale URLs.
• Verify that authentication_required matches runtime behavior.
• Periodically validate registered MCP endpoints with a real tools/list probe and flag entries whose metadata no longer matches runtime behavior.

[tidolblair-prog]

I still don’t understand and never understood or not interested really where tf I should apply( almost like recipe book but you know at least physical aspect of it ) where and how. These instructions