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
2
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
oauth_metadata_discovery
mcp-oauth-metadata-disco-when-running-multiple-mcp-servers-under-the-same-h-fe358a96
IFWhen running multiple MCP servers under the same host with different paths, the OAuth protected resource metadata endpoint is incorrectly constructed by appending `/.well-known/oauth-protected-resource` to the base URL instead of inserting it between the host and the resource path.
THENUpdate the OAuth client to construct the metadata URL by removing any terminating slash after the host and inserting `/.well-known/oauth-protected-resource` between the host and the path/query components of the resource server URL, as per RFC 9728 Section 3.1. This fix is available in PR #1407 of the python-sdk (merged).
Tier 170%
oauth_metadata_discovery
security-oauth-metadata-disco-when-running-multiple-mcp-servers-under-a-path-e-g-6c25b984
IFWhen running multiple MCP servers under a path (e.g., https://example.com/mcpServers/myAwesomeServer), the OAuth protected resource metadata URL is incorrectly constructed as base URL + '/.well-known/oauth-protected-resource' instead of inserting the well-known string between host and path as per RFC 9728.
THENModify the protected resource metadata discovery to construct the URL by inserting '/.well-known/oauth-protected-resource' between the host and the remaining path/query of the resource server URL. For example, for server URL 'https://example.com/mcpServers/myAwesomeServer', the correct metadata URL is 'https://example.com/.well-known/oauth-protected-resource/mcpServers/myAwesomeServer'. The same fix applies to the OAuth authorization server metadata endpoint.
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