Supabase MCP server — security posture
Supabase's MCP server for database access.
B79Last scanned August 27, 2026
Vendor domain: supabase.com
Email authentication
- DMARCEnforced (p=reject).
- SPFPublished — authorizes which servers may send mail for this domain.
- DKIMDetected — outgoing mail can be cryptographically verified.
- MTA-STSNot published — inbound mail delivery can be downgraded to plaintext.
- TLS-RPTNot published — no reports if mail delivery or TLS fails.
Disclosures
- security.txtPublishes a security contact (RFC 9116).
- llms.txtPublishes llms.txt for AI crawlers.
AI crawler stance
- GPTBotGPTBot is allowed to crawl.
- ClaudeBotClaudeBot is allowed to crawl.
- Google-ExtendedGoogle-Extended is allowed to crawl.
- PerplexityBotPerplexityBot is allowed to crawl.
- CCBotCCBot's access is unspecified in robots.txt.
- meta-externalagentmeta-externalagent's access is unspecified in robots.txt.
What this is — and isn't
These are outside-in observations of public infrastructure — DNS, TLS, and well-known paths. They say nothing about the vendor's code, data handling, or internal controls.