devashishjadhav

8 ms·

1. 1.▲
   by devashishjadhav 6mo ago

   The authorization gap you're describing is real but I think there's a layer missing even before the gateway the MCP server itself. If the tool schema is compromised or the server is a trojanized fork (there's an active thread
2. 2.▲
   by devashishjadhav 6mo ago

   Interesting approach. The context bloat problem is real I've been running into it while building an MCP server for a code knowledge graph. The pattern I landed on was the opposite direction: instead of compressing what goes in, keep th
3. 3.▲
   by devashishjadhav 6mo ago

   This is a real problem and it's going to get worse as the MCP ecosystem grows. The supply chain trust issue is structurally identical to what npm faced in 2018-2020 and the stakes are higher because MCP servers have filesystem access b