EWS MCP server — a lean, safety-gated, cache-first tool surface for an executive-mailbox assistant (see DESIGN.md). Internally packaged fork of azizmazrou/ews-mcp; provenance in PROVENANCE.md at the repo root.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"ews-mcp-orf","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ews-mcp-orf MCP server for an on-premises Microsoft Exchange mailbox via EWS — a lean, safety-gated tool surface for LLM assistants: capability tiers, send kill-switch, two-phase content-bound send confirmation, recipient guard, and a hash-chained audit log. > This is the internally packaged distribution of > [`azizmazrou/ews-mcp`](https://github.com/azizmazrou/ews-mcp) (MIT). > It carries local hardening patches (attachment size cap, recipient > canonicalization, audit fail-closed, persistent confirm tokens, > system-trust TLS). Full architecture and development docs live in the > source repository. ## Install & run (stdio — the default) Requires [uv](https://docs.astral.sh/uv/) (a single EXE; it manages its own Python) — no Docker, no venv, no checkout: ```bash uvx --from ews-mcp-orf ewsmcp ``` Pin a version for pilot deployments: ```bash uvx --from ews-mcp-orf==4.5.0a1.post1 ewsmcp ``` **Claude Code** (one command, then restart the session): ```bash claude mcp add exchange \ -e EWS_SERVER_URL="https://mail.example.com/EWS/Exchange.asmx" \ -e EWS_EMAIL="[email protected]" \ -e EWS_USERNAME="DOMAIN\\user" \ -e EWS_PASSWORD="…" \ -e EWS_CAPABILITY_TIER="read" \ -e SEND_ENABLED="false" \ -e EWS_TZ="Europe/Vienna" \ -- uvx --from ews-mcp-orf ewsmcp ``` On Windows, Integrated Authentication is available as an explicit opt-in: ```bash EWS_AUTH_MODE=process \ EWS_SERVER_URL="https://mail.example.com/EWS/Exchange.asmx" \ EWS_EMAIL="[email protected]" \ uvx --from ews-mcp-orf ewsmcp ``` This uses the current Windows logon token through SSPI and does not use `EWS_USERNAME` or `EWS_PASSWORD`. The default `EWS_AUTH_MODE=credentials` remains portable across Windows, Linux and macOS. **Claude Desktop** — add to `claude_desktop_config.json`: ```json { "mcpServers": { "exchange": { "command": "uvx", "args": ["--from", "ews-mcp-orf", "ewsmcp"], "env": { "EWS_SERVER_URL": "https://mail.example.com/EWS/Exchange.asmx", …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.