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 postgres server fails to connect to Azure Database for PostgreSQL Flexible Server with private endpoint, error 'no encryption' or 'SSL off'
THENAdd `?sslmode=enable` to the connection string. This enforces SSL transport encryption as required by Azure PostgreSQL flexible server.
IFMCP postgres server fails to connect to AWS RDS PostgreSQL with error 'no pg_hba.conf entry for host ...', even though other tools work
THENDownload the RDS combined CA bundle and add `?sslmode=verify-full&sslrootcert=<path-to-bundle>` to the connection string. This enables SSL verification with the proper certificate.
IFMCP postgres server returns error 'no pg_hba.conf entry for host ... , SSL off' or 'no encryption' when connecting to PostgreSQL
THENAdd `?sslmode=disable` to the connection string for local or non-encrypted environments. This explicitly disables SSL, bypassing the server's rejection of non-SSL connections.
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