Pattern preview · 12 of 4,089 sample rules shown · site-specific intelligence stays private
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.
Sample rules shown
3
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
progress_notifications
mcp-progress-notificatio-context-report-progress-does-not-send-notification-9205e370
IFcontext.report_progress does not send notifications on streamable-http transport because related_request_id is missing.
THENIn the report_progress method in fastmcp/server.py, add the argument related_request_id=self.request_id to the send_progress_notification call. This ensures progress notifications are correctly associated with the request and delivered via the correct SSE stream.
Tier 170%
progress_notifications
mcp-progress-notificatio-using-context-report-progress-in-a-fastmcp-server--2dba129e
IFUsing `context.report_progress` in a FastMCP server with `streamable-http` transport fails to send progress notifications.
THENModify the `report_progress` method in `src/mcp/server/fastmcp/server.py` to include `related_request_id=self.request_id` when calling `send_progress_notification`. This ensures progress notifications are routed correctly over the POST-initiated SSE stream.
Tier 170%
progress_notifications
mcp-progress-notificatio-when-using-context-report-progress-with-streamable-b3ed42c1
IFWhen using `context.report_progress()` with streamable-http transport, no progress notifications are sent to the client.
THENIn the `report_progress` method of `FastMCP Context`, add the `related_request_id=self.request_id` parameter to the call to `send_progress_notification`. As a temporary workaround, call `session.send_progress_notification` directly with the correct `request_id`.
Tier 170%
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