# Dealwize (remote · api.dealwize.co)

Analyse B2B sales deals, uncover risks, stakeholders, next steps, and winning actions.

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `api.dealwize.co`: 85/100 (this document), [markdown](https://verifymcp.io/servers/co-dealwize-dealwize/api-v1-mcp.md), [page](https://verifymcp.io/servers/co-dealwize-dealwize/api-v1-mcp)
- remote · `api.dealwize.co`: 28/100, [markdown](https://verifymcp.io/servers/co-dealwize-dealwize/api-v1-mcp-sse.md), [page](https://verifymcp.io/servers/co-dealwize-dealwize/api-v1-mcp-sse)

## Channel facts

- Endpoint: `https://api.dealwize.co/api/v1/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1616 tokens (~115/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Dealwize MCP server?

Dealwize is a hosted endpoint at https://api.dealwize.co/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http co-dealwize-dealwize 'https://api.dealwize.co/api/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-dealwize-dealwize": {
      "url": "https://api.dealwize.co/api/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-dealwize-dealwize": {
      "type": "http",
      "url": "https://api.dealwize.co/api/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-dealwize-dealwize]
url = "https://api.dealwize.co/api/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-dealwize-dealwize": {
      "type": "remote",
      "url": "https://api.dealwize.co/api/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-dealwize-dealwize --url 'https://api.dealwize.co/api/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-dealwize-dealwize:
    url: "https://api.dealwize.co/api/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-dealwize-dealwize": {
      "Transport": "http",
      "Url": "https://api.dealwize.co/api/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-dealwize-dealwize -t streamable-http -u 'https://api.dealwize.co/api/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-dealwize-dealwize": {
      "type": "http",
      "url": "https://api.dealwize.co/api/v1/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-29 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 84, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 83, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (14)

### `analyze_deal` (~163 tokens)

Analyse a raw B2B sales call transcript, meeting notes, sales conversation, or email thread and produce a Dealwize Deal Health Intelligence assessment. Use this when the user wants to know whether a sales opportunity is genuinely progressing, likely to close, at risk of slipping, missing key stakeholders, weakly qualified, lacking a real champion, or needs a clear next action. Returns deal health, buyer commitment, brutal truth, strengths, risks, stakeholder intelligence, qualification gaps, next best action, and a Mutual Action Plan. This tool can be used for first-time deal analysis without an existing persistent Dealwize deal.

Input parameters:

- `name` (string): Optional opportunity or company name
- `transcript` (string, required): Raw sales meeting transcript, email thread, or call notes

### `get_deal_health` (~124 tokens)

Assess the health of a saved B2B sales opportunity using Dealwize Deal Health Intelligence and return a 0–100 health score with the reasons behind it. Use this when the user asks whether a deal is healthy, genuinely progressing, likely to close, likely to slip, at risk, forecastable, stalled, or worth pursuing. Consider buyer commitment, stakeholder engagement, champion strength, economic buyer access, timeline movement, procurement progress, qualification gaps, competitive pressure, and other deal signals.

Input parameters:

- `deal_id` (string, required): ID or slug of the deal opportunity

### `get_deal_risks` (~114 tokens)

Identify the most important hidden and explicit risks that could prevent a saved B2B sales opportunity from closing. Categorize risks across commercial, stakeholder, timing, procurement, technical, competitive, qualification, and buyer-commitment factors. Use this when the user asks what could kill the deal, why the deal might slip, what blockers exist, what is being overlooked, what could go wrong, or what the seller should be worried about.

Input parameters:

- `deal_id` (string, required): ID or slug of the deal opportunity

### `get_stakeholders` (~107 tokens)

Analyse the stakeholder landscape of a saved B2B sales opportunity, including champion strength, economic buyer access, decision makers, technical evaluators, procurement contacts, influencers, blockers, and missing stakeholders. Use this when the user asks who matters in the deal, whether they have a real champion, whether the economic buyer is engaged, who may block the purchase, who makes the decision, or which stakeholder is missing.

Input parameters:

- `deal_id` (string, required): ID or slug of the deal opportunity

### `get_next_best_action` (~116 tokens)

Determine the single highest-priority action the seller should take next to increase the probability of progressing or closing a saved B2B sales opportunity. Base the recommendation on deal health, buyer commitment, stakeholder gaps, risks, timeline, qualification gaps, procurement status, and current deal evidence. Use this when the user asks what they should do next, how to progress the deal, how to unblock it, or what the most important action is after a sales conversation.

Input parameters:

- `deal_id` (string, required): ID or slug of the deal opportunity

### `get_deal` (~106 tokens)

Retrieve the complete Dealwize intelligence record for a specific saved B2B sales opportunity. Includes deal reality, health, brutal truth, North Star goals, top risks, stakeholder intelligence, buyer commitment, qualification gaps, timeline context, and next best action. Use this when the user wants a comprehensive understanding, review, briefing, or summary of a specific deal rather than one individual aspect of it.

Input parameters:

- `deal_id` (string, required): UUID, ID, or slug of the deal opportunity

### `get_deals` (~129 tokens)

List the user's saved B2B sales opportunities in Dealwize with their current health scores, statuses, buyer commitment, North Star goals, and primary risks. Use this when the user wants an overview of their pipeline, asks which deals need attention, wants to compare opportunities, asks which deals are healthiest or riskiest, or wants to see their Dealwize deal board.

Input parameters:

- `limit` (integer): Items per page (max 50)
- `page` (integer): Page number for paginated results
- `search` (string): Optional search term to filter deals by name or company

### `list_deals` (~129 tokens)

List the user's saved B2B sales opportunities in Dealwize with their current health scores, statuses, buyer commitment, North Star goals, and primary risks. Use this when the user wants an overview of their pipeline, asks which deals need attention, wants to compare opportunities, asks which deals are healthiest or riskiest, or wants to see their Dealwize deal board.

Input parameters:

- `limit` (integer): Items per page (max 50)
- `page` (integer): Page number for paginated results
- `search` (string): Optional search term to filter deals by name or company

### `generate_mutual_action_plan` (~139 tokens)

Generate a structured buyer-facing Mutual Action Plan (MAP) for a B2B sales opportunity using the available deal evidence or transcript. Create logical phases, milestones, action items, owners, dependencies, and target deadlines that help the buyer and seller progress toward a successful purchasing decision. Use this when the user asks to create a MAP, build a close plan, create a joint action plan, turn a sales conversation into an execution plan, or define the steps required to close the deal.

Input parameters:

- `deal_id` (string, required): ID or slug of the deal opportunity
- `transcript` (string): Call transcript text or meeting notes to extract milestones from

### `get_mutual_action_plan` (~93 tokens)

Retrieve the current living Mutual Action Plan for a saved B2B sales opportunity, including phases, milestones, action items, owners, checklist items, and deadlines. Use this when the user asks to review the deal plan, check MAP progress, see outstanding actions, identify overdue milestones, or understand what buyer and seller actions remain before close.

Input parameters:

- `deal_id` (string, required): ID or slug of the deal opportunity

### `update_deal` (~171 tokens)

Update an existing saved B2B sales opportunity or ingest new sales evidence such as a call transcript, meeting notes, or conversation into the deal. New evidence should trigger the existing Dealwize intelligence process so health, risks, stakeholders, buyer commitment, qualification, next actions, and other relevant intelligence can be refreshed. Use this when the user provides new information about an existing deal or asks Dealwize to update its assessment.

Input parameters:

- `deal_id` (string, required): ID, UUID, or slug of the deal opportunity
- `name` (string): Optional updated name for the deal
- `status` (string): Optional status (e.g. draft, active, closed_won, closed_lost)
- `transcript` (string): Optional new call transcript, email thread, or meeting notes to re-analyze

### `share_deal` (~85 tokens)

Create a safe shareable link for approved Dealwize deal intelligence or buyer-facing deal content that can be viewed without requiring the recipient to authenticate. Use this when the user asks to share a deal diagnosis, deal intelligence one-pager, deal board, or buyer-facing deal information with another person.

Input parameters:

- `deal_id` (string, required): ID or slug of the deal opportunity to share

### `get_login_url` (~80 tokens)

Generate a secure Dealwize authentication URL when the user needs to sign in, create or access their Dealwize account, authorize access to private Dealwize resources, or continue from a temporary analysis into a persistent Dealwize workspace.

Input parameters:

- `redirect_to` (string): Optional destination path after login (e.g. '/dashboard' or '/settings')

### `connect_account` (~60 tokens)

Start the authorization flow for connecting the current AI client to the user's Dealwize account. Use this when the user wants the AI client to access saved private deals, persistent Dealwize intelligence, living Mutual Action Plans, or other authenticated Dealwize resources.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-dealwize-dealwize/api-v1-mcp#diagnostics

## Score history

- 2026-09-29: 85
- 2026-09-28: 84
- 2026-09-27: 84
- 2026-09-26: 83
- 2026-09-25: 83
- 2026-09-24: 83
- 2026-09-23: 82
- 2026-09-22: 82
- 2026-09-21: 81
- 2026-09-20: 81
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 79
- 2026-09-16: 79
- 2026-09-15: 78
- 2026-09-14: 78
- 2026-09-13: 77
- 2026-09-12: 77
- 2026-09-11: 76
- 2026-09-10: 76
- 2026-09-09: 76
- 2026-09-08: 75
- 2026-09-07: 75
- 2026-09-06: 74
- 2026-09-05: 74
- 2026-09-04: 73

## Common questions

### What is the Dealwize MCP server?

Dealwize is an MCP server listed in the public MCP registry as co.dealwize/dealwize. Analyse B2B sales deals, uncover risks, stakeholders, next steps, and winning actions. This page covers its hosted endpoint (https://api.dealwize.co/api/v1/mcp).

### Is the Dealwize MCP server safe to use?

Dealwize scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Dealwize MCP server expose?

Dealwize exposes 14 tools: analyze_deal, get_deal_health, get_deal_risks, get_stakeholders, get_next_best_action, and 9 more. Their descriptions and schemas cost roughly 1,616 tokens of context every time the server is loaded.

### Does the Dealwize MCP server require authentication?

No. We connected to Dealwize without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Dealwize MCP server still maintained?

Dealwize is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.dealwize.co/api/v1/mcp
- Authorisation metadata: https://api.dealwize.co/.well-known/oauth-protected-resource/api/v1/mcp
- Website: https://dealwize.co/mcp
- Changelog RSS feed: https://verifymcp.io/servers/co-dealwize-dealwize/api-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-dealwize-dealwize/api-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-dealwize-dealwize/api-v1-mcp