Unverified50% confidenceEventExact time
The first run found that a test for moshcode mcp install inherited the host machine's PATH and HOME, causing a real mcp add operation to be executed; the workers fixed the issue by making it use only a stub engine.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/17/2026
First Seen
Valid until: 1/15/2027
Sources
Related Entities
Related Claims
UnverifiedUsing MCP over stdio as a seam allows replacing real tools with mock MCP servers during testing, enabling process-level dependency substitutability, similar to contract testing.66% similarVerifiedAfter an MCP server is successfully installed, an mcp.json file is generated in the project root directory, containing the configuration information for all project-level MCP servers.66% similarUnverifiedBefore returning the agent session, run extension must be manually called to forcibly trigger the session start event; otherwise, pi-mcp-adapter will not initialize the MCP server and will report an 'MCP server not initialized' error.65% similarUnverifiedA /mcp reconnect all command has been added for MCP, enabling a single retry of all MCP servers that have failed to connect or require authentication.65% similarUnverifiedAn MCP server in the local scope only takes effect for the current user and only in the current project, and is written under that project's entry in the .claude.json file in the home directory65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1052298API
curl https://kongchang.com/api/v1/knowledge/claims/1052298MCP
get_claim(id=1052298)