ai-smithery-pinion05-supabase-mcp-lite
ToolProof Connection Signal
Review First
Do not connect casually. Review the exposed tools, credentials, network/file/API access, and approval path before giving an agent access.
Evidence Confidence56/100
Tools Inferred0
Control Signals3
Profile status
ToolProof reviewSnapshotEvidence-backed review from observed public information.
Owner statusUnclaimedOwner-provided details have not been maintained yet.
Watch statusNot monitoredEnable ToolProof Watch to monitor drift and freshness.
Last observed2026-06-10T16:45:29ZMCP servers can change after observation.
Why this signal
- Source evidence fetched from 4 file(s).
- No MCP tools were confidently identified.
- 3 visible control signal(s) observed.
- 1 concern(s) identified from fetched evidence.
- Network/API or environment credential indicators are present, so scoped access matters.
What this server exposes
No MCP tools confidently identified.
Source and observation
Source: https://github.com/pinion05/supabase-mcp-lite
Observed: 2026-06-10T16:45:29Z
Machine ID: mcp:ai-smithery-pinion05-supabase-mcp-lite
Capabilities inferred
- MCP/server implementation evidence found
- Network access indicators
Controls observed
- Authentication/authorization language observed
- Explicit secret/env configuration language observed
- License file or license language observed
Recommended controls
- Use least privilege, logging, and staged rollout until controls are verified.
Open questions before connection
- What credentials or environment variables are required?
- What data can leave the local environment?
- What systems can the agent reach through this server?
- What actions should require human approval?
- Which external endpoints or APIs can be called?
Findings and concerns
- No MCP tools confidently identified
Claim or update this profile
Are you the owner of this MCP server? Submit official docs, intended use cases, support links, security contact, and recommended safe configuration.
Owner-provided information is shown separately from ToolProof evidence and does not change the connection signal unless reviewed.
Payment may buy review, monitoring, or sponsored visibility. It does not change the ToolProof connection signal.
Evidence fetched
- Dockerfile (604 bytes)
- README.md (3706 bytes)
- package.json (562 bytes)
- src/index.ts (23597 bytes)