Onetrust Api MCP Server

onetrust-api PyPI v0.2.1

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 98/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 2 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 36

Each tool and what it can reach — statically extracted from the published source.

  • onetrust_access_managementno sensitive capability
  • onetrust_ai_governanceno sensitive capability
  • onetrust_api_requestno sensitive capability
  • onetrust_assessmentsno sensitive capability
  • onetrust_audit_managementno sensitive capability
  • onetrust_bulk_exportno sensitive capability
  • onetrust_cmpno sensitive capability
  • onetrust_compliance_automationno sensitive capability
  • onetrust_consent_interfacesno sensitive capability
  • onetrust_consent_receiptsno sensitive capability
Show 26 more tools ↓
  • onetrust_cookie_consentno sensitive capability
  • onetrust_cookie_consent_legacyno sensitive capability
  • onetrust_cookie_domain_datano sensitive capability
  • onetrust_cross_device_consentno sensitive capability
  • onetrust_data_catalogno sensitive capability
  • onetrust_data_discoveryno sensitive capability
  • onetrust_data_discovery_workerno sensitive capability
  • onetrust_data_mappingno sensitive capability
  • onetrust_data_mapping_legacyno sensitive capability
  • onetrust_documentsno sensitive capability
  • onetrust_dsarno sensitive capability
  • onetrust_esgno sensitive capability
  • onetrust_incidentsno sensitive capability
  • onetrust_integrationsno sensitive capability
  • onetrust_inventoryno sensitive capability
  • onetrust_issues_managementno sensitive capability
  • onetrust_it_risk_managementno sensitive capability
  • onetrust_mobile_app_consentno sensitive capability
  • onetrust_object_managerno sensitive capability
  • onetrust_policy_managementno sensitive capability
  • onetrust_privacy_noticesno sensitive capability
  • onetrust_task_managementno sensitive capability
  • onetrust_tprmno sensitive capability
  • onetrust_trainingno sensitive capability
  • onetrust_universal_consentno sensitive capability
  • onetrust_user_provisioningno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.2.1 latest A 98/100 0 1.8.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/onetrust-api/badge.svg)](https://mcptrustchecker.com/registry/onetrust-api)
HTML
<a href="https://mcptrustchecker.com/registry/onetrust-api"><img src="https://mcptrustchecker.com/registry/onetrust-api/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/onetrust-api/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan onetrust-api --online --registry pypi

Use the free API → How scoring works

More in Developer Tools