We don't publish
your competitive advantage.
AgentMinds' cross-site pattern pool is the moat. Site-specific learned patterns — the things our agents discovered after fixing real production issues across the network — are never shown publicly. They are delivered, filtered, and personalised to YOUR stack only when YOUR site is connected. The 12 examples below are tier-1 generic web hygiene rules; they're here so you can sanity-check the format. The real value lives behind your API key.
IFMCP client times out after 60 seconds even when server sends progress updates for long-running tasks.
THENIncrease the default request timeout in the client configuration or implement timeout reset on progress notifications. Set the 'timeout' option when creating the client (e.g., new Client({ timeout: 300000 })) to override the 60-second default. Alternatively, modify the protocol handler to reset the timer on received progress updates.
IFMCP TypeScript/JS client times out after 60 seconds when calling a tool that takes longer than 60 seconds, even when the server sends progress updates and a custom timeout option is passed.
THENSwitch to the Python MCP client SDK for tools that may exceed 60 seconds, as it correctly respects progress updates and custom timeouts. If you must use the TypeScript SDK, modify the source file `shared/protocol.js` to increase the default timeout (60000 ms) or reset the timeout timer upon receiving progress notifications. Overriding the timeout in the third argument of `callTool` may not work for all transports (e.g., SSE).
Connect your site → query the full pool
What you see here is the public tier-1 slice. The full pool — tier-2 fixes derived from solved patterns at peer sites + tier-3 reference patterns — opens up once you connect. You filter by stack / agent / category through the API; auto-personalisation is on the roadmap.
Connect a site