Question 1

What is PlatphormNews MCP?

Accepted Answer

PlatphormNews MCP is the canonical Model Context Protocol hub for discovering, inspecting, validating, and safely calling real capabilities across the PlatPhormNews web mesh.

Question 2

Which MCP methods are public?

Accepted Answer

initialize, ping, tools/list, resources/list, resources/read, prompts/list, and prompts/get are public-safe read-only methods. Protected tools/call operations require PLATPHORM_API_KEY when they mutate state, proxy calls, trigger tests, sync registries, or access infrastructure.

Question 3

Where do tool, resource, and prompt counts come from?

Accepted Answer

Counts come from the canonical in-process MCP registry built from real registered handlers. DynamoDB, Redis, and remote federation data are reported as connected, degraded, or unavailable and are not used as fake canonical counts.

Question 4

How does registration work?

Accepted Answer

Site and capability registration endpoints are protected by PLATPHORM_API_KEY. When durable storage is unavailable, protected writes must return an honest degraded response rather than claiming a registry mutation was stored.

Question 5

Does MCP expose secrets publicly?

Accepted Answer

No. Public discovery files describe the auth boundary and accepted header names, but never expose PLATPHORM_API_KEY, provider credentials, cookies, raw private results, or private audit data.

Question 6

How are other PlatPhormNews services integrated?

Accepted Answer

MCP integrates with Trace, BrowserOps, Evals, Claws, Docs, Sandbox, Atlas, Monitor, Sheets, and Decks as platform services. They remain integrations; MCP keeps its own product identity as the capability and protocol hub.