First
REMOTE · MCP.THISFIRST.COM
Get a prenup with First: ask prenup questions, set up your account, and add assets.
Available components
Last scanned (23 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Documents and Files
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 Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7286 tokens (~208/item across 35 items; 35 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 36 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 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.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 +41
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Tool coverage: 92 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- 9 Nov 26 37
First indexed and scored.
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 21 Nov 2026 · Probed https://mcp.thisfirst.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.thisfirst.com | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 3b05ae14d57fce1d0e3503549b3ea2f0 |
| SANs: mcp.thisfirst.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.thisfirst.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| thisfirst.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer scope="agreement:read agreement:write", resource_metadata="https://mcp.thisfirst.com/.well-known/oauth-protected-resource/mcp"
Bearer scope="agreement:read agreement:write", resource_metadata="https://mcp.thisfirst.com/.well-known/oauth-protected-resource/mcp" | Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://mcp.thisfirst.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.thisfirst.com/mcp |
| Authorisation server | https://api.stytch.thisfirst.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.thisfirst.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.thisfirst.com/mcp | HTTPS enforced | 301 | https://mcp.thisfirst.com/mcp |
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 →
add_asset Add an asset or a debt ~373
Adds an asset or a debt to the customer's My Assets page. Call describe_asset_form for the fields and the module_state first. Confirm the values with the customer before you call this tool. When module_state is edit_restarts_alignment, also tell the customer that the change restarts the alignment of the couple and can email the partner, and get a yes. After an asset, family, or allocation write, tell the customer that the alignment restarted when alignment_restarted is true. Tell the customer that the partner got an email when partner_emailed is true. When a value is false, say nothing about it. When the customer asks about these values, answer from the results of all the writes in this conversation. For a bank account, a credit card, an investment, or a debt, when describe_asset_form gives plaid_connection_url (for example /prenup/my-assets/bank), offer two choices: the customer connects the account through Plaid in the app, or gives the account here for this tool. A Plaid connection in the app also restarts the alignment when module_state is edit_restarts_alignment, so get the same yes first. Never ask for the sign-in details of an account. Send the module_state that you read as expected_module_state, also when it is open.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_module_state | string | – | The module_state that you read from the list or describe tool of this module, also when it is open. When the state is now different, the tool saves nothing and gives the new state. |
| fields | object | yes | The values of the form, by the field keys of the describe tool. Give each currency amount in US dollars, with up to 2 decimals. The amount of a debt is positive. |
| kind | string | yes | The kind of asset or debt. |
| Name | Type | Req | Description |
|---|---|---|---|
| alignment_restarted | boolean | yes | True when the write restarted the alignment of the couple. |
| app_url | string | yes | – |
| asset | object | yes | – |
| partner_emailed | boolean | yes | True when the partner got an email that the alignment restarted. |
| status | string | yes | – |
No examples provided.
add_family_member Add a family member ~272
Adds a dependent or a pet to the customer's My Family page. Call describe_family_form for the fields and the module_state first. Confirm the values with the customer before you call this tool. When module_state is edit_restarts_alignment, also tell the customer that the change restarts the alignment of the couple and can email the partner, and get a yes. After an asset, family, or allocation write, tell the customer that the alignment restarted when alignment_restarted is true. Tell the customer that the partner got an email when partner_emailed is true. When a value is false, say nothing about it. When the customer asks about these values, answer from the results of all the writes in this conversation. Send the module_state that you read as expected_module_state, also when it is open.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_module_state | string | – | The module_state that you read from the list or describe tool of this module, also when it is open. When the state is now different, the tool saves nothing and gives the new state. |
| fields | object | yes | The values of the form, by the field keys of the describe tool. Give each currency amount in US dollars, with up to 2 decimals. The amount of a debt is positive. |
| kind | string | yes | dependent or pet. |
| Name | Type | Req | Description |
|---|---|---|---|
| alignment_restarted | boolean | yes | True when the write restarted the alignment of the couple. |
| app_url | string | yes | – |
| family_member | object | yes | – |
| partner_emailed | boolean | yes | True when the partner got an email that the alignment restarted. |
| status | string | yes | – |
No examples provided.
answer_quiz_question Answer the current quiz question ~276
Saves the answer of the customer to the current question of a quiz module, and returns the next question. Confirm the answer with the customer before you call this tool. Give the answer in the format that answer_format of the question names. A changed answer can remove the answers of questions that it hides, and it can restart the alignment of the couple. For the last screen of the quiz, give only the question_id: this finishes the module. The eligibility quiz finishes after its last question, and the result gives the next step and app_url. A result with status ineligible gives the reason and app_url: give both to the customer.
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | – | – |
| module_slug | string | yes | The slug of the quiz module, for example basic-information or financial-philosophy. Use eligibility, with product, for the eligibility questions before payment. |
| option_ids | array | – | The selected option ids. |
| other_text | string | – | The text of the customer for the option Other. |
| pets | array | – | – |
| product | string | – | The product line. Send it for the eligibility questions, and when the customer has more than one paid agreement. |
| question_id | string | yes | The question_id of the current question. |
| value | string|number | – | The value of an input question. |
| Name | Type | Req | Description |
|---|---|---|---|
| allocation_kind | string | – | – |
| answer_format | string | – | – |
| app_url | string | yes | – |
| body | string | – | – |
| educational_copy | object | – | – |
| field_label | string | – | – |
| items | array | – | The items of an allocation question. picked is false until the customer picks. |
| kind | string | – | – |
| module_slug | string | yes | – |
| module_state | string | – | The state of the module for a write of the customer. open: a write saves. edit_restarts_alignment: a write saves, restarts the alignment of the couple, and can email the partner. Tell the customer th… |
| next_step | string | – | – |
| next_step_url | string | – | Only for a closed module: the app page that shows the next step. |
| notes | array | – | – |
| options | array | – | – |
| pets | array | – | – |
| progress | integer | – | – |
| question_id | string | – | – |
| saved_answer | object | – | – |
| status | string | yes | – |
| subtitle | string | – | – |
| title | string | – | – |
| waiting_for_partner | string | – | – |
No examples provided.
ask_clara Ask Clara ~195
Asks Clara, the First assistant, a question for the customer. Use it for a general question about prenups (prenuptial agreements), for example "Do I need a prenup?" or "What can a prenup cover?", and for a question about First. Clara knows the First app and the general legal points of a prenup. When the customer is signed in, Clara also knows the customer's account. Send only the customer's question. Send the thread_id of an earlier answer to continue that conversation. Before sign-in, the result has notice, terms_url, and privacy_url: show the notice to the customer with the first answer, with both links.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | – | The product line that the question is about. Leave it out for a general question. |
| question | string | yes | The customer's question. |
| thread_id | string | – | The thread_id of an earlier ask_clara answer. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | – |
| notice | string | – | – |
| privacy_url | string | – | – |
| terms_url | string | – | – |
| thread_id | string | yes | – |
No examples provided.
complete_alignment Complete alignment ~175
Completes alignment, as the Complete Alignment button of the app does. Call it only when get_alignment gives ready_to_complete true, and the customer says to complete alignment. When get_alignment gives complete_statement, show this exact statement first, and get an explicit yes: "Once you complete alignment, any further changes to your prenup will need to be done by a lawyer. Are you sure you want to continue?" Then call with confirm true. When both partners completed alignment, the app makes the draft prenup. The completion emails the customer and the partner. Give the customer next_step or waiting_for_partner. When the result gives upgrade, offer the upgrade to Lawyer Review with its text and url.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | True only after the customer said yes to complete alignment, and to complete_statement when get_alignment gives it. |
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | yes | The dashboard of the app. |
| completed_now | boolean | yes | False when alignment was already complete. The tool then changed nothing. |
| next_step | string | – | The current module of the customer. |
| status | string | yes | – |
| upgrade | object | – | Only for a prenup that can upgrade to Lawyer Review: the offer of the app. |
| waiting_for_partner | string | – | Why the next module waits for the partner. |
No examples provided.
complete_alignment_step Complete an alignment step ~174
Completes one step of alignment, as the Complete Review button of its page does. Each step has the condition of its page: financial-views needs each question aligned. For partners-premarital-property, first show the customer each premarital asset of the partner (get_alignment with this step), and get a yes that the customer reviewed them. partners-postmarital-property needs a review of each item of the partner. postmarital-property needs no disagreement of the partner: the customer picks such an item again with set_allocation, and the partner reviews it again. The completion can open the next step and email the customer and the partner. Give the customer next_step, or waiting_for_partner.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | True only after the customer said to complete the step. |
| step | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | yes | – |
| completed_now | boolean | yes | False when the step was already complete. The tool then changed nothing. |
| next_step | string | – | The current module of the customer. |
| ready_to_complete | boolean | yes | Each step is complete for both partners: call complete_alignment. |
| status | string | yes | – |
| waiting_for_partner | string | – | Why the next step waits for the partner. |
No examples provided.
complete_my_assets Complete My Assets ~198
Completes the My Assets module, as the Complete button of the app does. Call it only when the customer says that the assets and the debts are complete. First call list_assets, and show the customer the full list of assets and debts. Then show this exact statement, and get an explicit yes: "I understand that full financial disclosure is key to the enforceability of my prenup and that it is my responsibility to share a complete version of my assets and liabilities." Then call with confirm true. The completion can open the next module and email the customer and the partner. Give the customer next_step.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | True only after the customer said yes to the statement of the description. |
| expected_module_state | string | – | The module_state that you read from the list or describe tool of this module, also when it is open. When the state is now different, the tool saves nothing and gives the new state. |
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | yes | The dashboard of the app. |
| completed_now | boolean | yes | False when the module was already complete. The tool then changed nothing. |
| next_step | string | – | The current module of the customer. |
| status | string | yes | – |
| waiting_for_partner | string | – | Why the next module waits for the partner. |
No examples provided.
complete_my_family Complete My Family ~169
Completes the My Family module, as the Complete button of the app does. Call it only when the customer says that the list of family members is complete. First call list_family_members, and show the customer the full list of family members. Then show this exact statement, and get an explicit yes: "I have shared a complete version of my family members." Then call with confirm true. The completion can open the next module. Give the customer next_step.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | True only after the customer said yes to the statement of the description. |
| expected_module_state | string | – | The module_state that you read from the list or describe tool of this module, also when it is open. When the state is now different, the tool saves nothing and gives the new state. |
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | yes | The dashboard of the app. |
| completed_now | boolean | yes | False when the module was already complete. The tool then changed nothing. |
| next_step | string | – | The current module of the customer. |
| status | string | yes | – |
| waiting_for_partner | string | – | Why the next module waits for the partner. |
No examples provided.
delete_asset Delete an asset or a debt ~239
Deletes one of the customer's own assets or debts. Take the id and the module_state from list_assets. Confirm the delete with the customer before you call this tool: the asset cannot be restored. When module_state is edit_restarts_alignment, also tell the customer that the delete restarts the alignment of the couple and can email the partner, and get a yes. After an asset, family, or allocation write, tell the customer that the alignment restarted when alignment_restarted is true. Tell the customer that the partner got an email when partner_emailed is true. When a value is false, say nothing about it. When the customer asks about these values, answer from the results of all the writes in this conversation. Send the module_state that you read as expected_module_state, also when it is open.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_module_state | string | – | The module_state that you read from the list or describe tool of this module, also when it is open. When the state is now different, the tool saves nothing and gives the new state. |
| id | string | yes | The id from the list tool. Only an own row of the customer. |
| Name | Type | Req | Description |
|---|---|---|---|
| alignment_restarted | boolean | yes | True when the write restarted the alignment of the couple. |
| app_url | string | yes | – |
| id | string | yes | – |
| partner_emailed | boolean | yes | True when the partner got an email that the alignment restarted. |
| status | string | yes | – |
No examples provided.
delete_family_member Delete a family member ~243
Deletes one of the customer's own dependents or pets. Take the id and the module_state from list_family_members. Confirm the delete with the customer before you call this tool: the family member cannot be restored. When module_state is edit_restarts_alignment, also tell the customer that the delete restarts the alignment of the couple and can email the partner, and get a yes. After an asset, family, or allocation write, tell the customer that the alignment restarted when alignment_restarted is true. Tell the customer that the partner got an email when partner_emailed is true. When a value is false, say nothing about it. When the customer asks about these values, answer from the results of all the writes in this conversation. Send the module_state that you read as expected_module_state, also when it is open.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_module_state | string | – | The module_state that you read from the list or describe tool of this module, also when it is open. When the state is now different, the tool saves nothing and gives the new state. |
| id | string | yes | The id from the list tool. Only an own row of the customer. |
| Name | Type | Req | Description |
|---|---|---|---|
| alignment_restarted | boolean | yes | True when the write restarted the alignment of the couple. |
| app_url | string | yes | – |
| id | string | yes | – |
| partner_emailed | boolean | yes | True when the partner got an email that the alignment restarted. |
| status | string | yes | – |
No examples provided.
describe_asset_form Describe an asset form ~191
Returns the form of one kind of asset or debt on the My Assets page: the field keys, the labels, the options, the required fields, and the module_state. Call it before add_asset or update_asset. When module_state is closed, do not collect values: give the customer next_step_url. Otherwise ask the customer for each required value. For a bank account, a credit card, an investment, or a debt, when the result gives plaid_connection_url (for example /prenup/my-assets/bank), offer two choices: the customer connects the account through Plaid in the app, or gives the account here for add_asset. A Plaid connection in the app also restarts the alignment when module_state is edit_restarts_alignment, so get the same yes first. Never ask for the sign-in details of an account.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | The kind of asset or debt. |
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | yes | – |
| kind | string | yes | – |
| module_state | string | yes | The state of the module for a write of the customer. open: a write saves. edit_restarts_alignment: a write saves, restarts the alignment of the couple, and can email the partner. Tell the customer th… |
| next_step_url | string | – | Only for a closed module: the app page that shows the next step. |
| notes | string | yes | – |
| plaid_connection_url | string | – | Only for a bank, a credit card, an investment, or a debt when the module is not closed: the app page that connects the account through Plaid. It needs a computer: the app does not show My Assets on a… |
| title | string | yes | – |
No examples provided.
describe_family_form Describe a family member form ~91
Returns the form of a dependent or a pet on the My Family page: the field keys, the labels, the options, the required fields, and the module_state. Call it before add_family_member or update_family_member. When module_state is closed, do not collect values: give the customer next_step_url. Otherwise ask the customer for each required value.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | dependent or pet. |
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | yes | – |
| kind | string | yes | – |
| module_state | string | yes | The state of the module for a write of the customer. open: a write saves. edit_restarts_alignment: a write saves, restarts the alignment of the couple, and can email the partner. Tell the customer th… |
| next_step_url | string | – | Only for a closed module: the app page that shows the next step. |
| notes | string | yes | – |
| plaid_connection_url | string | – | Only for a bank, a credit card, an investment, or a debt when the module is not closed: the app page that connects the account through Plaid. It needs a computer: the app does not show My Assets on a… |
| title | string | yes | – |
No examples provided.
finish_welcome_steps Finish the welcome steps ~230
Finishes the welcome steps of a paid product, as the dashboard of the First app does. It saves the acceptance of the statements of welcome.confirm from get_started, and the optional phone. Call it only at the onboarding stage. First show each statement, and get an explicit yes to each one from the customer. Then invite the partner with invite_partner when the next step of get_started asks for it. Returns the next setup step, as get_started does.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_terms | boolean | yes | True only after the customer said yes to the statement about the Terms of Service and the Privacy Policy. |
| acknowledge_signing | boolean | – | The prenup and the postnup only. True only after the customer said yes to the statement about the signature. |
| phone | string | – | The customer's US phone number, for texts about the service. |
| product | string | yes | The product line of the welcome steps. |
| skip_phone | boolean | – | True when the customer declines to give a phone. The app then does not ask again. Leave out phone and skip_phone when you did not ask. |
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | – | – |
| can_do | string | yes | – |
| choices | array | – | – |
| current_step | string | – | – |
| first_name | string | – | – |
| next_step | string | yes | – |
| product | string | – | – |
| products | array | – | – |
| stage | string | yes | – |
| status | string | – | – |
| waiting_for_partner | string | – | – |
| waiting_period_days_left | integer | – | – |
| welcome | object | – | – |
No examples provided.
get_agreement_status Get agreement status ~117
Returns where the customer is in their First agreement: the status, the waiting period when there is one, the current step in the app, and a link to the app. Before the account setup is done, it returns the setup stage and the next step, as get_started does. Do not use it for questions about how First or the law works.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | – | The product that the customer chose, or the product line of the agreement. Send it in each call until the customer has an agreement of this product. |
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | – | – |
| can_do | string | – | – |
| current_step | string | – | – |
| first_name | string | – | – |
| next_step | string | – | – |
| product | string | – | – |
| products | array | – | – |
| stage | string | – | – |
| status | string | – | – |
| waiting_for_partner | string | – | – |
| waiting_period_days_left | integer | – | – |
| welcome | object | – | – |
No examples provided.
get_alignment Get the alignment of the couple ~286
Returns the alignment steps of the prenup with the status of the customer and of the partner, the current step, and the data of a step as its app page shows it. The steps go in this order: financial-views (the customer agrees with the partner on each financial view), partners-premarital-property (the customer reads the premarital property of the partner), partners-postmarital-property (the customer agrees or disagrees with each postmarital allocation of the partner), and postmarital-property (the customer sees the review of the partner, and picks again where the partner disagrees). Give step to read a different step, or premarital-property or shared-property for the own premarital assets and the shared assets. Each asset and item gives its allocation in separate_property, as the page shows it. When ready_to_complete is true, the customer can complete alignment with complete_alignment. changed_after_completion names the sections that a partner changed after their completion. Tell the customer about them before a write of financial-views: the write clears the list, as the page does when it opens. Show the data to the customer before each write of the step. A question with in_app true changes only in the app: give the customer its app_url.
| Name | Type | Req | Description |
|---|---|---|---|
| step | string | – | The step or the page to read. Leave it out for the current step. |
| Name | Type | Req | Description |
|---|---|---|---|
| allocation_labels | object | yes | The words of the app for separate_property true and false. |
| app_url | string | yes | – |
| changed_after_completion | object | – | The titles of the sections that the customer or the partner changed after their completion. The title of a partner section speaks to the partner. |
| complete_statement | string | – | Only when ready_to_complete is true, for Lawyer Review: show it before complete_alignment, and get an explicit yes. |
| current_step | string | – | The first step that the customer can do now. |
| data | object | – | The data of shown_step, as its app page shows it. |
| ready_to_complete | boolean | yes | Each step is complete for both partners. |
| shown_step | string | – | The step or the page of data. |
| steps | array | yes | – |
| waiting_for_partner | string | – | Why the customer waits for the partner. |
No examples provided.
get_my_details Get the customer's details ~99
Returns the customer's First account details: the legal name, the email, the phone, the partner or the partner invite, and the purchases. Use it when the customer asks about these details. Do not use the email of the AI app account. To change the name, call update_profile. To change the phone, call update_phone. To change a pending partner invite, call update_partner_invite. To change the email, call request_email_change.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | yes | – |
| string | yes | – | |
| first_name | string | – | – |
| last_name | string | – | – |
| partner | object | – | – |
| pending_email | string | – | A new email that the customer did not verify yet. |
| phone | string | – | – |
| purchases | array | yes | – |
| requested_email | string | – | A new email of request_email_change that the current email did not approve yet. |
No examples provided.
get_quiz_question Get the current quiz question ~237
Returns the current question of a quiz module of the customer: the text, the options with their ids, the format of the answer, the saved answer, and the progress. Ask the customer the question, then call answer_quiz_question. The result can include notes: the text of the information screens before the question. Give the notes to the customer. This tool saves no answer, but it moves the quiz past the information screens. A result with status allocation gives items that the customer picks one by one with set_allocation. A result with status in_app is a question that the customer answers in the app, at app_url. A result with status complete means that the module is finished. For the eligibility quiz, give the customer next_step and app_url of a result with status complete or ineligible.
| Name | Type | Req | Description |
|---|---|---|---|
| module_slug | string | yes | The slug of the quiz module, for example basic-information or financial-philosophy. Use eligibility, with product, for the eligibility questions before payment. |
| product | string | – | The product line. Send it for the eligibility questions, and when the customer has more than one paid agreement. |
| Name | Type | Req | Description |
|---|---|---|---|
| allocation_kind | string | – | – |
| answer_format | string | – | – |
| app_url | string | yes | – |
| body | string | – | – |
| educational_copy | object | – | – |
| field_label | string | – | – |
| items | array | – | The items of an allocation question. picked is false until the customer picks. |
| kind | string | – | – |
| module_slug | string | yes | – |
| module_state | string | – | The state of the module for a write of the customer. open: a write saves. edit_restarts_alignment: a write saves, restarts the alignment of the couple, and can email the partner. Tell the customer th… |
| next_step | string | – | – |
| next_step_url | string | – | Only for a closed module: the app page that shows the next step. |
| notes | array | – | – |
| options | array | – | – |
| pets | array | – | – |
| progress | integer | – | – |
| question_id | string | – | – |
| saved_answer | object | – | – |
| status | string | yes | – |
| subtitle | string | – | – |
| title | string | – | – |
| waiting_for_partner | string | – | – |
No examples provided.
get_started Get started ~229
Returns the customer's first name, the setup stage of their First account, and the one next step. It also says what the assistant can do now. After the setup, it gives the status of the agreement. At the onboarding stage, it gives the welcome steps to do in the chat. Call it at the first message of a conversation, also when that message is only a greeting. Greet the customer by first name. Before the setup is done, it gives choices. When the message of the customer is only a greeting, offer the choices of get_started one time in the conversation and wait for the answer, or give the next step when there are no choices. When the message is not only a greeting, answer it, and give the next step when the customer asks what to do. A customer with no agreement gets the products to choose from: ask the customer to start one, or to only ask Clara questions.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | – | The product that the customer chose, or the product line of the agreement. Send it in each call until the customer has an agreement of this product. |
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | – | – |
| can_do | string | yes | – |
| choices | array | – | – |
| current_step | string | – | – |
| first_name | string | – | – |
| next_step | string | yes | – |
| product | string | – | – |
| products | array | – | – |
| stage | string | yes | – |
| status | string | – | – |
| waiting_for_partner | string | – | – |
| waiting_period_days_left | integer | – | – |
| welcome | object | – | – |
No examples provided.
invite_partner Invite the customer's partner ~108
Sends an invite email from First to the customer's partner, so the partner can join the agreement. Confirm the partner's name and email with the customer before you call this tool. When an invite is already pending, call resend_partner_invite to send it again, or update_partner_invite to change the email.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The partner's email address. | |
| first_name | string | yes | The partner's first name. |
| last_name | string | yes | The partner's last name. |
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | yes | – |
| next_step | string | yes | – |
| status | string | yes | – |
No examples provided.
list_assets List assets ~92
Returns the assets and debts on the customer's My Assets page, with their ids: the customer's own assets and the assets that the partner shares. Use it for the exact list or an id. Call ask_clara for questions about what the assets mean for the prenup. module_state tells if a write saves, restarts the alignment, or gets a refusal. When it is closed, give the customer next_step_url.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | yes | – |
| assets | array | yes | – |
| module_state | string | yes | The state of the module for a write of the customer. open: a write saves. edit_restarts_alignment: a write saves, restarts the alignment of the couple, and can email the partner. Tell the customer th… |
| next_step_url | string | – | Only for a closed module: the app page that shows the next step. |
No examples provided.
list_documents List documents ~103
Lists the customer's own documents, for example the prenup summary and the waivers: the kind, the title, whether the customer agreed, the date of the signature, and a link to the app. Some documents are only in the app. Call read_document with the kind for the text. The customer agrees to and signs a document only in the app.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | – | The product line of the agreement. Leave it out when only one agreement is paid. |
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | yes | – |
| documents | array | yes | – |
No examples provided.
list_family_members List family members ~96
Returns the dependents and pets on the customer's My Family page, with their ids: the customer's own family members and the members that the partner shares. Use it for the exact list or an id. Call ask_clara for questions about what the family members mean for the prenup. module_state tells if a write saves, restarts the alignment, or gets a refusal. When it is closed, give the customer next_step_url.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | yes | – |
| family_members | array | yes | – |
| module_state | string | yes | The state of the module for a write of the customer. open: a write saves. edit_restarts_alignment: a write saves, restarts the alignment of the couple, and can email the partner. Tell the customer th… |
| next_step_url | string | – | Only for a closed module: the app page that shows the next step. |
No examples provided.
previous_quiz_question Go back one quiz question ~124
Moves a quiz module back one question, as the Back button of the app does, and returns that question. It saves no answer, and it changes only the position in the quiz. Use it when the customer wants to change an earlier answer.
| Name | Type | Req | Description |
|---|---|---|---|
| module_slug | string | yes | The slug of the quiz module, for example basic-information or financial-philosophy. Use eligibility, with product, for the eligibility questions before payment. |
| product | string | – | The product line. Send it for the eligibility questions, and when the customer has more than one paid agreement. |
| Name | Type | Req | Description |
|---|---|---|---|
| allocation_kind | string | – | – |
| answer_format | string | – | – |
| app_url | string | yes | – |
| body | string | – | – |
| educational_copy | object | – | – |
| field_label | string | – | – |
| items | array | – | The items of an allocation question. picked is false until the customer picks. |
| kind | string | – | – |
| module_slug | string | yes | – |
| module_state | string | – | The state of the module for a write of the customer. open: a write saves. edit_restarts_alignment: a write saves, restarts the alignment of the couple, and can email the partner. Tell the customer th… |
| next_step | string | – | – |
| next_step_url | string | – | Only for a closed module: the app page that shows the next step. |
| notes | array | – | – |
| options | array | – | – |
| pets | array | – | – |
| progress | integer | – | – |
| question_id | string | – | – |
| saved_answer | object | – | – |
| status | string | yes | – |
| subtitle | string | – | – |
| title | string | – | – |
| waiting_for_partner | string | – | – |
No examples provided.
read_agreement Read agreement ~153
Returns the text of the customer's agreement, as the agreement page of the app shows it. Send search to get only the parts around a word or phrase, for example "house". Leave search out to read the whole agreement, for example for a question about the agreement as a whole. A long agreement comes in pages: call again with the next page until page equals pages.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | The page of the whole text. The first is 1. |
| product | string | – | The product line of the agreement. Leave it out when only one agreement is paid. |
| search | string | – | A word or phrase. The result has up to 10 excerpts around the matches, not a page. |
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | yes | – |
| excerpts | array | – | Empty when nothing matches. |
| more_matches | boolean | – | The agreement has more matches. Send a narrower search, or read the pages. |
| page | integer | – | – |
| pages | integer | – | – |
| product | string | yes | – |
| text | string | – | A page of the agreement, when the call has no search. |
No examples provided.
read_document Read a document ~72
Returns the text of one of the customer's own documents, for example the prenup summary. Call list_documents for the kinds that the customer has.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | The kind from list_documents. |
| product | string | – | The product line of the agreement. Leave it out when only one agreement is paid. |
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | yes | – |
| kind | string | yes | – |
| text | string | yes | – |
| title | string | yes | – |
No examples provided.
request_email_change Ask to change the customer's email ~79
Asks to change the email that the customer uses to sign in to First. Confirm the new email with the customer before you call this tool. The tool does not change the email: the customer approves the change from the current email, and then confirms the new email from a sign-in link.
| Name | Type | Req | Description |
|---|---|---|---|
| new_email | string | yes | The new email. |
| Name | Type | Req | Description |
|---|---|---|---|
| next_step | string | yes | – |
| status | string | yes | – |
No examples provided.
resend_partner_invite Send the partner's invite again ~53
Sends the pending partner invite again, to the same email. Confirm with the customer before you call this tool. To invite a different email, call update_partner_invite. A partner who declined gets no new invite.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | yes | – |
| next_step | string | yes | – |
| status | string | yes | – |
No examples provided.
review_financial_view Review a financial view ~168
Does one action of the financial-views step of alignment on one question, as the financial views page of the app does. Call get_alignment first: each question gives its actions. acknowledge: the customer read the different answer of the partner and accepts it. Show the answer of the partner first. answer: the customer changes the own answer, in the format of answer_format. Confirm the answer with the customer first. A changed answer asks the partner to review the financial views again. When each question is aligned, complete the step with complete_alignment_step.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| option_ids | array | – | The selected option ids. |
| question_id | string | yes | The question_id from get_alignment. |
| value | string|number | – | The value of an input question. |
| Name | Type | Req | Description |
|---|---|---|---|
| aligned | boolean | yes | Each question of the financial views is aligned. |
| app_url | string | yes | – |
| question | object | – | The question after the action, as get_alignment gives it. Not given when question_hidden is true. |
| question_hidden | boolean | yes | True when the new answer hides the question from the financial views. |
| status | string | yes | – |
No examples provided.
review_partner_property Review the partner's postmarital property ~164
Saves the review of the customer of the postmarital allocations of the partner, in the partners-postmarital-property step of alignment. Call get_alignment with this step first, and show the customer each item of the partner with its allocation. agree true accepts the allocation of the partner. agree false disagrees: the partner then picks again. Give an item for each item that has no review (customer_agrees null), in one call. Give the separate_property of each item as get_alignment gave it. When an item changed after the read, the tool saves nothing: read the step again, and show the new allocation to the customer. An item that you do not give keeps its review. Then complete the step with complete_alignment_step.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | yes | – |
| partner_items | array | yes | – |
| status | string | yes | – |
No examples provided.
set_allocation Set an allocation ~346
Saves one allocation pick of the customer: keep an item as separate property after the wedding, or share it (allocation_labels of get_alignment give the words of the app). kind asset is an own premarital asset that is not shared (get_alignment step premarital-property). kind marital_property is a category of postmarital property (get_alignment step postmarital-property). After the financial philosophy quiz closed, a pick of kind marital_property needs the step postmarital-property. An allocation question of the financial philosophy quiz gives the items of both kinds. A pick of a postmarital category asks the partner to review it again. Read module_state before the pick. When it is edit_restarts_alignment, tell the customer that the pick restarts the alignment of the couple and can email the partner, and get a yes. Send the module_state that you read as expected_module_state, also when it is open. After an asset, family, or allocation write, tell the customer that the alignment restarted when alignment_restarted is true. Tell the customer that the partner got an email when partner_emailed is true. When a value is false, say nothing about it. When the customer asks about these values, answer from the results of all the writes in this conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_module_state | string | – | The module_state that you read for this kind. When the state is now different, the tool saves nothing and gives the new state. |
| id | string | yes | The id of the asset or of the postmarital category. |
| kind | string | yes | – |
| separate_property | boolean | yes | True to keep the item separate. False to share it. |
| Name | Type | Req | Description |
|---|---|---|---|
| alignment_restarted | boolean | yes | True when the write restarted the alignment of the couple. |
| app_url | string | yes | – |
| id | string | yes | – |
| kind | string | yes | – |
| name | string | yes | – |
| partner_emailed | boolean | yes | True when the partner got an email that the alignment restarted. |
| separate_property | boolean | yes | – |
| status | string | yes | – |
No examples provided.
update_asset Change an asset or a debt ~287
Changes the fields of one of the customer's own assets or debts. Take the id and the module_state from list_assets. Give only the fields that change. Confirm the change with the customer before you call this tool. When module_state is edit_restarts_alignment, also tell the customer that the change restarts the alignment of the couple and can email the partner, and get a yes. After an asset, family, or allocation write, tell the customer that the alignment restarted when alignment_restarted is true. Tell the customer that the partner got an email when partner_emailed is true. When a value is false, say nothing about it. When the customer asks about these values, answer from the results of all the writes in this conversation. Send the module_state that you read as expected_module_state, also when it is open.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_module_state | string | – | The module_state that you read from the list or describe tool of this module, also when it is open. When the state is now different, the tool saves nothing and gives the new state. |
| fields | object | yes | The values of the form, by the field keys of the describe tool. Give each currency amount in US dollars, with up to 2 decimals. The amount of a debt is positive. |
| id | string | yes | The id from the list tool. Only an own row of the customer. |
| Name | Type | Req | Description |
|---|---|---|---|
| alignment_restarted | boolean | yes | True when the write restarted the alignment of the couple. |
| app_url | string | yes | – |
| asset | object | yes | – |
| partner_emailed | boolean | yes | True when the partner got an email that the alignment restarted. |
| status | string | yes | – |
No examples provided.
update_family_member Change a family member ~290
Changes the fields of one of the customer's own dependents or pets. Take the id and the module_state from list_family_members. Give only the fields that change. Confirm the change with the customer before you call this tool. When module_state is edit_restarts_alignment, also tell the customer that the change restarts the alignment of the couple and can email the partner, and get a yes. After an asset, family, or allocation write, tell the customer that the alignment restarted when alignment_restarted is true. Tell the customer that the partner got an email when partner_emailed is true. When a value is false, say nothing about it. When the customer asks about these values, answer from the results of all the writes in this conversation. Send the module_state that you read as expected_module_state, also when it is open.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_module_state | string | – | The module_state that you read from the list or describe tool of this module, also when it is open. When the state is now different, the tool saves nothing and gives the new state. |
| fields | object | yes | The values of the form, by the field keys of the describe tool. Give each currency amount in US dollars, with up to 2 decimals. The amount of a debt is positive. |
| id | string | yes | The id from the list tool. Only an own row of the customer. |
| Name | Type | Req | Description |
|---|---|---|---|
| alignment_restarted | boolean | yes | True when the write restarted the alignment of the couple. |
| app_url | string | yes | – |
| family_member | object | yes | – |
| partner_emailed | boolean | yes | True when the partner got an email that the alignment restarted. |
| status | string | yes | – |
No examples provided.
update_partner_invite Change the partner's invite ~122
Changes the email or the name of a partner who did not join yet. A new email gets a new invite email from First. Send only the values that change. Confirm them with the customer before you call this tool. When the partner already has a First account, send a new email with both names. After the partner joins, only the partner changes these details.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The partner's new email address. | |
| first_name | string | – | The partner's first name. |
| last_name | string | – | The partner's last name. |
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | yes | – |
| next_step | string | yes | – |
| status | string | yes | – |
No examples provided.
update_phone Change the customer's phone ~96
Saves the customer's US phone number, which First uses for texts about the service. An empty phone removes it. Confirm the number with the customer before you call this tool, and tell the customer: "By providing your phone number you consent to receiving transactional texts." At the welcome steps, send the phone with finish_welcome_steps instead.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | A US phone number with 10 digits, or "" to remove it. |
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | – | – |
| status | string | yes | – |
No examples provided.
update_profile Save the customer's legal name ~118
Saves the customer's full legal name, as on their birth certificate, driver's license, or passport. The name goes into the agreement. Confirm the exact spelling with the customer before you call this tool. Returns the next setup step, as get_started does.
| Name | Type | Req | Description |
|---|---|---|---|
| first_name | string | yes | The legal first name. |
| last_name | string | yes | The legal last name. |
| product | string | – | The product that the customer chose, or the product line of the agreement. Send it in each call until the customer has an agreement of this product. |
| Name | Type | Req | Description |
|---|---|---|---|
| app_url | string | – | – |
| can_do | string | yes | – |
| choices | array | – | – |
| current_step | string | – | – |
| first_name | string | – | – |
| next_step | string | yes | – |
| product | string | – | – |
| products | array | – | – |
| stage | string | yes | – |
| status | string | – | – |
| waiting_for_partner | string | – | – |
| waiting_period_days_left | integer | – | – |
| welcome | object | – | – |
No examples provided.
How do I install the First MCP server?
First is a hosted endpoint at https://mcp.thisfirst.com/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 · mcp.thisfirst.com
claude mcp add --transport http com-thisfirst-first 'https://mcp.thisfirst.com/mcp'
What is the First MCP server?
First is an MCP server listed in the public MCP registry as com.thisfirst/first. Get a prenup with First: ask prenup questions, set up your account, and add assets. This page covers its hosted endpoint (https://mcp.thisfirst.com/mcp).
Is the First MCP server safe to use?
First scores 82 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 First MCP server expose?
First exposes 35 tools: get_started, get_my_details, update_profile, update_phone, request_email_change, and 30 more. Their descriptions and schemas cost roughly 6,265 tokens of context every time the server is loaded.
Does the First MCP server require authentication?
Yes. First asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the First MCP server still maintained?
First is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the First MCP server?
VerifyMCP ran 13 checks on First, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.