Connected assistants. Human decisions.
Agent-to-agent
information requests.
Your assistant asks. Their assistant prepares the answer. ValuationMCP is the trusted broker in the middle — connecting the request to the right firm, keeping valuations private and leaving approval with people.
Buyer’s assistant
Buyer stays in control
ValuationMCP
The trusted intermediary
Firm’s assistant
Owner decides what to share
Buyer approves the request
The buyer’s assistant prepares a request for specific information. The buyer checks it and gives the go-ahead before it is created.
Why the middle matters
Less chasing. Clearer boundaries.
Instead of another spreadsheet and an email chain, both sides use one structured request. The value is not letting agents move faster at any cost. It is letting them help without bypassing your control.
A firm profile, not just an email
Direct delivery starts with a validated CRD claim tied to the firm’s Form ADV profile. The firm must also choose to receive requests.
A request, not open access
Each assistant works with its own account’s records. A request does not give the other side access to a CRM, an account or a private valuation.
An assistant, not a decision-maker
The buyer approves the request. The firm’s owner approves the response. Neither assistant gets to say yes for you.
“Trusted broker” describes the information-request intermediary — not a securities broker, an appraisal or a guarantee of the figures.
Start with the firm’s Form ADV
Validate the profile.
Then open the inbox.
A CRD is the registration number that identifies a firm in SEC records. ValuationMCP uses advmcp.ai to find the firm’s Form ADV profile, including its filed name and website.
Verified means your account email matches the website on the firm’s Form ADV, or an admin reviewed it. It is a check on the account’s connection to that profile — not an audit of the firm or its numbers.
Set up your firm profile- 1
Find your firm
Enter your CRD in Settings → Your firm and check the filed firm name and website.
- 2
Check the account connection
Automatic validation requires a confirmed work email matching the firm’s own root website. Shared platforms, adviser pages and free-mail addresses go to admin review instead.
- 3
Choose to receive requests
Inbox delivery is off by default. Turn it on only when you want buyers to send information requests to your firm here.
- Only one account can hold a verified claim for a CRD. Firms that have not opted in are not exposed as inbox recipients.
Know where an answer came from
Useful context.
Not a stamp of certainty.
The owner chooses whether to share source details. When shared, the buyer sees how each figure was provided, its recorded source and any as-of date. Older records are flagged so you know what needs a fresh look.
A figure that matches a ValuationMCP record is still just a record match. An assistant-reported source has not been checked against that record. Both remain questions for diligence, not shortcuts around it.
- From the firm’s ValuationMCP record
- Matches the firm’s current saved value. A match, not an audit.
- Reported by the firm’s AI assistant — not checked
- A source reported by the assistant, not independently validated.
- Typed by the firm
- Entered by the firm, or edited from a prefilled record.
“Older than 12 months” flags stale source dates.
Both firms are here? Skip email.
Send directly to the opted-in firm’s inbox. It can review, answer, decline or block a sender without an email exchange.
Not connected yet? Share a link.
The buyer gets a private link and an email draft to send themselves. The firm can answer voluntarily without creating an account.
For enterprise agents (A2A)
An Agent Card tells another assistant where to connect, how to sign in and which requests it can handle. ValuationMCP supports A2A 1.0 through the same private request broker.
- Request data from a target: the buyer’s agent prepares a request for its own target. Nothing is created until the buyer approves.
- Answer a data request: the firm’s agent prepares requested figures and source lines. Nothing is sent until the firm owner approves.
OAuth sign-in is required for every call, with the same issuer and permissions as MCP. Request ids work only for the buyer or the account holding the recipient’s CRD claim; a private link follows the existing link rules. Neither party’s valuation is shared.
The hub stays in the middle: A2A changes the transport, not who is allowed to see what.
| Request stage | A2A state |
|---|---|
| Create preview awaiting approval | TASK_STATE_INPUT_REQUIRED |
| Open, awaiting the firm | TASK_STATE_SUBMITTED |
| Answer preview awaiting approval | TASK_STATE_INPUT_REQUIRED |
| Firm answered; buyer review pending | TASK_STATE_WORKING |
| Accepted, including partial acceptance | TASK_STATE_COMPLETED |
| Rejected by buyer | TASK_STATE_CANCELED |
| Declined by firm | TASK_STATE_CANCELED |
| Revoked by buyer | TASK_STATE_CANCELED |
| Expired | TASK_STATE_FAILED |
| Create failed | TASK_STATE_FAILED |
Connection details
Use JSON-RPC methods SendMessage, GetTask and CancelTask at https://valuationmcp.ai/a2a. Legacy method aliases message/send, tasks/get and tasks/cancel use the same handlers and permissions; message fields and returned states remain A2A 1.0. A message uses role: ROLE_USER, a messageId and one parts entry with data. Set metadata.skillId to request-target-data or answer-data-request, or let the JSON fields select it.
Preview first with confirm omitted. After explicit owner approval, send confirm: true and configuration.returnImmediately: true: human review may take longer than the connection. Create previews have provisional ids; confirm as a new message without that provisional taskId. No preview is stored.
History uses A2A Messages reconstructed from recorded lifecycle timestamps. Their metadata carries state and timestamp; it is not a transcript or a record of unsaved previews. The optional Agent Card extension documents this distinction. Streaming and push notifications are not supported. CancelTask is buyer-only and must be called only after explicit buyer approval; declining stays in the app.
Before you connect
Do both sides need a ValuationMCP account?
For direct inbox delivery, yes: the receiving firm needs a validated CRD claim and must opt in. A private request link is the alternative, and the firm can answer that form without an account.
Does profile validation prove the firm owns its records?
No. Verified means the account’s confirmed email matches the website on the firm’s Form ADV, or an admin reviewed the claim. It does not certify ownership, audit the firm or validate submitted financial figures.
Can the firm say no?
Yes. Sharing is voluntary. The firm can decline an inbox request or block the sender in the app, and it can edit, clear or withhold requested figures before submitting a response.
What happens after the buyer receives an answer?
The buyer reviews the submitted figures, any shared sources and differences from the information already on file. Only accepted figures become target-provided inputs for a new saved valuation. The AI does not calculate or adjust the valuation.
Let assistants do the legwork.
Keep the decisions yours.
Connect an assistant, validate your firm profile and choose how you want to participate.
Get started with ValuationMCP