Remote MCP Accounts for 1,213 Profiles, but Its Boundary Is Different
detailed profile rows include 1,213 remote MCP targets and 596 remote descriptor successes. Remote MCP is smaller than local subprocess, but its auth, origin, and data-flow boundaries differ.
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
Remote MCP does not launch a local process, but it shifts the review to what data leaves the environment and which remote origin is trusted.
Key Findings
- detailed profile rows include 1,213 remote MCP targets and 596 remote descriptor successes. Remote MCP is smaller than local subprocess, but its auth, origin, and data-flow boundaries differ.
- 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-05-14 |
| 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 |
|---|---|---|
| Remote MCP targets | 1,213 | Candidate whose primary target is a remote endpoint |
| Remote descriptor OK | 596 | Candidate with remote descriptor confirmed |
| Streamable HTTP | 250 | Candidate using HTTP transport |
What We Observed
Remote MCP does not launch a local process, but it shifts the review to what data leaves the environment and which remote origin is trusted. This lens matters because MCP servers are not just plugins; they are bundles of authority exposed to an AI agent.
Practical Reading
Review endpoint ownership, authentication, TLS/origin, data retention, logs, and onward transfer to third-party APIs. 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
Review endpoint ownership, authentication, TLS/origin, data retention, logs, and onward transfer to third-party APIs. 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.