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
notification_validation
mcp-notification-validat-mcp-everything-server-sends-custom-notification-ty-7da0ee53
IFMCP 'everything' server sends custom notification type 'notifications/stderr' not defined in the MCP specification, causing pydantic type validation errors in the Python SDK.
THENEither update the 'everything' server to use the standard 'notifications/message' for stderr output instead of the custom method, or extend the SDK's ServerNotification model to accept custom notification methods (e.g., by adding 'notifications/stderr' to the allowed types or using a generic fallback).
Tier 170%
notification_validation
mcp-notification-validat-using-the-mcp-python-sdk-to-handle-notifications-f-64f06cd7
IFUsing the MCP Python SDK to handle notifications from the 'everything' server results in Pydantic validation errors because the server sends a non-standard 'notifications/stderr' notification type that is not in the SDK's ServerNotification union.
THENUpdate the 'everything' server to a version that includes the fix from PR #2469, which eliminates the 'notifications/stderr' notification. Alternatively, if you cannot update the server, patch the Python SDK's message handler to silently ignore or custom-handle unknown notification types.
Tier 170%
notification_validation
mcp-notification-validat-mcp-server-sends-a-notification-with-an-unrecogniz-25bd0f23
IFMCP server sends a notification with an unrecognized method string (e.g., 'notifications/stderr') causing pydantic validation errors in the Python SDK.
THENEnsure the server only emits notification methods defined in the MCP specification (e.g., 'notifications/message', 'notifications/cancelled', 'notifications/progress', etc.). If custom logging is needed, use the standard 'notifications/message' method with appropriate severity levels. Alternatively, extend the client SDK's ServerNotification model to accept additional methods.
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