mseep-mcp-foundry@0.1.1
VERIFIED· not startedPublisher claims: "MCP Server for Azure AI Foundry (experimental)" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
AZURE_OPENAI_API_KEYConfiguration, not credentials: AZURE_AI_PROJECT_ENDPOINT, AZURE_OPENAI_API_VERSION, AZURE_OPENAI_DEPLOYMENT, AZURE_OPENAI_ENDPOINT, DEFAULT_AGENT_ID, EVAL_DATA_DIR, LABS_API_URL, SWAGGER_PATH- Where it talks to
- no vendor host named in the codeAlso azure.com, azurewebsites.net, azureml.ms — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names azure.com, azurewebsites.net, azureml.ms as well as its own vendor. The guard injects AZURE_OPENAI_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-12 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
help='Path to .env file (default: .env)')Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.parser.add_argument('--envFile', required=False, default='.env',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.output = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.logger.info("SWAGGER_PATH not set in .env file, skipping swagger tool registration")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."hint": "Ensure SWAGGER_PATH is set in your .env file"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."hint": "Ensure SWAGGER_PATH is set in your .env file"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for mseep-mcp-foundry@0.1.1 as of 2d ago. This is the package itself, not its dependencies.