Productivity · Remote MCP server
Dealwize
Analyse B2B sales deals, uncover risks, stakeholders, next steps, and winning actions.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
co.dealwize/dealwize- Version
- 1.0.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP, SSE (HTTP + Server-Sent Events)
- Published
- 2026-09-04
- Updated
- 2026-09-04
- Publisher
- co.dealwize
- Namespace
- Namespace verified by the MCP Registry via the domain dealwize.co · how
- Website
- dealwize.co/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.dealwize.co/api/v1/mcp | Authorization (required, secret) |
| SSE (HTTP + Server-Sent Events) | https://api.dealwize.co/api/v1/mcp/sse | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://api.dealwize.co/api/v1/mcp(HTTP)- Reachable
- Yes (HTTP 200)
- Handshake
- dealwize-mcp 1.30.0 · protocol 2025-06-18
- Tools discovered
14 - show names
analyze_deal,get_deal_health,get_deal_risks,get_stakeholders,get_next_best_action,get_deal,get_deals,list_deals,generate_mutual_action_plan,get_mutual_action_plan,update_deal,share_deal,get_login_url,connect_account- Checked on
- 2026-10-05
- Endpoint
https://api.dealwize.co/api/v1/mcp/sse(SSE)- Reachable
- Yes (HTTP 200)
- SSE stream
- Opened and named its message endpoint (not used further)
- Checked on
- 2026-10-05
How to connect Dealwize
Dealwize is a remote MCP server: there is nothing to install. Its endpoint is https://api.dealwize.co/api/v1/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
It also lists an endpoint on the older SSE transport https://api.dealwize.co/api/v1/mcp/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| DazbenchTask management your AI agents can actually run. One line becomes a context-ready task over MCP. | Remote · HTTPLive check: sign-in required |
| Dead Simple EmailGive an agent its own inbox: send, receive, and pull signup codes from real email. | Remote & Local · HTTP, stdioLive check: sign-in required |
| dead-letterConvert.eml and.mbox email to clean Markdown for RAG, LLM pipelines, and local knowledge bases. | Local · stdio |
| DealboardSimple deal tracker with pipeline cards, notes, goals, reports, and AI-powered deal updates. | Remote · HTTPLive check: sign-in required |
| decantr-ai MCP-SERVERStable eight-tool MCP server for changed-UI assurance, authority-aware UI task context, and repair. | Local · stdio |
| DecernMCP server for Decern CRM - contacts, deals, pipelines, tasks, and approvals. | Local · stdio |
| dechonet.com20 domain recon tools for AI agents: DNS, SSL, headers, email, subdomains, lookalikes, changes. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| DeckExtractDownload DocSend and Papermark decks as PDF or PPTX, including email-gated and protected links. | Remote · HTTPLive check: ✓ handshake |