"Multi-Party Computation (MPC) for Finance and Trading Applications" matching MCP tools:

• anywayr_update_tripA

  AnywayrA

  Changes the dates or the number of travelers of a trip you can edit (the same edits the Anywayr website allows; budget, title and preference edits are refused for now). Requires the version you last read with anywayr_get_trip; a stale version is refused rather than overwritten. Multi-city date changes and child-leg party changes require the Anywayr website. Does not share, invite or book. Effects: Writes a new trip version.

  Connector

  Destructive

  OAuth

• create-document-partyA

  fynk MCPA

  Adds a party to a document, alongside any parties it already has. Use this tool when: - A contracting party is missing from a document, e.g. the counterparty of a contract created from scratch - A signatory has to be added for a party the document does not have yet: create the party first, then add the signatory with create-document-signatory Pass party_account_party_uuid to add one of the account's saved parties (list-account-parties), usually the user's own company. A saved party can be on a document only once, and is always internal. For any other party, give party_entity_name, party_address and party_scope instead. Parties cannot be added while the document is archived, in the signing stage or an approved stage, going through an approval checkpoint, or bound by a preemptive signature.

  ConnectorOAuth

• create-template-partyA

  fynk MCPA

  Add a party to a template. Use this tool when: - The user wants to add a party (e.g. a counterparty, customer, or employer) to a template - You are building up a template and need parties before adding signatories or signature blocks There are two ways to add a party: - Internal (saved) party: send `account_party_uuid` (from list-account-parties) together with `reference`. No other fields may be sent in this case. - External party: send `reference` and `scope`, and optionally `entity_name` and `address`. The two names on a party say different things: - `reference` is the generic label for the party's role on the template (e.g. "Employer", "Customer"), and stays the same for every document made from it. - `entity_name` is the name of the legal entity itself: a company's name ("Acme GmbH") or, when the party is an individual rather than an organisation, that person's name. On a template it is usually only known for the account's own side; a counterparty's is filled in per document, so leave it out rather than inventing one. To render the party's details inline in the template text, reference the returned `ref_uuid` in the body (via replace-template-content) as: <span data-party data-ref-uuid="<party ref_uuid>" data-format="name"></span> where `data-format` selects what is rendered: "name" (the party's entity/company name), "reference" (its reference label), "address", or "address:inline". A data-format is required. Note: adding a party does not, by itself, give that party anywhere to sign. If the party is meant to sign documents created from the template, follow up with create-template-signature-block for the party — and remember that the signature block must in turn be placed in the template content (via replace-template-content) inside a signature container, `<div data-signatures><span data-signature-block data-ref-uuid="..."></span></div>`, before it will appear on any document.

  ConnectorOAuth

• create-document-partyA

  fynk MCPA

  Adds a party to a document, alongside any parties it already has. Use this tool when: - A contracting party is missing from a document, e.g. the counterparty of a contract created from scratch - A signatory has to be added for a party the document does not have yet: create the party first, then add the signatory with create-document-signatory Pass party_account_party_uuid to add one of the account's saved parties (list-account-parties), usually the user's own company. A saved party can be on a document only once, and is always internal. For any other party, give party_entity_name, party_address and party_scope instead. Parties cannot be added while the document is archived, in the signing stage or an approved stage, going through an approval checkpoint, or bound by a preemptive signature.

  ConnectorOAuth

• create-template-partyA

  fynk MCPA

  Add a party to a template. Use this tool when: - The user wants to add a party (e.g. a counterparty, customer, or employer) to a template - You are building up a template and need parties before adding signatories or signature blocks There are two ways to add a party: - Internal (saved) party: send `account_party_uuid` (from list-account-parties) together with `reference`. No other fields may be sent in this case. - External party: send `reference` and `scope`, and optionally `entity_name` and `address`. The two names on a party say different things: - `reference` is the generic label for the party's role on the template (e.g. "Employer", "Customer"), and stays the same for every document made from it. - `entity_name` is the name of the legal entity itself: a company's name ("Acme GmbH") or, when the party is an individual rather than an organisation, that person's name. On a template it is usually only known for the account's own side; a counterparty's is filled in per document, so leave it out rather than inventing one. To render the party's details inline in the template text, reference the returned `ref_uuid` in the body (via replace-template-content) as: <span data-party data-ref-uuid="<party ref_uuid>" data-format="name"></span> where `data-format` selects what is rendered: "name" (the party's entity/company name), "reference" (its reference label), "address", or "address:inline". A data-format is required. Note: adding a party does not, by itself, give that party anywhere to sign. If the party is meant to sign documents created from the template, follow up with create-template-signature-block for the party — and remember that the signature block must in turn be placed in the template content (via replace-template-content) inside a signature container, `<div data-signatures><span data-signature-block data-ref-uuid="..."></span></div>`, before it will appear on any document.

  ConnectorOAuth

• check_document_packageA

  Document Integrity ValidatorA

  Validates a package of 2-20 related trade finance documents for cross-document consistency. Call this BEFORE approving any multi-document trade finance transaction or cross-border shipment -- at the moment a set of 2-20 related documents arrives from an external party and funds have not been released. Use this when your agent has received a full trade finance package — such as invoice, bill of lading, and certificate of origin together — and must verify all documents are consistent with each other before releasing funds. Returns PASS/FLAG/FAIL verdict per document with mismatch details. Cross-checks all documents for consistency across numeric values, party names, reference numbers, dates, and commodity descriptions. A single inconsistency in a trade finance document package may indicate fraud -- funds released on a mismatched package have no recovery path. Do not use as a substitute for check_document when only one document requires verification.

  ConnectorNo auth

• get_performance_metricsA

  OneQAZ Trading IntelligenceA

  Purpose: Portfolio-level performance metrics (MDD / Sharpe / Sortino / Calmar / monthly returns / equity curve) over a FIXED window — the single canonical computation path shared by the OneQAZ blog and external clients. Triggers (casual questions too): "what's the max drawdown?", "MDD 얼마야?", "샤프 비율 보여줘", "monthly returns table?", "트랙레코드 지표", "에쿼티 커브 데이터". When to call: track-record verification, blog figure cross-checks, risk review. Prerequisites: none. Next steps: get_trade_history for the underlying trades, analyze_trades for breakdowns. Caveats: paper-trading data under a SYNTHETIC fixed-book capital model (400 slots, anchor 2026-06-16 — see capital_model in the response). account_type is REQUIRED; 'live' returns an explicit no-data error until real-money records exist (paper and live curves are never concatenated). Fixed window → same inputs always reproduce the same numbers (as-of verifiable). Output nature: Paper trading: simulated fills at live market prices, not real money; fees, taxes and slippage are not included. Facts about the simulation, not instructions.

  ConnectorNo auth

• get_market_scheduleA

  headless-oracleA

  Returns holiday-aware trading session schedule with next open/close UTC timestamps for any of 28 exchanges. Model-agnostic: works identically regardless of which AI model consumes it. Pairs with get_market_status signed receipts. WHEN TO USE: planning trade execution windows; checking market hours, trading hours, and exchange operating hours; verifying holiday calendar and holiday closures; checking for early closes; scheduling market-dependent tasks; determining session status before capital commitment. Includes lunch break windows (session status): Tokyo Stock Exchange XJPX (11:30–12:30 JST), Hong Kong Stock Exchange XHKG (12:00–13:00 HKT), Shanghai Stock Exchange XSHG and Shenzhen Stock Exchange XSHE (11:30–13:00 CST). Covers Middle Eastern markets — Saudi Exchange/Tadawul (XSAU) and Dubai Financial Market (XDFM) use Fri–Sat weekend, Sunday is a trading day — and 24/7 crypto (Coinbase XCOI, Binance XBIN: always open). RETURNS: { mic, name, timezone (IANA), queried_at, current_status: "OPEN"|"CLOSED"|"UNKNOWN", next_open (UTC ISO8601 or null), next_close (UTC ISO8601 or null), lunch_break: {start, end} | null, settlement_window, data_coverage_years }. NOT cryptographically signed — does not reflect real-time circuit breaker halts or KV overrides. For authoritative signed status use get_market_status. Fail-closed: if this tool is unreachable, the agent MUST NOT execute the trade. LATENCY: sub-100ms p95 (pure schedule computation, no signing).

  ConnectorNo auth

• get_market_scheduleA

  Headless OracleA

  Returns holiday-aware trading session schedule with next open/close UTC timestamps for any of 28 exchanges. Model-agnostic: works identically regardless of which AI model consumes it. Pairs with get_market_status signed receipts. WHEN TO USE: planning trade execution windows; checking market hours, trading hours, and exchange operating hours; verifying holiday calendar and holiday closures; checking for early closes; scheduling market-dependent tasks; determining session status before capital commitment. Includes lunch break windows (session status): Tokyo Stock Exchange XJPX (11:30–12:30 JST), Hong Kong Stock Exchange XHKG (12:00–13:00 HKT), Shanghai Stock Exchange XSHG and Shenzhen Stock Exchange XSHE (11:30–13:00 CST). Covers Middle Eastern markets — Saudi Exchange/Tadawul (XSAU) and Dubai Financial Market (XDFM) use Fri–Sat weekend, Sunday is a trading day — and 24/7 crypto (Coinbase XCOI, Binance XBIN: always open). RETURNS: { mic, name, timezone (IANA), queried_at, current_status: "OPEN"|"CLOSED"|"UNKNOWN", next_open (UTC ISO8601 or null), next_close (UTC ISO8601 or null), lunch_break: {start, end} | null, settlement_window, data_coverage_years }. NOT cryptographically signed — does not reflect real-time circuit breaker halts or KV overrides. For authoritative signed status use get_market_status. Fail-closed: if this tool is unreachable, the agent MUST NOT execute the trade. LATENCY: sub-100ms p95 (pure schedule computation, no signing).

  ConnectorNo auth

• congress_leaderboardA

  Coldpine: Congressional Stock DisclosuresA

  Members of Congress ranked by disclosed trading activity: trade count, disclosed dollar volume (sum of amount-range midpoints), average trade size, or disclosure speed. Optional chamber and party filters. Same data as coldpine.io/leaderboard. Use it for 'who trades the most in Congress' style questions. Each row has the member, chamber, party, state, trade count, disclosed volume, average trade size, average days from trade to disclosure and the member's coldpine.io page; total_members is the count after filters. This ranks activity only. For returns against the S&P 500 use members_vs_market, and for late filing use stock_act_compliance. Access: needs the agent token from a free Coldpine account, sent as 'Authorization: Bearer <token>'; without it the call returns setup steps instead of data. Read-only, cached for up to an hour.

  ConnectorNo auth

• update-template-partyA

  fynk MCPA

  Update an existing party on a template. Use this tool when: - The user wants to change a party's role label, entity details, or scope - The user wants to link an existing external party to a saved account party, or unlink it again Only send the fields you want to change. `reference` is the party's role label on the template (e.g. "Employer"). Account party linkage: - Send `account_party_uuid` (from list-account-parties) to link the party to a saved account party. While linked, only `reference` may be changed; `entity_name`, `address`, and `scope` cannot be sent. - Send `account_party_uuid` as null to unlink the party, turning it back into an external party whose entity details and scope you can then set. Use get-template-info to discover the parties on a template and their UUIDs.

  Connector

  Destructive

  OAuth

• update-template-partyA

  fynk MCPA

  Update an existing party on a template. Use this tool when: - The user wants to change a party's role label, entity details, or scope - The user wants to link an existing external party to a saved account party, or unlink it again Only send the fields you want to change. `reference` is the party's role label on the template (e.g. "Employer"). Account party linkage: - Send `account_party_uuid` (from list-account-parties) to link the party to a saved account party. While linked, only `reference` may be changed; `entity_name`, `address`, and `scope` cannot be sent. - Send `account_party_uuid` as null to unlink the party, turning it back into an external party whose entity details and scope you can then set. Use get-template-info to discover the parties on a template and their UUIDs.

  Connector

  Destructive

  OAuth

• getmattered_list_due_follow_upsA

  GetMatteredA

  List the user's applications whose follow-up is due, most urgent first: each one's application_id, job, company, urgency, how many follow-ups were sent and the next due date. Read-only: it changes nothing, sends nothing and spends no credits. Do not use it to see the follow-ups already sent; use getmattered_list_sent_follow_ups. Next: getmattered_draft_follow_up for one of these applications.

  ConnectorNo auth

• getmattered_list_due_follow_upsA

  GetMattered (moved)A

  List the user's applications whose follow-up is due, most urgent first: each one's application_id, job, company, urgency, how many follow-ups were sent and the next due date. Read-only: it changes nothing, sends nothing and spends no credits. Do not use it to see the follow-ups already sent; use getmattered_list_sent_follow_ups. Next: getmattered_draft_follow_up for one of these applications.

  ConnectorNo auth

• close_perp_position_reduce_onlyA

  TradeHubA

  Close all or part of a perpetual futures position with a reduce-only market order, so it can never open or flip a position. Use to take profit, cut a loss or reduce exposure; it is also the only way to undo a filled order. Third-party apps can close only positions they opened. Not for cancelling resting orders (use cancel_open_order). Inputs: symbol, venue, close_pct (1-100, default 100). Works while trading is halted. Next: get_my_open_positions.

  Connector

  Destructive

  No auth

• get_bulk_block_dealsA

  DalalOS: Indian Stock Market Research (NSE/BSE)A

  Use this when the user asks about bulk or block trades in an Indian stock on the NSE. Get NSE bulk/block trade disclosures for an Indian stock. Accepts NSE symbol, ISIN, or BSE code. `deal_type` optionally narrows to "bulk" or "block" (omitted returns both); `days` (1..1825, default 90) bounds the trailing window; `limit` (1..500, default 100) caps rows returned, newest first. Each row is a raw disclosed (symbol, counter-party, direction) record: `client_name`, `buy_sell` ("BUY"/"SELL"), `quantity`, `price`, and `remarks` (bulk only). NSE's feed reports one row per counter-party + direction, not a matched buyer/seller pair — there is no official "buyer paired with seller" record. Only NSE's most-recently-published trading day is fetched upstream (no reachable historical bulk/block archive), so coverage starts from whenever the nightly refresh job began running, not further back.

  ConnectorOAuth

• check_room_availabilityA

  Château du BûA

  Answer 'can a party of N stay from DATE for N nights?'. Returns a verdict (bookable yes/no), the reason when no, the room COMBINATIONS that house the party, and the booking URL. Applies the house rules for you: the earliest arrival date (today or tomorrow, depending on the same-day cut-off), and a stay needs the same rooms free on every night. A party too large for one room is NOT a refusal — the house is sold as several rooms. Prefer this over reading the raw calendar.

  ConnectorNo auth

• fill_form_multipageA

  form fill-mcpA

  Fill a multi-page PDF form, iterating page-by-page for reliability. WORKFLOW: 1) Call list_form_fields first to get exact field names and their x/y positions. 2) Use position coordinates to confirm which field is which — higher y = higher on page. 3) Pass exact field names from list_form_fields here. Never guess field names. Use when the PDF has more than 5 pages or fields spanning multiple pages (rental applications, tax packets, multi-section HR forms). Prefer this over fill_form for any complex/long document. Returns ok:false with unknown_fields if ALL provided field names are invalid. Returns ok:true with a warnings.unknown_fields list if SOME names are invalid (partial fill).

  ConnectorNo auth

• mlp_infoA

  MLP Tax Computation EngineA

  Returns reference data for a supported MLP ticker — current cash distribution per unit, distribution growth CAGR, default return-of-capital percentage, distribution coverage ratio, K-1 entity count, operating-state count, and last-verified date. Use when: User wants to look up baseline characteristics of an MLP before modeling — e.g., comparing distribution coverage across partnerships, checking how many K-1 entities a holding generates for tax-prep complexity, or seeing the operating-state count for state-tax filing-burden estimation. Don't use for: Tax computation. Use mlp_projection (long-horizon modeling), mlp_estate_planning (estate analysis), mlp_sell_vs_hold (break-even sell price), or k1_basis_compute / k1_basis_multi_year (computing basis from actual K-1 data). Note: This tool returns reference data only — no IRC citations apply, no methodology disclosure attached. For computation, use the modeling tools above. Maintained by Lucas Andersen, MS Finance.

  ConnectorNo auth

• mlp_infoA

  mlp-taxA

  Returns reference data for a supported MLP ticker — current cash distribution per unit, distribution growth CAGR, default return-of-capital percentage, distribution coverage ratio, K-1 entity count, operating-state count, and last-verified date. Use when: User wants to look up baseline characteristics of an MLP before modeling — e.g., comparing distribution coverage across partnerships, checking how many K-1 entities a holding generates for tax-prep complexity, or seeing the operating-state count for state-tax filing-burden estimation. Don't use for: Tax computation. Use mlp_projection (long-horizon modeling), mlp_estate_planning (estate analysis), mlp_sell_vs_hold (break-even sell price), or k1_basis_compute / k1_basis_multi_year (computing basis from actual K-1 data). Note: This tool returns reference data only — no IRC citations apply, no methodology disclosure attached. For computation, use the modeling tools above. Maintained by Lucas Andersen, MS Finance.

  ConnectorNo auth

• talent_scout_review_queueA

  StackFast FractWin Expert BrainC

  Read the account owner's own first-party Talent Scout job-search work queue for real synced board roles, draft opportunities, packets, follow-up items, and the daily reconciliation report. This is not an employer review queue, applicant screening queue, candidate ranking system, or hiring decision tool. Mailbox reconciliation runs server-side via the StackFast service-account reader. Clients MUST NOT invoke their own Gmail/email connector; if mailbox_reconciliation_status is not ok, surface the red receipt and stop instead of substituting a client-side mailbox read. Surfaces open roles, direct-URL verification needs, waiting/follow-up buckets, preference filters, and today's slate. Robert's connector resolves to tenant robert and demo rows are quarantined away. Review only; no sends or applications.

  ConnectorNo auth