All servers / Security / Transcend MCP server
Transcend MCP server
Transcend MCP Server — unified server with all domain tools.
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-18 on package version 1.7.4. Package: @transcend-io/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (8.5 seconds including download)
- Tools offered: 91
- Last published: 2026-11-18
- Weekly downloads (npm): 2,367
- License: Apache-2.0 · Direct dependencies: 14
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
docs_list4 of 4 parameters describedList or full-text search Transcend documentation. Pick the narrowest argument you can: use route when you know the Admin Dashboard page the user is on ("this page"); it returns that page's docs, then more docs for its product. Otherwise use product when you know the product area. Otherwise use query, which ranks articles by title and body and returns snippets. route and product can each be combined with query. section alone lists one llms.txt section; with no arguments the tool returns the section names. Pick the best matching url, then call docs_fetch.
docs_fetch1 of 1 parameter describedFetch full markdown content for a Transcend documentation article by URL. Use urls returned by docs_list.
dsr_submit6 of 6 parameters describedSubmit a Data Subject Request via customer-ingress REST bulk create (`POST /v1/data-subject-request-bulk`). Call `workflows_list` first and pass a returned `id` as `workflowConfigId` — type and subjectType are derived from that workflow (do not invent them). Sombra attests the subject from the provided email/identifiers. coreIdentifier defaults to email. Returns a minimal summary for each created request. Requires Sombra (SOMBRA_URL or organization customerUrl).
dsr_poll_status1 of 1 parameter describedPoll the current status of a Data Subject Request
dsr_list4 of 4 parameters describedList Data Subject Requests with assigned owners and teams. Filter by identifierValue to look up requests by email or phone (fuzzy/exact across request identifiers, same as admin "Identifier Value (Fuzzy)"). Use emails only for exact match on primary email address. Note: Server-side date filtering is not available — filter results client-side if needed. For per-system failures and system owners, use dsr_list_request_data_silos on a specific request.
dsr_get_details1 of 1 parameter describedGet detailed information about a specific Data Subject Request, including assigned request owners (individual assignees), teams, and request enrichers (enricher.id for dsr_enrich_identifiers without a nonce). For connected system status, failures, and system owners, use dsr_list_request_data_silos.
dsr_list_identifiers3 of 3 parameters describedList decrypted identifiers attached to a Data Subject Request.
dsr_list_request_data_silos6 of 6 parameters describedList connected data systems (request data silos) for a Data Subject Request, including each system's processing status, error message when failed, and the responsible system owners and teams. Use this to diagnose approval or compilation bottlenecks caused by failed or stalled systems. Filter with status=["ERROR"] for failures.
dsr_list_pending_requests2 of 2 parameters describedList outstanding ACCESS or ERASURE jobs waiting on one data silo (integration), oldest first. Each item carries the requestId, the identifier to process, and the Sombra-signed nonce that dsr_enrich_identifiers requires for that job. Requires Sombra and a Transcend API key linked to this data silo; OAuth-only auth returns 401.
dsr_enrich_identifiers5 of 5 parameters describedEnrich a Data Subject Request with additional identifiers during preflight. Prefer a nonce from dsr_list_pending_requests (enrichment stage) or the webhook. Alternate with no nonce: pass requestId + enricherId (official enrich-only header path). Access/erasure respond tools still require a real fulfillment nonce. Requires Sombra. Listing pending jobs needs a Transcend API key associated with that data silo (not OAuth-only).
dsr_cancel3 of 3 parameters describedCancel a Data Subject Request
dsr_analyze1 of 1 parameter describedSummarize the 100 most recent DSRs: counts by type and status, completion rate, and a configurable recent-days window (default 30). For full-fleet analytics, page through dsr_list and aggregate yourself.
consent_get_preferences2 of 2 parameters describedGet consent preferences for a specific user/identifier
consent_list_purposes2 of 2 parameters describedList all tracking purposes configured for consent management.
consent_list_data_flows15 of 15 parameters describedList data flows (network requests) in your consent manager. Requires status: NEEDS_REVIEW (triage) or LIVE (approved). Returns value (URL/host), service, purposes, occurrences. Filter via unmappedOnly, type, trackingTypes, minOccurrences, lastDiscoveredAtBefore/After.
consent_list_cookies13 of 13 parameters describedList cookies in your consent manager. Requires status: NEEDS_REVIEW (triage) or LIVE (approved). Returns name, service, purposes, occurrences, junk status. Filter via trackingPurposes, lastDiscoveredAtBefore/After, minOccurrences, orderField.
consent_list_airgap_bundlesno parametersGet the consent manager (airgap bundle) configured for your organization. Returns the bundle ID, URLs, configuration, and domains.
consent_list_regimes2 of 2 parameters describedList all consent experiences (regional regimes) configured for your organization. Returns experience name, regions, purposes, opted-out purposes, and view state.
consent_get_inventory_statsno parametersGet cookie and data-flow inventory triage counts: live (approved), needs review, and junk. Counts match the Consent Manager tables and the default consent_list_cookies / consent_list_data_flows filters (CSP data flows are omitted, same as the UI). This is inventory status, not consent analytics — use consent_get_aggregate_analytics or consent_get_timeseries_analytics for opt-in/out and signal metrics.
consent_cookie_triage_review_app1 of 1 parameter describedOpens an interactive consent triage review UI for cookies or data flows. Pass triageType ("cookies" | "data_flows"). On MCP App hosts the tool returns a fast shell and the view pages consent_list_cookies or consent_list_data_flows; elsewhere the tool fetches the organization name and items (pages of 100, cap ~600), groups by purpose (≤100/tab), and sorts by traffic. No agent classification suggestions. Use the consent-triage prompt for the full workflow.
consent_get_aggregate_analytics5 of 5 parameters describedQuery aggregate consent analytics via airgapBundleAggregateAnalytics. Use CONSENT_CHANGED with NEW_VALUE/REGIME/PURPOSE for opt-in/out counts; SITE_SESSIONS or PAGE_VIEWS for total traffic. Requires ViewConsentManager API key scope.
consent_get_timeseries_analytics5 of 5 parameters describedQuery timeseries consent analytics via airgapBundleTimeseriesAnalytics. Use PAGE_VIEWS or SITE_SESSIONS for traffic volume; SIGNAL_DETECTED for privacy signal counts. Requires ViewConsentManager API key scope.
consent_get_analytics_data5 of 5 parameters describedQuery consent metrics via the analyticsData GraphQL query. Returns timeseries for privacy signals (DNT/GPC), consent changes (opt-in/out), or sessions by regime. Requires ViewConsentManager API key scope.
consent_update_cookies1 of 1 parameter describedUpdate one or more cookies. Use to approve (status=LIVE), junk (isJunk=true), assign tracking purposes, or set a service. The cookie "name" field is the identifier for upsert — existing cookies with matching names will be updated.
consent_update_data_flows1 of 1 parameter describedUpdate one or more data flows. Use to approve (status=LIVE), junk (isJunk=true), assign tracking purposes, or set a service.
consent_bulk_triage1 of 1 parameter describedBulk triage action: approve or junk multiple cookies and data flows in a single call. For cookies, APPROVE sets status=LIVE; JUNK sets isJunk=true. For data flows, same behavior. Optionally assign tracking purposes and service when approving.
consent_list_roc_records5 of 5 parameters describedList all ROC records for a given user in a partition.
custom_functions_upsert14 of 14 parameters describedCreate or update a Custom Function from plaintext TypeScript. name/description apply immediately; code and runtime settings write a draft — run custom_functions_test_run { id }, then custom_functions_promote_version. Never pass secret values: use environmentVariables with isSecret true and dashboard fill-in. allowedHosts sets outbound domains (omit on update to keep). On create, omit sombraId and dataSiloId unless an error asks for them; use a unique name.
custom_functions_list6 of 6 parameters describedList Custom Functions (lifecycle, gateway, silo, versions). Search with text; check results before upsert when choosing a silo or gateway.
custom_functions_get_code2 of 2 parameters describedLoad plaintext TypeScript and runtime settings for editing (pending draft if any, else active). Pass versionId from the returned versions list to read any version. Returns settings and environmentVariables; secret values are never returned.
custom_functions_promote_version3 of 3 parameters describedPromote a draft Custom Function version to active. Does not run tests; returns untestedWarning when the draft never passed custom_functions_test_run. Returns dependencyWarnings when follow-up may be needed.
custom_functions_test_run11 of 11 parameters describedTest a Custom Function (saved or unsaved TypeScript). Pass { id } alone for the stored version (uses dashboard env); pass code for a trial without secrets. Prefer omitting payload. DSR or GENERAL. Logs mask all env var values, including plain ones.
preferences_list_partitionsno parametersList Preference Store partition keys for this organization: the default airgap-bundle partition plus any custom consent partitions. partitions[].partition is the string to pass as `partition` on preferences_* tools — not the organization id. effectivePartition is the partition the consent manager currently uses; prefer the row with isEffectiveForConsentManager unless the user named another partition.
preferences_query4 of 4 parameters describedQuery consent preferences for multiple users by their identifiers
preferences_upsert3 of 3 parameters describedBatch upsert consent preference records for multiple users. records[].options.mergeRecordsOnConflict controls merge vs fail (default merge). Call preferences_list_partitions first and pass purposes[].enabled (boolean) — Preference Store rejects a "consent" field.
preferences_delete3 of 3 parameters describedDelete consent preferences for specified users
preferences_append_identifiers3 of 3 parameters describedAdd another identifier that resolves to an existing preference record. Leaves current identifiers and their consent history intact.
preferences_update_identifiers3 of 3 parameters describedRewrite an existing identifier value in place, moving its consent history onto the new value. The old value stops resolving.
preferences_delete_identifiers3 of 3 parameters describedRemove one identifier from a preference record, keeping the record and its remaining identifiers. Use preferences_delete to remove the whole record.
inventory_list_data_silos5 of 5 parameters describedList data silos (data systems and integrations) in your organization. Pass `text` or `titles` to search/filter, or `customSiloConnectionStrategy=CUSTOM_FUNCTION` to find silos that can host a DSR Custom Function. Each row includes connectionState and customSiloConnectionStrategy; call inventory_get_data_silo for sombraId. `totalCount` is the full match count, not the size of this page.
inventory_get_data_silo1 of 1 parameter describedGet detailed information about a specific data silo (Data Systems row): vendor link, silo-level processing purposes, owners, teams, business entities, data subjects (allowlist + blocklist), contact/website/notes metadata, identifiers, connectionState, customSiloConnectionStrategy, and sombraId. DSR Custom Functions attach only when strategy is CUSTOM_FUNCTION, sombraId is set, and connectionState is NOT_CONFIGURED (one function per silo). Use before inventory_write_data_silo to avoid overwriting existing assignments. For datapoints on this silo, call inventory_list_data_points with dataSiloId.
inventory_list_catalog_integrations3 of 3 parameters describedSearch the Transcend integration catalog for valid `integrationName` values to pass to inventory_write_data_silo. Pass `text` to match title or integrationName (e.g. "salesforce"). `totalCount` is the full match count, not the size of this page.
inventory_write_data_silo18 of 18 parameters describedCreate or update a data silo (Data Systems table). Pass `dataSiloId` to update by ID, or `integrationName` to create (always creates — never upserts by title). For Custom Function integrations pass integrationName "customFunction" and sombraId. Optional metadata (owners, vendor, purposes, subjects, etc.) applies after create; if that patch fails the error includes `details.dataSiloId` — retry with `dataSiloId`, do not create again.
inventory_list_vendors3 of 3 parameters describedList vendors (third-party data processors) with contact, website, DPA link, address, and headquarters fields. Pass `text` to search. `totalCount` is the full match count, not the size of this page.
inventory_write_vendor11 of 11 parameters describedCreate or update a vendor in the Vendors table. Pass `vendorId` to update by ID, or `title` to upsert by title (creates when missing). Mirrors CLI inventory vendor sync.
inventory_list_data_points4 of 4 parameters describedList data points (collections of personal data). Pass `dataSiloId` to scope to one data system (recommended) and/or `text` to search. Each row includes `dataSiloId`. For field-level purposes/categories, follow up with inventory_list_sub_data_points.
inventory_update_or_create_data_point8 of 8 parameters describedCreate or update a datapoint (and its fields / sub-data points) on a data silo. Use this to assign purpose of processing on fields via `subDataPoints[].purposes` (`{ purpose, name }`, name defaults to "Other"). Mirrors GraphQL updateOrCreateDataPoint.
inventory_list_sub_data_points3 of 3 parameters describedList sub-data points (individual data fields) for a specific data point, including purpose of processing and data category assignments. Empty subcategory names are normalized to "Other".
inventory_list_identifiers2 of 2 parameters describedList identifier types (email, user ID, etc.) configured in your organization. `totalCount` is the full match count, not the size of this page.
inventory_list_categories3 of 3 parameters describedList data category subcategories (PII types) from the Data Categories table. Each row includes `id`, `name`, `category`, and optional `description`. Optional `text` is a HAVING search over name, attributes, and DataCategoryType labels. Use these IDs or name+category pairs when assigning field-level categories via inventory_update_or_create_data_point.
inventory_write_category6 of 6 parameters describedCreate or update a data subcategory in the Data Categories table. Pass `id` to update by ID (name and category cannot change on update), or `name` + `category` to upsert (creates when missing). The unique key is name + category (e.g. "Email:CONTACT"). Use returned IDs when assigning categories via inventory_update_or_create_data_point.
inventory_list_processing_purposes3 of 3 parameters describedList processing purpose subcategories from the Processing Purposes table in Data Inventory. Empty subcategory names are normalized to "Other" to match write-tool defaults. Use these IDs when assigning silo-level purposes via inventory_write_data_silo, or match `purpose`/`name` pairs when assigning field-level purposes via inventory_update_or_create_data_point.
inventory_write_processing_purpose4 of 4 parameters describedCreate or update a processing purpose subcategory in the Processing Purposes table. Pass `id` to update by ID, or `name` + `purpose` to upsert (creates when missing). The unique key is name + purpose (e.g. "Other:ESSENTIAL").
inventory_list_business_entities2 of 2 parameters describedList business entities from Data Inventory. Use `title` values with inventory_write_data_silo `businessEntityTitles`.
inventory_list_data_subjectsno parametersList data subject types configured for the organization. Use `id` values with inventory_write_data_silo `dataSubjectBlockListIds` (IDs of subjects to *block* from the data system — inverse of an allowlist). Returns the full set (not paginated).
inventory_analyzeno parametersAnalyze your data inventory including data silos by type, vendor distribution, and data point coverage
discovery_classify_text3 of 3 parameters describedClassify text content using Transcend's LLM classifier to identify data categories. Requires at least one category label.
discovery_ner_extract2 of 2 parameters describedExtract named entities (PII, organizations, locations, etc.) from text using NER. Requires at least one entity type label.
discovery_list_scans2 of 2 parameters describedList data silos as classification scan records. Each row describes a silo rather than a real scan run, so `status` is not a live scan state; use `inventory_list_data_silos` when you want the silos themselves.
discovery_list_plugins2 of 2 parameters describedList the integration types in use in your organization, derived from the distinct types of the data silos on this page. Because the set is derived per page rather than queried directly, union the results across pages for a complete list.
assessments_list16 of 16 parameters describedList all assessments in your organization. Surface the `url` on each row verbatim; never build assessment URLs from IDs.
assessments_get3 of 3 parameters describedRead one filled-in assessment and the answers submitted to it. Given only assessmentId it returns the section list with a question count each, NOT the question text. To read the questions, either pass questionText to get just the ones on a topic wherever they sit, or sectionIds to expand whole sections; every sectionId must exist or the call fails, and reading the form in full means passing every one of them. Reviewer feedback is counted here but read with assessments_list_comments. Surface the returned `url` verbatim; never build assessment URLs from IDs.
assessments_create3 of 3 parameters describedCreate a new privacy assessment inside an assessment group, resolved by name through assessments_list_groups. Surface the returned `url` verbatim; never build assessment URLs from IDs.
assessments_create_group4 of 4 parameters describedCreate a new assessment group linked to a template. Assessment groups are containers for assessments. Surface the returned `groupUrl` verbatim.
assessments_list_groups5 of 5 parameters describedList all assessment groups. Groups are containers for assessments and are linked to templates. Use this to find the right group ID for creating assessments. To reach the template behind a form, pass its `assessmentGroupId` as `ids` and read `assessmentFormTemplate`. Surface the `groupUrl` on each row verbatim.
assessments_list_comments6 of 6 parameters describedRead the reviewer feedback on one assessment — the comments left on it during review. Returns feedback from all three levels at once, whether it was left on the form as a whole, on a section, or on a single question, each row naming what it sits on. Resolution is per thread on the root comment (no parentCommentId); replies close when that root is resolved. Narrow with levels, authorIds, and resolution (OPEN/RESOLVED/ALL). Use this rather than assessments_get, which only counts feedback. To reply or resolve a thread, call assessments_write_comment with the root id, level, and targetId.
assessments_write_comment7 of 7 parameters describedLeave, reply to, edit, or resolve reviewer feedback on an assessment — form, section, or question. Resolution is per thread on the root comment (no parentCommentId); replies close when that root is resolved. Pass parentCommentId to reply, commentId to edit or resolve a root, or reply with resolved true to close the parent thread. Needs the comment id, level, and target id from existing reviewer feedback on the assessment.
assessments_update6 of 6 parameters describedUpdate an existing assessment. Surface the returned `url` verbatim; never build assessment URLs from IDs.
assessments_list_templates5 of 5 parameters describedList the blank assessment templates. Only `PUBLISHED` ones can build new assessments.
assessments_update_assignees3 of 3 parameters describedAssign internal users (by ID) or external users (by email) to an assessment form. This also transitions DRAFT assessments to SHARED status.
assessments_answer_question3 of 3 parameters describedAnswer an assessment question by selecting existing answer options or providing free-text values. For SINGLE_SELECT/MULTI_SELECT questions, provide assessmentAnswerIds from the answerOptions. For SHORT_ANSWER_TEXT/LONG_ANSWER_TEXT, provide assessmentAnswerValues with {value, isUserCreated: true}.
assessments_submit_response2 of 2 parameters describedSubmit an assessment form for review. Optionally specify which sections to submit. This transitions the assessment toward the IN_REVIEW status. The returned `url` points at the assessment-group page where reviewers find the submitted form — surface it verbatim; never build assessment URLs from IDs.
assessments_create_template4 of 4 parameters describedCreate a new assessment form template with sections and questions inline. This is the "import" side of the JSON import/export workflow. You can provide the full template structure (sections with questions and answer options) in a single call. Question types: LONG_ANSWER_TEXT, SHORT_ANSWER_TEXT, SINGLE_SELECT, MULTI_SELECT, FILE. SubTypes: NONE, CUSTOM, USER, TEAM, DATA_SUB_CATEGORY, HAS_PERSONAL_DATA, ATTRIBUTE_KEY, SENSITIVE_CATEGORY. Auto-corrections: referenceId is auto-generated as UUID if missing or not UUID format; subType is auto-set to CUSTOM when allowSelectOther is true; requireRiskEvaluation is ignored when no riskFrameworkId is provided.
assessments_add_section3 of 3 parameters describedAdd a new section (with optional inline questions) to an existing assessment form template. Useful for building templates incrementally or adding sections to imported templates. Same auto-corrections as assessments_create_template apply to questions.
assessments_export_template1 of 1 parameter describedExport a full assessment form template as JSON, including all sections, questions, answer options, and configuration. This is the "export" side of the JSON import/export workflow. The output can be used as input for assessments_create_template to recreate the template elsewhere.
assessments_prefill8 of 8 parameters describedCreate an assessment form, fill in the answers you supply, and assign it for review in one call. Combines: create form → assign it → read its questions → answer each → optionally submit. Requires assigneeIds or assigneeEmails: a form accepts no answers until it is assigned. The answers are yours to provide; nothing is generated for you. Surface the returned `url` verbatim.
workflows_list2 of 2 parameters describedList workflow configs in your organization. Use each returned `id` as `workflowConfigId` for `dsr_submit`. Results include `actionType` and `subjectType` so you can pick ACCESS vs ERASURE (and subject class) without guessing.
workflows_update_config4 of 4 parameters describedUpdate the configuration for a workflow. Supported fields: title, subtitle, description. Note: privacy-center visibility is controlled by the workflow config's visibility tier and is not editable through this tool.
workflows_list_email_templates2 of 2 parameters describedList all email templates used in workflows and communications.
policy_get_templates1 of 1 parameter describedList Policy Engine starter templates (no args) or return scaffold files (templateId). ActivatePolicyEngineBundles covers all policy tools — do not create separate API keys per operation.
policy_list_bundles6 of 6 parameters describedDiscover Policy Engine bundles, version history, and download URLs. Mirrors transcend policy bundles / versions / download. Requires View Policy scope (included in Activate scope).
policy_publish6 of 6 parameters describedUpload an inert Policy Engine version from files (in-memory map) or dir. Not live until policy_set_live activate. Requires Manage Policy scope (included in Activate).
policy_set_live6 of 6 parameters describedExplicit go-live or take-offline step after policy_publish. action "activate" makes a version live; "deactivate" clears the active version. Mirrors transcend policy activate / deactivate. Requires Activate Policy scope.
admin_get_organizationno parametersGet information about your Transcend organization
admin_get_current_userno parametersGet information about the currently authenticated user (the API key owner)
admin_list_users15 of 15 parameters describedList users in your Transcend organization with the same filters as Administration → Users. text searches name and email (case-insensitive substring). Team filters need UUIDs — call admin_list_teams then pass teamIds. scopeNames / derivedScopeNames use ScopeName values from admin_list_scopes. Default sort is name ASC.
admin_list_teams2 of 2 parameters describedList all teams in your Transcend organization.
admin_list_api_keys2 of 2 parameters describedList all API keys configured for your organization (tokens are not shown).
admin_list_scopes2 of 2 parameters describedList valid ScopeName values for API keys and user permissions. Default rows are compact (name, title, type, dependencies). Filter with text; set includeDetails only when titles are not enough.
admin_get_privacy_centerno parametersGet privacy center configuration for your organization
admin_test_connectionno parametersTest connectivity to both Transcend REST and GraphQL APIs
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.