Skills/PyPI/outlook-mcp

outlook-mcp@0.1.0

VERIFIED· not started

Publisher claims: "MCP server for Microsoft Outlook integration to manage emails, calendar events, and contacts" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher akhilthomas236 · publishing for 526 daysInstalls 107Last detonated 8 h ago
$claude mcp add outlook-mcp -- uvx outlook-mcp
WatchReport an issue

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
OUTLOOK_CLIENT_SECRETOUTLOOK_PASSWORDConfiguration, not credentials: OUTLOOK_CLIENT_ID, OUTLOOK_TENANT_ID, OUTLOOK_USERNAME
Where it talks to
no vendor host named in the codeAlso microsoft.com — 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 microsoft.com as well as its own vendor. The guard injects OUTLOOK_CLIENT_SECRET, OUTLOOK_PASSWORD only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx outlook-mcp

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-14 and scored it 88/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 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsmcp-username-password-complete-guide.json:28 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"filename": ".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsmcp-username-password-complete-guide.json:86 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"⚠️ Never commit .env file to version control"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup_username_password.py:16 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv_file = current_dir / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstest_server.py:171 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesprint("2. Configure environment variables (.env file)")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsmcp-config-examples.json:24 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"description": "Configuration using .env file (recommended for security)",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup_username_password.py:35 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Create .env contentFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstest_auth.py:25 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesprint("Please check your .env file and make sure all values are set.")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsmcp-config-examples.json:34 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"note": "This assumes you have a .env file in the project directory with the credentials"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup_username_password.py:10 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Create .env file with username/password authentication."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsmcp-username-password-complete-guide.json:76 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"step_6": "Create .env file with your credentials",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsusername-password-setup-guide.json:30 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"filename": ".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup_username_password.py:52 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Write .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈59 tok
1 file · 26 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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 outlook-mcp@0.1.0 as of 7 h ago. This is the package itself, not its dependencies.