Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"azure-foundry-edge-mcp-server-with-relay": {
"args": [
"mcp-remote",
"https://my-lab-relay.servicebus.windows.net/secure-lab-devices"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A production-ready architecture for securely connecting cloud-based AI agents to on-premises MCP (Model Context Protocol) servers using Azure Relay Hybrid Connections. This solution enables AI agents running in Azure AI Foundry to interact with local lab equipment, devices, and APIs without exposing ports through your firewall.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud / ai-ml
Dynamic problem-solving through sequential thought chains
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
MCP Security Weekly
Get CVE alerts and security updates for Azure Foundry Edge Mcp Server With Relay and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A production-ready architecture for securely connecting cloud-based AI agents to on-premises MCP (Model Context Protocol) servers using Azure Relay Hybrid Connections. This solution enables AI agents running in Azure AI Foundry to interact with local lab equipment, devices, and APIs without exposing ports through your firewall.
┌──────────────────────┐
│ CLIENT APPS │ ┌────────────────────────────────────────────────────┐
│ (Any Location) │ │ AZURE CLOUD │
│ │ │ │
│ ┌────────────────┐ │ │ ┌──────────────────────────────────────────────┐ │
│ │ Web UI │─┼────────▶│ │ Microscopy Agent (Backend API) │ │
│ │ (Next.js) │ │ AG-UI │ │ + Azure AI Foundry (GPT-4) │ │
│ │ Port: 3000 │ │ SSE │ │ Port: 5200 │ │
│ └────────────────┘ │ │ └──────────────────────────────────────────────┘ │
│ │ │ │ │
│ ┌────────────────┐ │ │ │ MCP Request │
│ │ Teams Chat │─┼────┐ │ ▼ │
│ └────────────────┘ │ │ │ ┌──────────────────────────────────────┐ │
│ │ │ │ │ Azure Relay Hybrid Connection │ │
│ ┌────────────────┐ │ │ │ │ (Biirectional Secure Tunnel) │ │
│ │ Mobile App │─┼────┘ │ │ • No direct calls to on-premises │ │
│ └────────────────┘ │ │ │ • Relay Listener initiates tunnel │ │
│ │ │ │ • Requests proxied through tunnel │ │
│ │ │ └──────────────────────────────────────┘ │
└──────────────────────┘ │ ▲ │
│ │ Outbound HTTPS (443) │
│ │ Persistent WebSocket │
└────────────────────────┼────────────────────────────┘
│
│ ← Relay Listener establishes
│ outbound connection only
│
┌───────────────────────────────────┼────────────────────────────┐
│ ON-PREMISES / EDGE │ │
│ │ │
│ ┌──────────┴──────────┐ │
│ │ Relay Listener │ │
│ │ (Proxy) │ │
│ │ • Initiates tunnel │ │
│ │ • No inbound ports │ │
│ └──────────┬──────────┘ │
│ │ │
│ │ localhost HTTP :5100 │
│ ▼ │
│ ┌─────────────────────┐ │
│ │ Device MCP API │ │
│ │ (MCP Server) │ │
... [View full README on GitHub](https://github.com/jmasengeshomsft/azure-foundry-edge-mcp-server-with-relay#readme)