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_url
mcp-oauth-metadata-url-when-running-multiple-mcp-servers-under-a-common-b-498e7c6f
IFWhen running multiple MCP servers under a common base path (e.g., https://example.com/mcpServers/myAwesomeServer), 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.
THENFix the URL construction to follow RFC 9728: remove any trailing slash from the host component, then insert '/.well-known/oauth-protected-resource' before the path component of the resource identifier. For a server URL like 'https://example.com/mcpServers/myAwesomeServer', the metadata endpoint becomes 'https://example.com/.well-known/oauth-protected-resource/mcpServers/myAwesomeServer'.
Tier 170%
oauth_metadata_url
mcp-oauth-metadata-url-protected-resource-metadata-url-is-constructed-by--5eb88324
IFProtected resource metadata URL is constructed by appending '/.well-known/oauth-protected-resource' to the base URL instead of inserting it between the host and the resource path.
THENFollow RFC 9728 Section 3.1: remove any trailing slash from the host component, then insert '/.well-known/oauth-protected-resource' between the host and the path/query of the resource identifier. For example, given resource URL 'https://example.com/mcpServers/myAwesomeServer', the metadata endpoint should be 'https://example.com/.well-known/oauth-protected-resource/mcpServers/myAwesomeServer'. Update the SDK's `_discover_protected_resource` method accordingly.
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