SaaS ideas your next customers are already looking for
100 SaaS startup ideas for the people who said they'd pay, from agency owners to dentists. Micro SaaS ideas, AI SaaS ideas and B2B SaaS ideas: find yours, build it, sign them up.
Popular:
| # | Idea |
|---|
No idea matches this filter.
Pain points in business: what people struggle with
Search the problems to solve, as people described them on Reddit and other platforms, in their own words.
Popular:
| # | Pain point |
|---|
No pain point matches this filter.
MCP Server Security Governance
MCP servers lack access control, audit logging, and runtime policy enforcement, creating security and compliance risks in production.
In their words
the moment someone asks "can you show me every time this tool was called and by whom" and you realize you can't
If Glama accepted that existing proof (or any shared ownership standard across directories), claiming would be one click
instead of Customer A's access ending when Customer A was done, Customer B would show up and get their own data plus Customer A's
Tokens lived in his home directory, he'd left the company three months earlier.
increasingly some of my smaller clients need something more immediate
our actual problem had grown past "route between providers" into needing the same governance layer over mcp and agent traffic too
anyone who is chatting with my agent can automatically inherit my permissions - as agent is actually 'acting on my behalf'
you'd need a dev who actually knows what they're looking at, plus the ongoing overhead of re-checking when the repo updates
Which server an agent may call and what it may do once it is there looks like another.
specifically care about unified logging across multiple MCP servers, routing, and something that doesn't become its own ops project to maintain
How are you all keeping track of the MCP servers your devs spin up?
there is no way for me to prevent AI from sharing measure/column definitions with the user
we have so many problems with MCP related to auth, scopes etc... how do you guys help solve that?
I've been a bit hesitant to spin up too many MCP servers locally when I can't easily tell what permissions they're asking for.
MCP platform and security teams
Where they talk
- r/mcp
- r/AI_Agents
- r/cybersecurity
- r/MCPservers
- r/AskNetsec
- r/ClaudeAI
- r/sysadmin
- r/aiagents
Tools they use today
- MCP
- Claude
- Docker
- TrueFoundry
- GitHub
- Glama
- OAuth
- Cursor
Why those fall short
- authorization context never ends, so data accumulates across tenants
- each server holds its own credentials and rotates independently
- no per-workflow gating; only a single global toggle
- separate identity artifacts, no re-scan, anonymous scanners skew stats
- static perms miss direct API calls; manual review does not scale past 30 tools
Map of ideas
Drawing the map…