APX `mcp check` Is the Fastest Way to Debug Shadowed MCPs

APX mcp check Is the Fastest Way to Debug Shadowed MCPs APC is the portable context layer. APX is the local runtime and tooling layer that makes APC useful every day. When an MCP setup feels wrong, the fastest fix is usually not to stare at the final list of servers. It is to inspect how APX merged the sources. That is why apx mcp check matters. It shows the source files, the active entries after merge, and any conflicts. In other words, it answers the real question: which MCP won, and what got shadowed? Why list is not enough apx mcp list is useful, but it only shows the merged result. That is good for a quick inventory and bad for debugging drift. If the same MCP name exists in more than one scope, the final list hides the path that produced it. A clean list can still hide a bad setup. For example: a shared MCP in .apc/mcps.json a runtime override in ~/.apx/projects/<id>/mcps.json a machine-wide entry in ~/.apx/mcps.json The name looks fine. The