TrustLayer

You run an MCP server that exposes read‑only access to the Public TrustLayer API. Clients connect to the MCP endpoint to retrieve parties, documents, projects, and other TrustLayer data in structured JSON, using standard GET operations. This server is designed for safe, read‑only access and easy integration with tools and automation.

How to use

Connect your MCP client to the server using the HTTP endpoint for remote access or run the server locally in stdio mode for testing and integration with local tools. In HTTP mode, authentication can be provided per request via the Authorization header, enabling multiple clients to use distinct API tokens. In stdio mode, the server reads the API token from environment variables.

You can query a wide range of TrustLayer data, including parties, documents, projects, tags, compliance profiles, party types, custom fields, reports, webhooks, and branding configurations. Use the client’s MCP data access patterns to list resources or fetch individual items by ID. All responses are delivered as JSON and follow the Public TrustLayer API data shapes.

How to install

Prerequisites: You need Python 3.11 or newer and a TrustLayer API token if you access protected data.

cd mcp-server

# Create a Python virtual environment
python -m venv venv

# Activate the virtual environment
# On macOS/Linux:
source venv/bin/activate
# On Windows:
venv\Scripts\activate

# Install dependencies
pip install -r requirements.txt

# Create environment file for configuration
cp env.example .env

# Edit .env and set required values (examples shown):
# TRUSTLAYER_API_BASE_URL=https://api.trustlayer.io
# TRUSTLAYER_API_VERSION=v1
# TRUSTLAYER_API_TOKEN=your_api_token_here  # optional for HTTP mode

Configuration options you will set in the environment file include the base URL for TrustLayer, the API version, and optionally an API token if you plan to run in stdio mode or want to pass the token via environment.

Additional information

Configuration and operation details are provided to enable you to run the MCP server in either stdio or HTTP mode. Your setup should include the correct base URL for the TrustLayer API, the API version, and the appropriate authentication method (per-request header in HTTP mode or environment variable in stdio mode). For production deployments, consider exposing the HTTP endpoint behind a reverse proxy with HTTPS and implementing access controls.

# Quick health check (when running the HTTP server)
curl http://localhost:8000/health

Available tools

get_party

Fetch a single party by its ID using a GET operation.

get_document

Fetch a single document by its ID.

get_project

Fetch a single project by its ID.

get_contact

Fetch a single contact by its ID.

get_party_contacts

List all contacts associated with a party.

get_party_compliance_profile

Retrieve the compliance profile for a party.

get_party_compliance_certificate

Retrieve the compliance certificate for a party.

get_party_document_request

Retrieve the document request for a party.

get_compliance_profile

Fetch a compliance profile by ID.

get_report

Fetch a report by ID.

list_parties

List all parties with optional pagination.

list_documents

List all documents with optional pagination.

list_projects

List all projects with optional pagination.

list_tags

List all tags available in the TrustLayer data set.

list_compliance_profiles

List all compliance profiles.

list_party_types

List all party types.

list_custom_fields

List all custom fields.

list_reports

List all reports.

list_webhooks

List all webhooks.