Domain Intel MCP vs Ms 365 MCP Server

A side-by-side look at the Domain Intel MCP and Ms 365 MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Domain Intel MCP logoDomain Intel MCPCommunication · Remote HTTP/SSEDomain & company intel for AI agents: RDAP, DNS, email deliverability, tech stack. No API keys.69GreatAuth: no auth requiredMs 365 MCP Server logoMs 365 MCP ServerCommunication · Local subprocess (stdio)MCP server that connects to Microsoft Office and the whole Microsoft 365 suite using Graph API (including Outlook, mail, files, Excel, calendar)73GreatAuth: oauth 2.0

Verdict: choose Domain Intel MCP for communication work over a hosted endpoint; choose Ms 365 MCP Server for communication as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Domain Intel MCP logoChoose Domain Intel MCP when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
  • You want tools like domain_report, domain_intel, dns_lookup.
Explore Domain Intel MCP

Ms 365 MCP Server logoChoose Ms 365 MCP Server when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
  • You want tools like login, logout, verify-login.
Explore Ms 365 MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDomain Intel MCP logoDomain Intel MCPMs 365 MCP Server logoMs 365 MCP Server
CategoryCommunicationCommunication
Quality signal69/100 · Great73/100 · Great
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNo auth requiredOAuth 2.0
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars11,076
Directory activity 2 views 0 installs 0 upvotes 8 views 0 installs 0 upvotes
Tools619

Tools & capabilities

Domain Intel MCP tools 6

  • domain_reportOne-call full dossier on a domain: registration (RDAP), DNS records, email deliverability, and website tech stack, combined into a single report. Use for fast lead qualification, company research, or recon without four separate calls.
  • domain_intelRegistration intelligence for a domain via RDAP (the modern WHOIS). Returns registrar, creation/expiration/last-changed dates, domain age in years, EPP status codes, nameservers, DNSSEC state, and abuse contact. Use to vet a company, assess a lead, or judge how established a domain is.
  • dns_lookupLook up DNS records for a domain via Cloudflare DNS-over-HTTPS. Returns A, AAAA, MX, NS, TXT, CNAME, and SOA records. Use to see where a domain is hosted, who runs its mail and DNS, and what verification/policy TXT records it publishes.
  • email_deliverabilityAssess whether a domain (or the domain of an email address) can receive mail and how strong its sender authentication is. Returns MX presence, SPF and DMARC policy, whether it's a free consumer provider (gmail, etc.) or a known disposable/temp-mail provider, and an overall verdict. Use to qualify leads and flag throwaway signups.
  • tech_stackFingerprint the technology behind a website by fetching its homepage. Detects web server, CMS/framework (WordPress, Shopify, Next.js, etc.), CDN, analytics, and returns the page title, final URL after redirects, and key response headers. Use for competitive research and lead enrichment.
  • subdomainsDiscover a domain's public subdomains (app., api., staging., and so on) from Certificate Transparency logs, querying crt.sh and Cert Spotter in parallel and returning whichever answers first. Useful for mapping a company's public attack surface or infrastructure. If both sources are down the call returns an error rather than an empty list.

Ms 365 MCP Server tools 19

  • loginAuthenticate with Microsoft account
  • logoutLog out from Microsoft account
  • verify-loginCheck current Microsoft authentication status
  • list-accountsList all Microsoft accounts configured in this server. Use this to discover available account emails before making tool calls. Reflects accounts added mid-session via --login.
  • select-accountSelect a Microsoft account as the default. Accepts email address (e.g. user@outlook.com) or account ID. Use list-accounts to discover available accounts.
  • remove-accountRemove a Microsoft account from the cache. Accepts email address (e.g. user@outlook.com) or account ID. Use list-accounts to discover available accounts.
  • graph-batchCombine up to 20 Graph requests into a single HTTP call. Body: { requests: [{ id: '1', method: 'GET'|'POST'|'PATCH'|'DELETE', url: '/me/messages?$top=5', headers?: {...}, body?: {...}, dependsOn?: ['1'] }, ...] }. Returns { responses: [{ id, status, body, headers }] } in arbitrary order — match by id. Use cases: (1) parallelize many small reads (e.g. fetch 15 mail messages by id in one round-trip); (2) sequence dependent writes via dependsOn; (3) batch many Excel range writes into one call to dramatically reduce latency on large workbook builds. Note: each sub-request URL is relative to the Graph version root (/me/..., /drives/..., NOT https://graph.microsoft.com/v1.0/...). 💡 TIP: Combine up to 20 Graph requests into a single HTTP call. Body: { requests: [{ id: '1', method: 'GET'|'POST'|'PATCH'|'DELETE', url: '/me/messages?$top=5', headers?: {...}, body?: {...}, dependsOn?: ['1'] }, ...] }. Returns { responses: [{ id, status, body, headers }] } in arbitrary order — match by id. Use cases: (1) parallelize many small reads (e.g. fetch 15 mail messages by id in one round-trip); (2) sequence dependent writes via dependsOn; (3) batch many Excel range writes into one call to dramatically reduce latency on large workbook builds. Note: each sub-request URL is relative to the Graph version root (/me/..., /drives/..., NOT https://graph.microsoft.com/v1.0/...).
  • list-subscriptionsRetrieve the properties and relationships of webhook subscriptions, based on the app ID, the user, and the user's role with a tenant. The content of the response depends on the context in which the app is calling; for details, see the scenarios in the Permissions section. 💡 TIP: Lists webhook subscriptions owned by the current app/user. Returns id, resource, changeType, notificationUrl, expirationDateTime, clientState. Use $filter=resource eq '/me/messages' to find subscriptions for a specific resource. No dedicated 'Subscription.*' scope exists — the caller must already have a read permission for the subscribed resource (e.g. Mail.Read for /me/messages), which is supplied by the tool that reads that resource.
  • create-subscriptionSubscribes a listener application to receive change notifications when the requested type of changes occur to the specified resource in Microsoft Graph. To identify the resources for which you can create subscriptions and the limitations on subscriptions, see Set up notifications for changes in resource data: Supported resources. Some resources support rich notifications, that is, notifications that include resource data. For more information about these resources, see Set up change notifications that include resource data: Supported resources. 💡 TIP: Creates a webhook subscription for change notifications. Required body: { changeType (comma-separated: 'created,updated,deleted'), notificationUrl (HTTPS, must validate with token echo), resource (e.g. '/me/mailFolders/inbox/messages', '/users/{id}/events', '/teams/{id}/channels/{id}/messages'), expirationDateTime (ISO 8601, max varies by resource type — 1 hour for calls, 24h for messages, 3 days for mail), clientState (opaque string returned in notifications, for validation) }. Optional: includeResourceData (true enables rich notifications, requires encryptionCertificate + encryptionCertificateId). No dedicated scope — caller must have a read permission for the target resource (e.g. Mail.Read, Calendars.Read, ChannelMessage.Read.All, Files.Read.All).
  • get-subscriptionRetrieve the properties and relationships of a subscription. See the table in the Permissions section for the list of resources that support subscribing to change notifications. 💡 TIP: Gets a specific webhook subscription by id. Use list-subscriptions to find the id. Returns full subscription details including resource, changeType, notificationUrl, expirationDateTime, applicationId.
  • update-subscriptionRenew a subscription by extending its expiry time. The table in the Permissions section lists the resources that support subscribing to change notifications. Subscriptions expire after a length of time that varies by resource type. In order to avoid missing change notifications, an app should renew its subscriptions well in advance of their expiry date. See subscription for maximum length of a subscription for each resource type. 💡 TIP: Renews a webhook subscription by extending its expiration. Body: { expirationDateTime (ISO 8601, new expiry) }. Call before the current expirationDateTime to avoid missing notifications. Max extension varies by resource type — check Microsoft Graph docs for subscription limits.
  • delete-subscriptionDelete a subscription. For the list of resources that support subscribing to change notifications, see the table in the Permissions section. 💡 TIP: Deletes a webhook subscription. No further change notifications will be sent. Use this to clean up stale subscriptions or stop receiving notifications. Use list-subscriptions to find the id.
  • +7 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Domain Intel MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "domain-intel-mcp": {
      "url": "https://domain.datakoot.com/mcp"
    }
  }
}

Ms 365 MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "softeria-ms-365-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@softeria/ms-365-mcp-server"
      ]
    }
  }
}

Frequently asked questions

Domain Intel MCP is categorized under Communication and uses a remote HTTP/SSE transport. Ms 365 MCP Server belongs to Communication and uses a local stdio subprocess. Pick Domain Intel MCP for communication work and Ms 365 MCP Server for communication.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Domain Intel MCP has no declared pricing — check the project's own site. Auth: no auth required. Ms 365 MCP Server is listed as free. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add domain-intel-mcp and softeria-ms-365-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Domain Intel MCP has a quality signal of 69/100 (Great) with 2 views, 0 installs and 1 GitHub stars. Ms 365 MCP Server has 73/100 (Great) with 8 views, 0 installs and 1,076 GitHub stars.