Add Phasoric remote MCP entry (pending remote license metadata)

[aketchel]

MCP Server Information

Server Name: Phasoric
Service URL: https://phasoric.com
Documentation: https://developers.phasoric.com/mcp-client-setup
Brief Description: Search, read, and safely update Markdown notes in your connected Phasoric knowledge vaults.

Adds a hosted Streamable HTTP entry at https://phasoric.com/api/mcp with OAuth and dynamic tool discovery. Only public catalog metadata is contributed: server.yaml, an empty tools.json, and a documentation README. No implementation source, private repository URL, credentials, or user content is included.

Phasoric is a proprietary hosted service. Open-source implementation and Dockerfile requirements do not apply to this remote-only submission. The catalog metadata contribution does not change the service's license.

Publication blocker: generated license metadata

Please keep this submission in draft until the remote-service license metadata is resolved. Running go run ./cmd/catalog phasoric succeeds, but pkg/catalog/tile.go initializes license := "Apache License 2.0" and only replaces it for local source-backed servers. The generated remote catalog therefore incorrectly labels Phasoric as Apache-2.0. The server-entry schema has no license override. Please omit that default for remote services or provide an accurate proprietary-service designation before publication. The generated catalog is not included in this PR.

Validation

• go run ./cmd/validate --name phasoric passes.
• go run ./cmd/catalog phasoric completes; license issue above was found while inspecting the output.
• Prettier checks pass for all three submitted files.
• Public setup documentation, MCP reference, icon, and OAuth authorization-server metadata return HTTP 200.
• An unauthenticated MCP initialization request returns HTTP 401 with a WWW-Authenticate protected-resource metadata challenge.
• Phasoric is active in the official MCP Registry as io.github.aketchel/phasoric version 1.0.1.
• Docker Desktop OAuth authorization and authenticated tool calls have not been tested for this submission.
• No test credentials have been shared. Any required review access must be limited to a dedicated synthetic-data account.

This submission requires Docker's automated and manual review and is not a claim of end-to-end Docker client compatibility.