Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Dealwize

REMOTE · API.DEALWIZE.CO · 2 COMPONENTS · SCANNED SEP 29

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

+3 this week 85 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security77
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

remote · api.dealwize.co

# add to Claude Code
claude mcp add --transport http co-dealwize-dealwize 'https://api.dealwize.co/api/v1/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "co-dealwize-dealwize": {
      "url": "https://api.dealwize.co/api/v1/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "co-dealwize-dealwize": {
      "type": "http",
      "url": "https://api.dealwize.co/api/v1/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add co-dealwize-dealwize --url 'https://api.dealwize.co/api/v1/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  co-dealwize-dealwize:
    url: "https://api.dealwize.co/api/v1/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "co-dealwize-dealwize": {
      "Transport": "http",
      "Url": "https://api.dealwize.co/api/v1/mcp"
    }
  }
}
# add to Vellum
assistant mcp add co-dealwize-dealwize -t streamable-http -u 'https://api.dealwize.co/api/v1/mcp'
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 29 Sept 26 +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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +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.

  • 22 Sept 26 +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.

  • 20 Sept 26 +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.

  • 18 Sept 26 +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.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 29 Sept 2026 · Probed https://api.dealwize.co/api/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.dealwize.co CN=YE2,O=Let's Encrypt,C=US 9 Aug 2026 7 Nov 2026 ECDSA 256 ECDSA-SHA384 6d8eabca8e5935b68306b094b8cac1d62ec
SANs: api.dealwize.co
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.dealwize.co. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
co. present 7786 8 Verified
dealwize.co. present 48541 8 Verified
api.dealwize.co. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.dealwize.co/api/v1/mcp Verified 200
http (plaintext) http://api.dealwize.co/api/v1/mcp HTTPS enforced 301 https://api.dealwize.co/api/v1/mcp
MCP tools · 14 exposed · ~1,616 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_deal ~163

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.

NameTypeReqDescription
namestring–Optional opportunity or company name
transcriptstringyesRaw sales meeting transcript, email thread, or call notes

No output schema declared.

No examples provided.

connect_account ~60

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

generate_mutual_action_plan ~139

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.

NameTypeReqDescription
deal_idstringyesID or slug of the deal opportunity
transcriptstring–Call transcript text or meeting notes to extract milestones from

No output schema declared.

No examples provided.

get_deal ~106

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.

NameTypeReqDescription
deal_idstringyesUUID, ID, or slug of the deal opportunity

No output schema declared.

No examples provided.

get_deal_health ~124

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.

NameTypeReqDescription
deal_idstringyesID or slug of the deal opportunity

No output schema declared.

No examples provided.

get_deal_risks ~114

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.

NameTypeReqDescription
deal_idstringyesID or slug of the deal opportunity

No output schema declared.

No examples provided.

get_deals ~129

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.

NameTypeReqDescription
limitinteger–Items per page (max 50)
pageinteger–Page number for paginated results
searchstring–Optional search term to filter deals by name or company

No output schema declared.

No examples provided.

get_login_url ~80

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.

NameTypeReqDescription
redirect_tostring–Optional destination path after login (e.g. '/dashboard' or '/settings')

No output schema declared.

No examples provided.

get_mutual_action_plan ~93

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.

NameTypeReqDescription
deal_idstringyesID or slug of the deal opportunity

No output schema declared.

No examples provided.

get_next_best_action ~116

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.

NameTypeReqDescription
deal_idstringyesID or slug of the deal opportunity

No output schema declared.

No examples provided.

get_stakeholders ~107

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.

NameTypeReqDescription
deal_idstringyesID or slug of the deal opportunity

No output schema declared.

No examples provided.

list_deals ~129

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.

NameTypeReqDescription
limitinteger–Items per page (max 50)
pageinteger–Page number for paginated results
searchstring–Optional search term to filter deals by name or company

No output schema declared.

No examples provided.

share_deal ~85

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.

NameTypeReqDescription
deal_idstringyesID or slug of the deal opportunity to share

No output schema declared.

No examples provided.

update_deal ~171

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.

NameTypeReqDescription
deal_idstringyesID, UUID, or slug of the deal opportunity
namestring–Optional updated name for the deal
statusstring–Optional status (e.g. draft, active, closed_won, closed_lost)
transcriptstring–Optional new call transcript, email thread, or meeting notes to re-analyze

No output schema declared.

No examples provided.

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.