What does Noma Security discover?
Models, agents and MCP servers across an organisation, as part of AI agent hardening.
Beam vs NOMA SECURITY
Beam vs Noma Security
Noma Security discovers models, agents and MCP servers across an organisation and hardens AI agents, backed by more than $100M in reported funding. That is an enterprise inventory and hardening problem. Beam answers a local one: what did the coding agent on this machine do, and does this skill or MCP config look risky before you run it.
Beam vs Noma Security, side by side
Details below are drawn from a September 2026 review of the AI agent security market. Some figures are vendor-sourced or analyst estimates, and this is a fast-moving space — check with each vendor before you buy. Composio details come from its own pricing and documentation pages as of October 2026.
| Beam | Noma Security | |
|---|---|---|
| What it is | Local-first activity monitor, policy enforcement, and pre-run scanner for AI coding agents, with a Sentinel browser extension for AI chats. | Enterprise AI security platform focused on agent hardening and AI asset discovery. |
| Monitoring | Shell commands, file changes, tool calls, network endpoints and browser actions from harnesses such as Claude Code, Codex and Cursor, plus Beam Sentinel checks on supported AI chat sites before send. Normalised into local NDJSON with risk flags and evidence attached. | Discovers models, agents and MCP servers across an organisation and hardens AI agents. |
| Skill / MCP scanning | Yes. SKILL.md files and MCP configurations are scanned before you run them, using 11 heuristic patterns plus an MCP version-pin check. Workspace admins can also block an MCP server for the org or one user. | Discovers MCP servers as part of AI asset discovery. Dedicated skill-file scanning is not covered in our source research. |
| Blocking / enforcement | Yes. Workspace owners and admins set observe, advisory, or enforce policy. Enforce denies matching tool calls on Claude Code and Codex PreToolUse hooks. The Sentinel Chrome extension pauses or blocks high-risk browser sends and can hold a send after redacting live secrets. | Agent hardening is part of the platform. |
| Individual use | Free for up to 3 people, and Pro for one person at $8/month. Team workspaces add owner/admin roles, org baselines, stricter member overrides and a control plane. | None. Enterprise platform sale. |
| Deployment | Local collector plus a workspace dashboard. Apple and Windows MDM. Sentinel Chrome extension for browser AI chats. Licensed self-hosted control plane for teams that need it on their own infrastructure. | Enterprise deployment. |
| Source / licence | AGPL-3.0 for the local CLI and collector; the multi-user control plane is proprietary. | Commercial, not open source. |
| Pricing | Free for up to 3 people. Pro $8/month for one person. Team $20 per developer and $5 per browser seat a month, billed yearly. | Enterprise custom quote, no public price. |
Noma Security in numbers
As reported in our source research. Some figures are estimates.
- Funding
- Reported to have raised more than $100M; some funding figures in this space are estimates
- Discovery
- Models, agents and MCP servers
Where Noma Security does more
- Organisation-wide discovery of models, agents and MCP servers — Beam sees only the machine it runs on.
- Agent hardening rather than observation alone.
- Well funded, with more than $100M reported raised.
Where Beam differs
- Beam is a local tool a single engineer can run without a platform rollout.
- Beam scans an MCP configuration file before you connect it, as a discrete pre-run step.
- Beam keeps its record local, with credentials redacted before persistence.
Beam’s current gaps
- Enforce is hook-based: a native deny is wired for Claude Code and Codex PreToolUse. Cursor, Copilot CLI and Gemini currently get a deny note, not a verified block.
- Missing, unreadable or expired cached policy allows the action. Beam is not a fail-closed kernel sandbox or an in-silicon watchdog.
- Scanning is heuristic pattern matching. It produces false positives, misses novel phrasing, and is not a guarantee of safety.
- There is no SOC 2 report and no default SIEM forwarder. Kernel isolation like OpenShell remains a different layer.
Which one fits
If you need to find every model, agent and MCP server across an organisation, that is Noma's problem space and not Beam's. Beam suits a team starting from a single machine and no budget cycle.
FAQ
How much has Noma raised?
More than $100M according to reporting, though funding figures in this market are sometimes estimates.
Can Beam do organisation-wide discovery?
No. Beam runs on enrolled machines and has a workspace console, but it is not an organisation-wide inventory of every model, agent and MCP server.
See how Beam works
Beam is an early, local-first prototype. Read what it actually does today before comparing it further.