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.

Dealroom

REMOTE · DEALROOM.TODO.LAW

Make a contract in one call, or negotiate it clause by clause with a published compromise formula.

+3 this week 73 Trust /100

Last scanned (15 hours ago)

Scores higher than 64% of remote servers

Reachable. Last reached 23 Oct 2026.

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 Security63
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2388 tokens (~132/item across 18 items; 18 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 Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 73% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 19 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
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.

  • 22 Oct 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.

  • 20 Oct 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.

  • 18 Oct 26 +1

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

  • 16 Oct 26 +1

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

  • 14 Oct 26 +1
    • Tool “generate_contract” rewrote its description, which is the text the model reads security
    • “generate_contract” reworded the description of “counterparty” cosmetic
    • “generate_contract” reworded the description of “party” cosmetic
  • 13 Oct 26 0
    • Tool “list_contract_types” rewrote its description, which is the text the model reads security
    • “list_contract_types” added an optional parameter “contractType” cosmetic
    • “list_contract_types” added an optional parameter “summary” cosmetic
  • 11 Oct 26 +1

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

  • 10 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 13. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 4 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 23 Oct 2026 · Probed https://dealroom.todo.law/api/v1/agent/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dealroom.todo.law CN=YR2,O=Let's Encrypt,C=US 14 Oct 2026 12 Jan 2027 RSA 2048 SHA256-RSA 5b216e33dffcd809053f582cd4029dc3e3b
SANs: dealroom.todo.law
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of dealroom.todo.law. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
law. present 56101 13 Verified
todo.law. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://t.sealmetrics.com https://accounts.google.com; style-src 'self' 'unsafe-inline' https://accounts.google.com; img-src 'self' data: blob: https:; font-src 'self' data:; media-src 'self' blob: https:; frame-src https://accounts.google.com; object-src 'none'; base-uri 'self'; form-action 'self' https://accounts.google.com https://checkout.stripe.com https://billing.stripe.com; frame-ancestors 'none'; connect-src 'self' https:
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://dealroom.todo.law/api/v1/agent/mcp Verified 200
http (plaintext) http://dealroom.todo.law/api/v1/agent/mcp HTTPS enforced 308 https://dealroom.todo.law/api/v1/agent/mcp
MCP tools · 18 exposed · ~2,308 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
buy_credits ~84

Open a hosted checkout for a pack of ten contract credits for this API key's customer (any of its keys can spend them). Returns checkoutUrl for a person to open in a browser; the credits arrive when the payment succeeds. Answers 409 where payments are off.

NameTypeReqDescription
currencystring––
returnUrlstring–URL to return to after checkout

No output schema declared.

No examples provided.

create_playbook ~119

Create a negotiation playbook defining preferences for each clause: preferred option, priority (1-5), flexibility (1-5), red lines, and acceptable alternatives.

NameTypeReqDescription
contractLanguagestring––
contractTypestringyesContract type code: one from list_contract_types, or an A2A_ agent-to-agent protocol type from list_templates (those are negotiated only, never made with generate_contract)
entriesarrayyes–
governingLawstringyes–
namestringyesUnique playbook name

No output schema declared.

No examples provided.

delete_deal ~159

Delete one of your single-party deals and its data: the parties, the other side's details, the clause choices, the inputs and the contract (documents are made on request and never stored). This cannot be undone. Only the account that made the deal can delete it; for any other account it does not exist (HTTP 404, also when it was already deleted). A deal another party takes part in, such as a two-party negotiation, is refused with HTTP 409 and nothing is deleted. The payment record is kept for billing (amount, date, account and deal id, no names or contract text), and a spent credit is not given back.

NameTypeReqDescription
dealIdstringyesAgent deal id (dealId from generate_contract)

No output schema declared.

No examples provided.

download_contract ~139

Download the agreed contract as Markdown, HTML, PDF, DOCX or TXT (Markdown by default: agents read it best). Negotiation is free; the contract is paid when its document is first fetched: one prepaid credit of the customer is spent (any of its keys draws on the one balance). Later fetches of the same deal are free. With no credit left the answer is HTTP 402 with code PAYMENT_REQUIRED and the link to buy credits.

NameTypeReqDescription
dealIdstringyesAgent deal room ID
formatstring–md (Markdown) or html for agents and tools; pdf, docx or txt for people and printers

No output schema declared.

No examples provided.

explain_options ~134

The options of one clause, each with its description and its pros and cons for each party, plus the clause's trade-off text, exactly as the template holds them. Nothing is ranked or recommended; when the template has no such text, the answer says so. Free (no credit).

NameTypeReqDescription
clausestringyesClause id (from get_template) or the clause title
contractTypestringyesContract type code: one from list_contract_types, or an A2A_ agent-to-agent protocol type from list_templates (those are negotiated only, never made with generate_contract)
langstring––

No output schema declared.

No examples provided.

find_template ~151

Describe the matter in your own words; Dealroom answers with the contract types whose names or usual terms appear in the description (code, title, guide link), or "No template covers this. Such matters are usually handled by a lawyer." The matching is by words, with no AI model. A lawsuit or claim received, a subpoena, a data breach or a letter from a regulator is flagged as a time-sensitive matter outside the templates (outsideTemplates). It does not say what the user needs and names no lawyer. Free; no API key needed.

NameTypeReqDescription
langstring–Language of titles, links and the message
querystringyesThe matter in plain words, in English or Spanish

No output schema declared.

No examples provided.

generate_contract ~422

Make a finished contract in one call: give the contract type, your side's details and, if you know them, the other side's. Clauses you leave out take the template's middle-ground option (the most neutral one; for an optional clause such as non-solicitation, none), never simply the first option listed. One prepaid credit is spent (the same price as any contract); with no credit the answer is HTTP 402 with code PAYMENT_REQUIRED and nothing is created. Returns the contract as Markdown, then the deal id, the link where the person can read it in Dealroom and the Markdown, HTML, PDF, DOCX and TXT links (free to fetch again).

NameTypeReqDescription
clausesobject–Optional clause choices: clause id to option code (see get_template)
contractTypestringyesCode (for example NDA) or guide slug (for example nda), from list_contract_types
counterpartyobject–The other side, with its address and jurisdiction of incorporation when you know them. Left out: its block stays blank for it to complete.
governingLawstring–Required when the contract type offers more than one
idempotencyKeystring–Send the same value when retrying, so a retry never makes or charges a second contract
inlinestring–The contract itself in the answer: md (Markdown, the default here), html or txt
languagestring––
partyobjectyesYour side (the side the API key acts for). Send every detail you have: only what you send is written into the contract.
rolestring–DPA and BAA only: the role you take (see roles in list_contract_types)
termsobject–Inputs by id (see inputs in list_contract_types). Send every required input in terms. A required input with a default can be left out: the default is applied.
titlestring–Name of the deal; made from the parties when left out

No output schema declared.

No examples provided.

get_credit_balance ~34

Remaining contract credits of this API key's customer (one balance shared by all of its keys) and the latest ledger entries.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_deadlines ~182

A small public calendar of statutory dates: the Section 83(b) election (30 days after the stock is transferred), the SEC Form D notice (15 calendar days after the first sale) and the Delaware annual report and franchise tax (1 March). Give grantDate or firstSaleDate to count the due date. Each item carries its official source and is marked "Verify with the official source." General public dates, not advice. Free; no API key needed.

NameTypeReqDescription
firstSaleDatestring–Date of the first sale of securities (YYYY-MM-DD), for Form D
grantDatestring–Date the stock was transferred or granted (YYYY-MM-DD), for the 83(b) election
langstring––
yearinteger–Year of the Delaware due date; left out, the next 1 March

No output schema declared.

No examples provided.

get_deal ~37

Get deal details including per-clause agreed options, satisfaction scores, and reasoning.

NameTypeReqDescription
dealIdstringyesAgent deal room ID

No output schema declared.

No examples provided.

get_subscriptions ~33

List earlier per-skill subscriptions and their status. Skills are no longer sold one by one; every template is included.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_template ~69

Get full details for a specific contract template including all clauses and their options with bias values.

NameTypeReqDescription
contractTypestringyesContract type code: one from list_contract_types, or an A2A_ agent-to-agent protocol type from list_templates (those are negotiated only, never made with generate_contract)

No output schema declared.

No examples provided.

initiate_negotiation ~86

Start a new contract negotiation. Returns a negotiation token for the respondent to join.

NameTypeReqDescription
dealNamestringyesHuman-readable deal name
initiatorCompanystring––
initiatorEmailstringyes–
playbookIdstringyesID of your playbook
respondentCompanystring––
respondentEmailstring––

No output schema declared.

No examples provided.

join_negotiation ~76

Join an existing negotiation as the respondent. Triggers automatic compromise resolution and returns the result.

NameTypeReqDescription
negotiationTokenstringyesToken from the initiator
playbookIdstringyesID of your playbook (must match contract type)
respondentCompanystring––
respondentEmailstringyes–

No output schema declared.

No examples provided.

list_contract_types ~220

Every contract type Dealroom can make, with the code to use as contractType, the guide slug, the governing laws and languages it is offered in, the role the caller can take (DPA and BAA only) and the inputs it asks for. Each input says whether it is required and, when it has one, its default; mustSend marks the required inputs without a default. Send every required input in terms. A required input with a default can be left out: the default is applied. Call this first to know what to ask the user. Send contractType to get one type with its inputs, or summary true to get every type without its inputs (a short list of codes). No API key needed.

NameTypeReqDescription
contractTypestring–Optional: one code (for example DPA) or guide slug; only that type is returned, with its inputs
langstring–Language of names and labels
summaryboolean–Optional: leave the inputs out of each type (each then carries inputCount)

No output schema declared.

No examples provided.

list_obligations ~116

What a contract commits its parties to and the dates it states: the obligations ledger (recurring and event-driven duties, for the DPA today) and, for every contract type, the date inputs, the term, notice and renewal inputs and the agreed option of each term, renewal, termination, notice or duration clause. Facts as the contract states them; the contract text governs. Free (no credit).

NameTypeReqDescription
dealIdstringyesAgent deal id (dealId from generate_contract)
langstring––

No output schema declared.

No examples provided.

list_templates ~95

List available contract templates with clauses, options, and bias values. Use this to understand which contract types are available and what options exist for each clause. Pass `query` to search by code, abbreviation or name in English or Spanish ("nda", "dpa", "hipaa", "confidencialidad"), best match first.

NameTypeReqDescription
querystring–Optional search: contract code, abbreviation or name (English or Spanish)

No output schema declared.

No examples provided.

share_with_attorney ~152

Invite a lawyer of the user's choice, by e-mail, to review the contract in Dealroom's attorney review. Available to any lawyer the user invites. The lawyer works for the user and bills the user directly; Dealroom takes no fee and makes no recommendation. Signing waits until the lawyer approves or the user cancels the review in Dealroom. Free (no credit).

NameTypeReqDescription
dealIdstringyesAgent deal id (dealId from generate_contract)
emailstringyesThe lawyer's e-mail address
langstring–Language of the e-mail; left out, the contract's language
namestring–The lawyer's name, for the e-mail greeting

No output schema declared.

No examples provided.

Install

How do I install the Dealroom MCP server?

Dealroom is a hosted endpoint at https://dealroom.todo.law/api/v1/agent/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 · dealroom.todo.law

# add to Claude Code
claude mcp add --transport http sergiomaldo-dealroom 'https://dealroom.todo.law/api/v1/agent/mcp'
Common questions

What is the Dealroom MCP server?

Dealroom is an MCP server listed in the public MCP registry as io.github.sergiomaldo/dealroom. Make a contract in one call, or negotiate it clause by clause with a published compromise formula. This page covers its hosted endpoint (https://dealroom.todo.law/api/v1/agent/mcp).

Is the Dealroom MCP server safe to use?

Dealroom scores 73 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 Dealroom MCP server expose?

Dealroom exposes 18 tools: list_contract_types, generate_contract, list_templates, get_template, create_playbook, and 13 more. Their descriptions and schemas cost roughly 2,308 tokens of context every time the server is loaded.

Does the Dealroom MCP server require authentication?

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

Is the Dealroom MCP server still maintained?

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