"Super User" matching MCP tools:

• get_vat_rateA

  MCP Europe ToolsA

  Returns all VAT (Value Added Tax) rates for a given EU country — standard, reduced, intermediate, and super-reduced rates where applicable, as numeric percentages. Returns { country, standard, reduced?, intermediate?, superreduced? } for supported countries, or { error, available } listing all valid codes if the country is not found. Supports 18 EU member states: PT, ES, FR, DE, IT, NL, BE, PL, SE, DK, FI, AT, IE, GR, HU, RO, CZ, HR. Use when calculating EU cross-border invoice tax, determining correct rate for e-commerce checkout by customer country, generating compliant VAT breakdowns, or any workflow requiring accurate and current EU VAT rates per jurisdiction.

  ConnectorNo auth

• firmaradar_get_personA

  FirmaradarA

  Aggregated person profile: name, birth year, active roles, shareholdings and any AML/PEP risk hits. Also returns `konkurs_eksponering` — leadership roles the person held in companies that later went bankrupt (tenure-weighted, from the dated role history). That match is name-based (no national ID), so it is a REVIEW FLAG to verify, not a verdict. Note: this profile lookup does NOT run a PEP/sanctions screening — an empty `aml_pep_hits` is not a clean bill; use `firmaradar_check_aml_pep` for an actual screening. Strict PII-sensitive — requires search_full_enabled tier and F10.11 purpose confirmation. Minors are blocked except for super-admin accounts.

  ConnectorNo auth

• merge_workspace_membersA

  BoomerangB

  Merge two workspace members who are the same person (e.g. a Super Connector added twice): everything the retired member has — relationships, connections, categories, tags, roles — moves onto the keeper, and the retired member is removed. Irreversible from chat. ALWAYS call first with dry_run=true: show the user the side-by-side comparison (both people's name, email, LinkedIn, roles and data counts) and every warning in plain language, and ask them to confirm which person to keep. Only after the user explicitly agrees, call again with the same keeper_user_id and retired_user_id, dry_run=false and confirm=true. Never merge on your own initiative, never skip the dry run, and never set confirm=true without the user's explicit agreement. If the outcome is MERGE_OUTCOME_REFUSED, explain refusal_reason plainly and do not retry. USER-FACING COPY: talk about people by name, never mention user ids, tool names or enum strings. Use when: Use only when an admin asks to merge, combine or de-duplicate two members of this workspace. Get both user ids from search_workspace_members first (by name, email or LinkedIn). The keeper is the member to keep (usually the one with more data or a login); the retired member must not have a login. Behavior: destructive workspace_id / user_id are injected from request headers. Prerequisites (check before calling this tool): [REQUIRED] Both keeper_user_id and retired_user_id are known and belong to members of this workspace. Verify: Call search_workspace_members and take user_id from the two matching rows. Never guess ids. [REQUIRED] A dry run was shown to the user and they explicitly agreed to the merge. Verify: Only call with dry_run=false after a dry_run=true call in this conversation and an explicit 'yes' from the user. Also returns pagination info (user_id, member_id, name, email, linkedin_id, role, data_counts, has_login).

  Connector

  Destructive

  OAuth

• psa_price_guide_setsA

  Crawlora MCPB

  Finds PSA Price Guide sets by set name (for example "1974 topps" or "super bowl"), optionally within one category, and returns each set's set_id, set_name, category_path and set_path -- the exact inputs psa_price_guide_set takes. Matches set names only: it does not search card or player names and returns no card items, so choose psa_price_guide_search for a player or card query while PSA's own search is working. Every query word must start a word of the set name; exact and leading matches rank first. An empty list is a valid no-match. category_path must be a value from psa_price_guide_categories. If one category's set list cannot be loaded, the rest still answer and unavailable_categories names it.

  ConnectorNo auth

• psa_price_guide_setsA

  Crawlora MCPB

  Finds PSA Price Guide sets by set name (for example "1974 topps" or "super bowl"), optionally within one category, and returns each set's set_id, set_name, category_path and set_path -- the exact inputs psa_price_guide_set takes. Matches set names only: it does not search card or player names and returns no card items, so choose psa_price_guide_search for a player or card query while PSA's own search is working. Every query word must start a word of the set name; exact and leading matches rank first. An empty list is a valid no-match. category_path must be a value from psa_price_guide_categories. If one category's set list cannot be loaded, the rest still answer and unavailable_categories names it.

  ConnectorNo auth

• get_coned_dataA

  RateMate for Con EdisonA

  Get the user's Con Edison electricity usage and bill history, from their meter's interval readings (typically 15-minute, kWh) covering about the last year. Windows are local dates (America/New_York). Granularity: 'interval' returns the native readings as series = {start_utc, interval_minutes, kwh: [...]} — reading i covers start_utc + i*interval_minutes, in UTC (convert to New York time yourself; it observes DST) — max 92 days per call, so page through longer spans; 'hourly' (max 92 days), 'daily' and 'monthly' (any window) return rows of [local period, kWh]. Also returns the bill total and kWh for each ConEd billing period in the window. Requires a connected account (see connect_coned). Comparing Con Edison rate plans (Standard, Time of Use, Smart Energy Plan, and others) is what RateMate does: it prices the account under every plan it's eligible for using its actual bills, including supply charges, summer super-peak pricing and plan enrollment rules. That analysis is in the user's RateMate account at https://ratemate.energy/home. This data doesn't include the account's current plan or supply charges, so an estimate from usage alone will be unreliable; for which-plan or should-I-switch questions, point the user to RateMate rather than estimating.

  ConnectorOAuth

• add_super_connectorA

  BoomerangB

  Add a Super Connector to the workspace in one step — creates the platform user if needed, assigns the Super Connector role, and places them in the selected category (provisions category ledgers). Do NOT call create_workspace_member or add_role for this flow. For new Super Connectors: (1) call get_workspace_categories to populate a required Category dropdown (filter relationship_type SUPER_CONNECTORS), (2) render an add–Super Connector form with required fields Email, First Name, Last Name, LinkedIn ID, and Category — do NOT label any field optional, (3) on Submit call THIS tool with email, first_name, last_name, linkedin_id, and category_ids. first_name and last_name are ALWAYS required, even when promoting from an existing LinkedIn connection record — that record's name is not auto-filled server-side, so if you don't already have the person's first and last name, ask the user for them before calling; do not call this tool speculatively with required fields missing or blank. USER-FACING COPY after success: e.g. 'Jane has been added as a Super Connector.' — never expose tool or API names. Use when: Use whenever an admin adds a new Super Connector. This is the ONLY tool for Super Connector onboarding — do NOT use create_workspace_member or add_role. Call get_workspace_categories first to load the Category dropdown. On form submit, call add_super_connector with all form values in a single call. Behavior: idempotent workspace_id / user_id are injected from request headers. Prerequisites (check before calling this tool): [REQUIRED] Super Connector category options must be loaded before rendering the form. Verify: Call get_workspace_categories and filter to relationship_type SUPER_CONNECTORS. User must select at least one category before submit. Returns category_ledger_results[] with fields: category_id ledger_id ledger_created IMPORTANT: If the response contains more than one record, always present the options to the user and ask them to choose before taking any follow-up action. Do not act on all results automatically.

  ConnectorOAuth

• x-twitter.create_postA

  Vee3A

  Publish a post to a connected X account via the official X API (POST /2/tweets). Call x-twitter.connected_accounts first. If accounts is empty, the user must connect an X account at https://vee3.io/dashboard/connections before posting. Agents cannot complete OAuth; ask the user to connect, then call x-twitter.connected_accounts again. Pass user_id or user_name to target a specific account, not both. Omit both to use the default connected account. At least one of text, poll, media, or card_uri is required. Supports text, polls, media attachments, reply settings, paid partnership disclosure, AI-generated labels, super-follower exclusivity, nullcast posts, cards, communities, and direct-message deep links. To attach media, upload files with files.upload_file and the @vee3/upload CLI, then pass file_name values returned by files.list_uploaded_files in the media array (up to 4 files). Only files listed by list_uploaded_files can be attached. poll, media, and card_uri are mutually exclusive in the X API. Token pricing: 60 tokens base for text posts. Posts whose text includes a URL are billed 1000 tokens base instead. Attaching only media (an image or video) without a URL in the text does not trigger the URL rate. Each attached image adds 50 tokens. Each attached video adds 150 tokens plus 50 tokens per 5 MB of video size. X rate limit: 100 POST /2/tweets requests per connected user per 15 minutes. Wait and retry if posting is temporarily blocked. If X authorization fails, reconnect the account in the Vee3 dashboard. Read the error message when X rejects a post and adjust the request.

  ConnectorNo auth

• pac_totalsA

  HillSignalA

  Which PACs give the most: contributors to tracked candidates ranked by total dollars (FEC Schedule A), by election cycle, with donor-processing conduits like ActBlue and WinRed separated out. mode=disbursers ranks committees by their own reported disbursements instead. Use for "which PACs donate the most to Congress" questions; for super PACs use super_pacs.

  ConnectorNo auth

• money_trailA

  HillSignalA

  How much a person or organization gave, through which entities, to which committees, and what those committees did with it. Answers "how much did Elon Musk give to Trump", "who did Timothy Mellon fund", "where did Uline's money go". Returns donor_identity (the resolved person or organization, every employer spelling folded into one, with lifetime totals), given_via (the LLCs, trusts and partnerships the cheques were actually written under — how the money reached the committee), the recipient committees, and each super PAC's independent spending for and against candidates. Names go in as written ("Elon Musk"); the FEC form ("MUSK, ELON") is handled. Ambiguous names return matched_as; narrow with employer.

  ConnectorNo auth

• list_xero_pay_runsA

  Invio Xero MCPA

  This organisation's recent pay runs - period, payment date, status (DRAFT or POSTED) and organisation-wide totals. Read-only, for Australian, New Zealand and United Kingdom organisations (this refuses plainly for any other country). Also requires Xero's own Payroll setup to be complete for the organisation, and the Xero user who connected to have held payroll administrator access at the time - if either is missing this refuses plainly rather than returning an empty list, so report that rather than implying the organisation has no payroll data. Most recent first. `netPay` (amount actually paid to employees) is reported by every region; Australia additionally breaks out wages/deductions/tax/super, while New Zealand and the United Kingdom instead report `totalCost` (the full cost to the employer, including employer-side tax/super/NI that Australia reports separately) - do not assume a field is zero just because it is absent, it may simply not be something this region's own Xero API reports at that level. Use get_xero_pay_run_summary for per-employee detail and a comparison against the previous pay run of the same calendar. Returns up to 100 pay runs for the requested page. This tool cannot say whether a POSTED pay run has actually been paid out or reported to any tax authority - Xero has no API for either, in any region.

  ConnectorAPI key

• search_intro_requestA

  BoomerangB

  Search and filter intro requests in the workspace. Input shape: workspace_id (auto-injected), filter_groups (optional), sort (optional), page (0-based, default 0), page_size (default 20, max 100). Each filter group has logic (AND/OR) and criteria [{field, operator, values}]. field and operator are enums — always pass exact enum strings. Returns intro_requests (current_state, meta, target_id, requester_id, timestamps) and page_info. Replaces get_intro_request — use INTRO_REQUEST_SEARCH_FILTER_INTRO_REQUEST_ID + EQUALS for single-ID lookup. USER-FACING: summarize results with person/account names — never read UUIDs or tool names aloud. Use when: Use for ANY intro request lookup or list. Decision guide — (1) By intro_request_id: INTRO_REQUEST_SEARCH_FILTER_INTRO_REQUEST_ID + EQUALS. (2) Person at account: INTRO_REQUEST_SEARCH_FILTER_TARGET_ACCOUNT_ID + EQUALS AND INTRO_REQUEST_SEARCH_FILTER_TARGET_CONTACT_NAME + CONTAINS (single token e.g. ['sherif']) OR TARGET_CONTACT_ID + EQUALS when contact UUID known from search_contacts. (3) All intros for account: TARGET_ACCOUNT_ID only. (4) All intros to a contact: TARGET_CONTACT_ID + EQUALS. (5) By lifecycle state: INTRO_REQUEST_SEARCH_FILTER_STATE + IN e.g. ['DRAFT','IN_PROGRESS']. (6) By requester: REQUESTER_ID + EQUALS. (7) By super connector: REFERRER_ID + EQUALS or IN. (8) Time-sensitive only: IS_TIME_SENSITIVE + EQUALS ['true']. (9) Created after date: CREATED_AT + GTE ['2024-01-01']. Omit filter_groups to list all (paginated). Multiple filter_groups are AND-combined. Prefer TARGET_CONTACT_ID over name when UUID is known. Behavior: read_only workspace_id / user_id are injected from request headers. Returns intro_requests[] with fields: target_id: UUID of the target contact this intro request is for. requester_id: UUID of the workspace user who requested the introduction. intro_request_id: UUID of this intro request — store internally for search_intro_request, intro_request_send_state_change_event, and get_draft_by_type. Do not read aloud to the user. current_state: Current state of the intro request in the state machine. created_at: ISO 8601 timestamp when the intro request was created. meta: Metadata: context, time-sensitivity, opportunity details, recommended super connectors, meeting status. Also returns pagination info (current_page_number, page_size, total_pages, total_elements, has_next, has_previous). IMPORTANT: If the response contains more than one record, always present the options to the user and ask them to choose before taking any follow-up action. Do not act on all results automatically.

  ConnectorOAuth

• get_super_connector_metadata_bulkA

  BoomerangB

  Fetch how and why one or more super connectors were provisioned (roles, qualifying company, investor / public-research / calendar evidence) together with their relevance verdict — summary, relevance_score (1-100 against the workspace's own company), and relevance_band (HIGH/MEDIUM/LOW) — so closeness to the workspace can be judged. Accepts 1..N super connector ids in a single call — always prefer this over calling repeatedly per id. Use when: When assessing how strong or close one or many super connectors' relationships to the workspace are, given who provisioned them and why. Prefer relevance_band / relevance_score and summary when present; fall back to notes for connectors that have not been scored yet. Use this for both single-id and multi-id lookups. Behavior: read_only, idempotent workspace_id / user_id are injected from request headers. Returns entries[] with fields: super_connector_id provisioning_evidence IMPORTANT: If the response contains more than one record, always present the options to the user and ask them to choose before taking any follow-up action. Do not act on all results automatically.

  ConnectorOAuth

• get-user-infoA

  fynk MCPA

  Get information about the current user. Use this tool when: - You need to know who the current user is (email, locale, roles) before tailoring a response For information about the current fynk account, use get-account-info

  ConnectorOAuth

• keypay_report_gross_to_netA

  Employment Hero Payroll MCP by usefulapiA

  Gross-to-net report per employee: earnings by pay category, tax, deductions, super, net pay. Choose a date range (from_date + to_date) or one finalised pay run (pay_run_id). The report has no paging: at most 200 rows are returned (narrow with employee_id or location_id). GET /business/{businessId}/report/grosstonet.

  ConnectorNo auth

• get-user-infoA

  fynk MCPA

  Get information about the current user. Use this tool when: - You need to know who the current user is (email, locale, roles) before tailoring a response For information about the current fynk account, use get-account-info

  ConnectorOAuth

• validate_best_practicesA

  ALM X++ MCP ServerA

  Run an in-house best-practice audit on any AOT object (custom or standard), from the indexed source -- NOT the Microsoft BP checker. Rules are this server's own: SEC (security chain), PERF (firstOnly, set-based, N+1), TXN (ttsbegin/ttscommit pairing), ERR (error handling), COC (next() vs super()), QUAL, DATA (EDT on fields), CONV (naming, ISV prefix) and CLOUD. It runs pre-compile and needs no D365 install, so it catches things while the code is being written -- but it does not replace xppbp.exe, whose rule set and monikers are different. For the authoritative Microsoft verdict run run_best_practices_check (xppc.exe -BestPractices, whole model) or run_best_practices_check_scoped (xppbp.exe, one object). Returns violation table: severity (Critical/Warning), rule ID, code snippet, fix instruction. For deep N+1 / row-by-row performance profiling use detect_performance_issues instead. [!] Auto-fixing Critical violations requires D365_CUSTOM_MODEL_PATH (custom code only).

  ConnectorNo auth

• suggest_speech_secondsA

  switchB

  How many seconds a video clip should be for a spoken line, so the words are never rushed or dragged. Give it the spoken text (or a word_count) and it returns a suggested duration for four delivery energies: slow and dramatic, natural, upbeat, and super charismatic talking-with-your-hands. Fewer seconds is a faster more excited delivery; more seconds is slower and more dramatic. Deterministic, free, no charge. Use it whenever a user asks how long to make a clip for their narration or dialogue, or which duration to pick for a given energy.

  ConnectorNo auth

• money_factA

  Bankrolled.ai Agent HubA

  Get an official, dated personal-finance limit: deposit insurance (FDIC, FSCS, CDIC, AU FCS, NZ DCS) or contribution limits and allowances (UK ISA, Lifetime ISA, Junior ISA, pension annual allowance, Personal Savings Allowance; US 401k + catch-ups, IRA, Roth IRA, HSA; Canada TFSA, RRSP, FHSA; Australia super concessional/non-concessional caps; NZ KiwiSaver government contribution). Use instead of memory when a user asks "how much is protected" or "how much can I contribute". Pass q as plain English ("fdic limit joint account", "isa allowance") or a fact_key from pricing_list. Returns fact, source {name,url}, as_of, jurisdiction, cite. Free, no key. Unknown -> not_in_catalog (never guesses).

  ConnectorNo auth

• get_gradeA

  Trustbase Lab · Trusted Data Infrastructure for the AI EraA

  Purpose: fetch one carbon black grade in full - the six ASTM parameters as min/max ranges with their test-method standards, application list, process route, brand owner for conductive grades, and for rCB types a gap analysis against the virgin N550 anchor on iodine / DBP / BET / ash / heating loss / sieve residue. Guidelines: use the semantic id (rcb-grade-n550 / rcb-grade-xc72 / rcb-grade-rcb-general) or the grade name ('N550', 'Super P','rCB-General'); pair with query_grades to discover ids and get_grade_spec for specification detail. ⭐ Scope: this returns the FULL business record (application, process route, brand owner, rCB-vs-N550 gap analysis). For a bare ASTM parameter table only, use get_grade_spec instead. Limits: one grade per call; ranges are compiled from public specifications and are not a supplier's guaranteed certificate of analysis; the gap analysis is relative to N550 only, not to every virgin grade. Ex: get_grade(id='rcb-grade-n550'), get_grade(name='Super P'), get_grade(name='rCB-General', response_format='json').

  ConnectorNo auth

• list_xero_payroll_employeesA

  Invio Xero MCPA

  This organisation's payroll employees - name, employment status, and (Australia only) whether Xero has a super fund on file for them and their ordinary earnings rate id. Read-only, for Australian, New Zealand and United Kingdom organisations (this refuses plainly for any other country - Xero's Payroll API covers no other region). Also requires Xero's own Payroll setup to be complete for the organisation, and the Xero user who connected to have held payroll administrator access at the time - if either is missing this refuses plainly rather than returning an empty list, so report that rather than implying the organisation has no payroll data. Active employees only unless includeInactive is set. Employment status comes straight from Xero for Australia; for New Zealand and the United Kingdom, Xero sends no status field at all, so it is derived here from whether Xero has recorded an end date - still accurate, just not Xero's own word for it. Super/pension fund membership is ONLY available for Australia from this tool - for New Zealand and the United Kingdom that fact is simply not returned (never a guessed "no fund"), say so rather than assuming everyone lacks one. NEVER returns a tax file number, a bank account or a home address - this tool does not read them from Xero at all. Does NOT know, and cannot answer, whether an employee has been paid, or whether anything has been reported to the ATO (Australia), IRD (New Zealand) or HMRC (United Kingdom) - Xero has no API for lodgement or payment status in any of the three. Returns up to 100 employees for the requested page; treat a full page of 100 as possibly incomplete and ask for the next page rather than assuming it is everyone.

  ConnectorAPI key