Execution Risk Across 2,858 Command-or-Code MCP Profiles
2,858 detailed profile rows fall into command-or-code execution capability. Execution is useful, but when it overlaps with outbound access or file mutation, review priority rises.
Terminology
| Term | Meaning |
|---|---|
| Public Registry | Inspected MCP candidates searchable in the public Registry |
| Profile evidence | Inspection-profile aggregates used to interpret public candidates in more depth |
| Review/action rows | Entries in WARN, NEED_REVIEW, RESTRICT, or BLOCK that require reasoned adoption review |
Lead
When an MCP server can run code or commands, an AI-agent suggestion can turn into execution on a machine. That requires stronger boundary review than simple information retrieval.
Key Findings
- 2,858 detailed profile rows fall into command-or-code execution capability. Execution is useful, but when it overlaps with outbound access or file mutation, review priority rises.
- The 20,629 public Registry entries and 11,627 profile-evidence rows answer different questions and should not be mixed casually.
- The observation is an adoption input, not a final approval for a specific environment.
- Counts are snapshot evidence, so adoption review should check the observation date before treating the number as current state.
Dataset
| Item | Value |
|---|---|
| Article date | 2026-04-26 |
| Public Registry snapshot | 20,629 entries, synced 2026-06-06T01:17:38.963Z |
| Detailed profile evidence | 11,627 rows, generated 2026-05-20/21 |
| Public disclosure level | Aggregates, distributions, anonymized observations, and operational interpretation |
Observed Metrics
| Metric | Value | Meaning |
|---|---|---|
| Command/code execution profiles | 2,858 | Capability near command or code execution |
| Command execution signal | 2,439 | Observation near external command execution |
| Code execution signal | 1,074 | Observation near dynamic code execution |
What We Observed
When an MCP server can run code or commands, an AI-agent suggestion can turn into execution on a machine. That requires stronger boundary review than simple information retrieval. This lens matters because MCP servers are not just plugins; they are bundles of authority exposed to an AI agent.
Practical Reading
For execution-capable MCP servers, teams should document what can be executed, with which arguments, in which directory, with what network access, and where output is stored. Review should record execution location, destinations, data touched, and unresolved evidence, not only the server name or README.
Limits
- The evidence uses public aggregate data and anonymized observations, not internal detection mechanics.
- Counts are snapshot values and will change as the Registry updates.
- This is not a claim that any named MCP server is safe or unsafe.
Conclusion
For execution-capable MCP servers, teams should document what can be executed, with which arguments, in which directory, with what network access, and where output is stored. Keeping this evidence in the intake record makes the review repeatable across teams and deployments.
MCP Guard continuously turns public Registry and profile evidence into adoption-review signals for MCP security teams.