Outlook SNDS

io.github.optipub由 GitHub 帳號 optipub 發布v1.0.4更新於 Oct 24, 2026

Outlook.com SNDS IP Data and IP Status reports via the OAuth-secured REST API.

已驗證STDIO僅桌面溝通與協作安全與監控

概覽

AI 產生的概覽

一個本機 MCP 伺服器,用 Microsoft 帳戶登入 Outlook.com SNDS,並回傳你寄信 IP 的逐 IP 郵件信譽報告。

可以做什麼
透過 Microsoft OAuth 流程登入與登出 SNDS,並查詢目前是否已登入。依日期取得 IP Data 報告,可再篩選單一 IPv4 位址。取得 IP Status 報告,查看被封鎖、判定為機器人或垃圾郵件的 IP。報告涵蓋 Outlook.com 觀點下的寄信量、投訴率、垃圾郵件過濾判定、陷阱命中與封鎖狀態。
適用情境
當你向 Outlook.com 寄信,希望助理直接取得 SNDS 的 IP 信譽資料、投訴率和封鎖狀態,而不必手動造訪入口網站時使用。適合與瀏覽器同機的本機桌面 MCP 用戶端。
執行需求
以本機 stdio 程序在桌面機器上執行;從原始碼執行需要 Node.js 18 以上版本,也可在 Claude Desktop 或 Cowork 中安裝打包擴充功能。需要一個具 SNDS 存取權限的 Microsoft 帳戶,首次呼叫工具會開啟瀏覽器登入。需要連線至 Microsoft 登入服務與 SNDS API 的網路。選用環境變數可覆寫用戶端 ID、授權單位、範圍、API 位址、權杖目錄與逾時。
安裝前請注意
登入後伺服器會取得 OAuth 權杖,權杖以受限權限快取在本機權杖目錄中;登出可清除。它從 Microsoft 服務讀取你的 SNDS 信譽資料,報告內容會傳送給該第三方。工具對 SNDS 為唯讀,但登入期間伺服器會開啟本機回環監聽並開啟瀏覽器。僅接受 HTTPS URL 的遠端用戶端無法直接使用此 stdio 版本。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Outlook SNDS,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Outlook SNDS MCP

[License: MIT] [Built with MCPB] [Node] [Dependencies]

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)

  1. Download outlook-snds.mcpb from the latest release.
  2. In Cowork / Claude Desktop: Settings → Capabilities → install extension, pick the file (or just double-click it).
  3. No configuration required.

From source — see Build.

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):

json
{  "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:

AskTool
"Sign me in to SNDS"snds_authenticate
"Am I signed in to SNDS?"snds_auth_status
"Show my latest SNDS data report"get_data_report
"SNDS data for 2026-12-31"get_data_report { date: "2026-12-31" }
"SNDS data for 1.2.3.4 on 2026-12-31"get_data_report { date: "2026-12-31", ip: "1.2.3.4" }
"Any blocked/bot/junked IPs?"get_ip_status
"Sign me out of SNDS"snds_sign_out

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

FieldValue
Authorizehttps://login.microsoftonline.com/consumers/oauth2/v2.0/authorize
Tokenhttps://login.microsoftonline.com/consumers/oauth2/v2.0/token
Client IDa53a6cc1-a1cd-46f7-a4aa-281cdabec33c (the SNDS portal's public client)
Scopea53a6cc1-a1cd-46f7-a4aa-281cdabec33c/.default offline_access openid profile
Redirecthttp://localhost:<dynamic-port> (loopback)

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 report
  • GET /api/report/status/ip — IP Status report

Configuration (optional)

Everything defaults to the SNDS portal values. Override via environment variables if you need to:

VariableDefault
SNDS_CLIENT_IDa53a6cc1-a1cd-46f7-a4aa-281cdabec33c
SNDS_AUTHORITYhttps://login.microsoftonline.com/consumers
SNDS_SCOPE<client-id>/.default offline_access openid profile
SNDS_API_BASEhttps://substrate.office.com/ip-domain-management-snds
SNDS_TOKEN_DIR~/.snds-mcp
SNDS_LOGIN_TIMEOUT_MS180000
SNDS_REQUEST_TIMEOUT_MS60000

Build

Requires Node 18+.

bash
npx @anthropic-ai/mcpb validate manifest.jsonnpx @anthropic-ai/mcpb pack . outlook-snds.mcpb

Pushing 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.

來源:README.md,提交 be596bb

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v1.0.4最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分