file.googleapis.com MCP is misidentified as Google Drive and auth-free

[Anrahya]

Hi — while using the registry as a discovery source, I found that the file.googleapis.com MCP entry is misidentified.

Current catalog entry

domains/file.googleapis.com/integrations.json identifies https://file.googleapis.com/mcp as a Google Drive MCP server with authStatus: "none".

However:

• tools/list on that endpoint returns Cloud Filestore tools such as list_instances and create_backup.
• Calling list_instances without credentials returns Request is missing required authentication credential.
• Google's Filestore REST reference identifies file.googleapis.com as the Cloud Filestore service.
• Google's Drive MCP reference gives the Drive endpoint as https://drivemcp.googleapis.com/mcp/v1.
• Google's Drive MCP setup guide states that it uses OAuth 2.0.

Expected

• Reclassify https://file.googleapis.com/mcp as Cloud Filestore and mark its authentication accurately.
• Represent the actual Google Drive MCP endpoint and OAuth requirement if Developer Preview surfaces belong in the catalog.
• Correct the durable discovery source or validation path so a catalog sync does not restore the incorrect record.

I did not find an existing issue covering this. I would be happy to help with a focused PR once the preferred correction point (discovery pipeline, persisted discovery data, or checked-in record) is clear.