Outlook SNDS MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Outlook SNDS MCPShow my latest SNDS data report"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Outlook SNDS MCP
An MCP server that brings the Outlook.com Smart Network Data Services (SNDS) REST API into Claude / Cowork / Claude Desktop and any other MCP client.
Sign in once with your Microsoft account — the server handles the full OAuth 2.0
authorization-code + PKCE flow over a loopback (http://localhost) redirect,
caches the tokens, and refreshes them automatically. Then just ask for your IP
reputation data.
SNDS gives senders per-IP insight into how Outlook.com sees their mail: volume, complaint rates, spam-filter verdicts, trap hits, and block/bot status.
Built & maintained by the Postmaster+ team at OptiPub.
Install
From a release (recommended)
Download
outlook-snds.mcpbfrom the latest release.In Cowork / Claude Desktop: Settings → Capabilities → install extension, pick the file (or just double-click it).
No configuration required.
From source — see Build.
Related MCP server: Resend MCP Server
Use with other MCP clients (Cursor, VS Code, Windsurf, …)
The .mcpb is just a packaging convenience for Claude Desktop / Cowork.
Underneath, this is a standard stdio MCP server, so any client that runs
local MCP servers can use it directly — no .mcpb required. Just point the
client at server/index.js.
Clone or download the repo first, then add a server entry:
Cursor — edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):
{
"mcpServers": {
"outlook-snds": {
"command": "node",
"args": ["/absolute/path/to/outlook-snds-mcp/server/index.js"]
}
}
}VS Code (.vscode/mcp.json), Windsurf, Claude Desktop (manual
config), and most other clients use the same command + args shape — only the
config file location differs. Optional environment overrides (see
Configuration) go in an "env": { ... } object.
The first tool call opens your browser for the SNDS sign-in, exactly as in Cowork — the localhost OAuth loopback works on any local desktop client.
Remote-only clients (e.g. Perplexity, ChatGPT connectors): these accept only a remote HTTPS MCP server URL, not a local command, so this stdio build can't be added directly. Using it there would require hosting it as a remote server with a web-based OAuth redirect.
Usage
Run snds_authenticate once (your browser opens for a Microsoft sign-in), then:
Ask | Tool |
"Sign me in to SNDS" |
|
"Am I signed in to SNDS?" |
|
"Show my latest SNDS data report" |
|
"SNDS data for 2026-12-31" |
|
"SNDS data for 1.2.3.4 on 2026-12-31" |
|
"Any blocked/bot/junked IPs?" |
|
"Sign me out of SNDS" |
|
get_data_report takes an optional date (yyyy-MM-dd) and an optional ip
(IPv4). A date is required to filter by IP, because the API path is
/api/report/data/{date}/{ip}.
How authentication works
Field | Value |
Authorize |
|
Token |
|
Client ID |
|
Scope |
|
Redirect |
|
On sign-in the server starts a short-lived HTTP listener on 127.0.0.1, opens
your browser to the Microsoft login, receives the authorization code on the
loopback URL, and exchanges it (with the PKCE code verifier) for tokens.
No secrets ship in this repo. It's a public OAuth client using PKCE — there
is no client secret. Tokens are stored only on your machine at
~/.snds-mcp/tokens.json with 0600 permissions, and are git-ignored.
REST endpoints wrapped
Base URL: https://substrate.office.com/ip-domain-management-snds
GET /api/report/data/{date?}/{ip?}— IP Data reportGET /api/report/status/ip— IP Status report
Configuration (optional)
Everything defaults to the SNDS portal values. Override via environment variables if you need to:
Variable | Default |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Build
Requires Node 18+.
npx @anthropic-ai/mcpb validate manifest.json
npx @anthropic-ai/mcpb pack . outlook-snds.mcpbPushing a tag like v1.0.0 triggers CI to validate, pack, and attach the
.mcpb to a GitHub Release automatically (see
.github/workflows/release.yml).
Why zero dependencies
The runtime uses only Node.js built-ins (http, https, crypto,
readline). That keeps the bundle tiny (~11 KB), removes supply-chain risk, and
means there's nothing to npm install at runtime.
Contributing
PRs and issues welcome — see CONTRIBUTING.md.
License
MIT © OptiPub
Not affiliated with or endorsed by Microsoft. "Outlook", "Outlook.com", and "SNDS" are trademarks of Microsoft Corporation.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/optipub/outlook-snds-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server