Unverified50% confidenceEventExact time
Coding-focused Agents that had previously removed MCP due to cost concerns are now adding MCP back
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/9/2026
First Seen
Valid until: 1/7/2027
Sources
Related Entities
Related Claims
UnverifiedThe update fixes an issue where the tool list cache was retained after an MCP server reconnected.74% similarUnverifiedLegacy MCP Servers (such as aws.api-mcp-server or aws.knowledge-mcp-server) provide overlapping tools that may cause AI agent confusion or task failures, and should be removed from claude.json before installation.73% similarUnverifiedMCP is a stateless call, making it impossible to go back and ask a previously contacted agent what happened.73% similarUnverifiedSetting MCP support as the default rather than an option indicates that the project team believes MCP has transitioned from an experimental feature to a foundational capability.72% similarUnverifiedMCP servers can silently change their tool behavior after being approved, and agents will continue to invoke the new version without the user's knowledge.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/991742API
curl https://kongchang.com/api/v1/knowledge/claims/991742MCP
get_claim(id=991742)