Nicheloom visits: 58,050 all-time · 7,694 in the last 7 days

The opportunity tracker for new startups.

Today: 1,953 launches · Niche of the day: specialized calculation tools · See what launched today →

Risk Analysis Database of Every MCP Server

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

Hi HN, We’re building security tooling around agentic AI systems.Today, we're releasing our public MCP catalog with detailed risk analysis for every MCP server we've found on the internet: https://mcp.armor1.ai/mcp-directoryWe all love agents and the power that MCPs unlock: suddenly your AI assistant can query databases, manage files, call APIs, and interact with the real world. But when we started adopting MCPs ourselves, we kept running into the same nagging questions:Is this MCP safe? Where is my data actually going? Could it execute destructive actions? Is it susceptible to prompt injection? Can the LLM be tricked into calling something it shouldn't? And perhaps most concerning, can one MCP server influence the model and exfiltrate data meant for another?We looked for answers and found... not much. No comprehensive catalog or standardized risk assessment. Nothing that gave us confidence before connecting an MCP to our agents.So we built an MCP threat catalog and what we found was eye-opening.We built what we believe is the deepest risk analysis pipeline for MCP servers:• Provenance tracking: from an official source or community-contributed• MCP spec conformance: does it follow the protocol correctly, or are there deviations that could cause unexpected behavior• OWASP Top 10 for Agentic Apps: evaluate tool descriptions against the emerging threat categories specific to AI agents• Static source analysis: analyze source code for AI-specific vulnerabilities, not just traditional ones• CVE correlation: check dependencies against known vulnerabilities.• Behavioral risk patterns: tool definitions that could enable prompt injection, privilege escalation, or cross-server data theftWhat we found:• Hundreds of credential leaks: API keys, tokens, and secrets exposed in server configurations and code.• Dozens of MCP servers using known malicious packages: Not just vulnerable dependencies, but actually malicious ones.• Tools attempting context poisoning: MCP servers designed to subvert the LLM and steal information via memory manipulation, potentially exfiltrating data meant for other connected servers.We want everyone to realize the benefits of agentic AI, but not at the cost of security being an afterthought. So we're making this catalog free with no login, and we're committed to keeping it that way.This is still a WIP. Looking forward to your feedback on what we need to improve, what we got right, and what we should prioritize next.

HN · launched Feb 5, 2026 · 22 upvotes (top 30%) · 0 views

Niche: ai agent security and monitoring tools · 297 launches, 14 in the last 7 days ▼ -44% · Explore this niche →

Category and tags

  • Security
  • Compliance & governance
  • B2B
  • AI feature
  • Commercial product

Visit website ↗ Source listing ↗

Could you build this?

Partial Building the directory and UI is straightforward CRUD, but generating high-quality risk and vulnerability analysis across arbitrary third-party MCP servers requires specialized static analysis and security auditing pipelines.

What it would actually take: The system requires a web crawler/indexer targeting GitHub and package registries to discover MCP servers, combined with an automated static analysis (AST parsing, permission auditing) and dynamic sandboxing engine that monitors tool capabilities and potential prompt injection/privilege escalation vectors. The challenge lies in accurately detecting malicious agent tool definitions, secret leakage, and unsafe shell/network execution paths automatically. This demands dedicated security research expertise in AI agent protocols and automated vulnerability triage.

Discussion

7 comments analyzed.

Competitors mentioned: mcp-scan

Concerns raised: MCPs lack standardization and protocols, Need visibility into what tools are doing on system, Unclear how many MCP servers have actually been analyzed, High false positives from risk analysis tools

Feature requests: MCP server interface to analyze installed MCP servers, Armor1 MCP server support

Competitors

Other products that read as similar to this one : 701 launches clear the similarity bar, closest 8 shown.

Attention rank: #257 of 702 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 97 days after the earliest competitor.

  • CyberCage · hn · 2025-12-11 · 6 upvotes · similarity 0.59
  • AgentExploitDB · ph · 2026-10-07 · 1 upvotes · similarity 0.54
  • MCP Mesh · hn · 2025-12-30 · 8 upvotes · similarity 0.53
  • GuardiAgent · hn · 2025-11-21 · 9 upvotes · similarity 0.53
  • I built a database for AI agents · hn · 2026-04-07 · 12 upvotes · similarity 0.52
  • Mwe-MCP · hn · 2026-07-23 · 5 upvotes · similarity 0.52
  • MCPJam · hn · 2026-09-17 · 12 upvotes · similarity 0.51
  • MCPfinder · hn · 2026-04-20 · 9 upvotes · similarity 0.51

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.