AI agents

Run the compliance workflow through tools, not through model recall.

Compliance Platform exposes MCP tools so an AI assistant can classify goods, check duties, screen exposure to EU sanctions against Russia and Belarus, and generate source-linked reports through controlled organization access.

MCP workflow

The agent asks the platform before it answers the user.

A good compliance agent should route the user request to the right tool, return the key finding first, and keep official source references available for verification.

Request test access View sample report

See a real session output

Agent routing rules

Project instructions excerpt

Tool-first

Always use the MCP tools for any CN/TARIC code question.

When a CN code and country are given, run the compliance check immediately.

Highlight review-required warnings and sanctions matches prominently.

Use the HTML report for detailed evidence instead of dumping raw measure lists.

Connector setup

A concrete MCP connector screen for technical reviewers.

This is the kind of setup screen an IT or operations reviewer expects to see: endpoint, organization credential, and an explicit connector label. The key itself should never be published or shared in visible form.

The connector name is just a label inside the AI workspace.

The server URL points to the Compliance Platform MCP endpoint.

The masked field is the Organization API key generated in Platform → Settings → API Keys.

The AI workspace masks the key after it is pasted; the screenshot does not expose a usable secret.

Example Claude custom connector setup for the Compliance Platform MCP server — Example setup screen. Use the Organization API key issued by Compliance Platform; the workspace masks the key after it is pasted.

Setup path

Settings should be boring, explicit, and reviewable.

The goal is to make the agent predictable: connect the MCP server, use a scoped organization key, add instructions, then test with one code.

1. Connect the MCP server

Claude

Direct API key

Add the MCP endpoint URL in Claude's connector settings, then paste your Organization API key into the API key or Authorization field. No OAuth form — Claude connects immediately.

https://api.compliance-mcp.com/mcp

ChatGPT

OAuth

Add the MCP endpoint URL as a custom connector in ChatGPT, then click Connect. You will be redirected once to enter your Organization API key.

https://api.compliance-mcp.com/mcp

2. Add agent instructions

Tell the agent to use MCP tools for CN/TARIC questions and to avoid answering from memory.

Tool-first behavior

3. Test with one code

Ask for a real code and country context. The agent should call the tool immediately.

Check 8504403000 · China

Live dialogue example

After connector and skill setup, the AI assistant works immediately.

The important demo is not the settings screen. It is the first real conversation where the agent reads the skill, calls the MCP tools, and turns live compliance data into a useful working view.

Excerpt reconstructed from a real Claude session, April 2026. Claude is a product of Anthropic; product names and UI screenshots are used for identification only. Compliance Platform is independent and is not affiliated with Anthropic.

User

Hey Claude — I just added the compliance-skill. Can you make something amazing with it?

The agent reads the skill

The assistant recognizes that the skill connects to the Compliance Platform MCP server and that TARIC and sanctions questions should go through live tools.

The agent calls MCP tools

It checks code 7601 10 00 for Belarus, then pulls Russia for the same code so the comparison is based on real platform data.

The agent builds a working view

The result is an interactive command-center: BY/RU side-by-side, drill-down buttons, and a way to query another code.

Compliance command center

7601 10 00

Aluminium, not alloyed · chapter 76

Reg. 765/2006Date: 2026-04-28

Belarus

Review required

Tariff measures

Sanctions matches

Export

Export luxury

Import

Russia

Review required

Tariff measures

Sanctions matches

Export

Export (2nd match)

Import

Tariff measures side-by-side

Measure	Code	BY	RU
Entry into free circulation	1008	2,500	2,500
Airworthiness tariff suspension	1011	0%	0%
Third country duty	103	—	3.0%
Non-preferential tariff quota	122	—	3.0%
Export restriction	467	—	Active

Measure type 467 reflects export restrictions under Regulation 833/2014 (Russia sanctions package).

BY full report ↗

RU full report ↗

Check another code ↗

HTML report proof

Ask the assistant for the full file, not another chat summary.

The strongest AI-agent demo is when the assistant uses the MCP integration, creates a standalone HTML report, and gives the reviewer a downloadable evidence file.

The report keeps TARIC measures, sanctions annex matches, footnotes, and warnings together.

The chat stays readable while the detailed evidence moves into the generated file.

Critical trade and regulatory decisions should be reviewed by qualified customs, legal, or trade compliance professionals and verified against official sources or competent authorities.

Part 1

Session output excerpt

Claude conversation excerpt showing a generated downloadable Compliance Platform HTML report file — Excerpt from a Claude conversation, April 2026. The agent generated a standalone BY HTML report with TARIC and sanctions-annex evidence.

Compliance Platform HTML report evidence showing sanctions annex and TARIC sections — Excerpt from a Claude conversation, April 2026. The agent generated a standalone BY HTML report with TARIC and sanctions-annex evidence.

Part 2

Readable breakdown extracted from the same session

Reconstructed from a real session. Tool calls and report content are unmodified.

Session transcript

Using Compliance MCP integration

Prompt
Show me the full file for BY
Response
I will grab the full BY report and save it as a downloadable file.
Used Compliance Platform MCP tools and file output
Full BY compliance report for 7601 10 00 - standalone HTML with all measures, conditions, sanctions matches, and footnotes.

BY Compliance Report — 7601 10 00 — EN

Code · HTML

Download

BY Compliance Report — 7601 10 00 — EN · HTML

Generated report preview

CopyHTML

Goods code: 7601100000Origin/destination: BYLanguage: ENDate: 2026-04-282 measures

Sanctions annex check

76	BY Reg. 765/2006 ANNEX XVIII — Industrial capacity enhancement goods	EXPORT
7601	BY Reg. 765/2006 ANNEX XXV — Luxury goods	EXPORT LUXURY
7601	BY Reg. 765/2006 ANNEX XXVII — Revenue-generating goods	IMPORT

TARIC measure information

76ALUMINIUM AND ARTICLES THEREOF

7601Unwrought aluminium

7601 10Aluminium, not alloyed

7601 10Aluminium, not alloyed(TN701) (CD333)

Entry into free circulation

Measure 1008 · Trade context

2500.0

0640/18

Airworthiness tariff suspension

Measure 1011 · Trade context

1517/18

Footnotes flagged: CD333 and TN701. The report gives the reviewer a concrete source trail, while the platform reminds users to verify critical decisions against official sources.

Open sample report

Claude workspace settings

Recommended Claude settings for working with platform data.

If an AI assistant is used to work with Compliance Platform data, technical reviewers should know where network access, skills, and connector behavior are configured.

Use a narrow domain allowlist when the assistant needs network access to platform data.

Allow `api.compliance-mcp.com`; avoid broad wildcards unless there is a clear operational reason.

Skills configuration is a good place to keep the agent behavior explicit and reviewable.

Connectors can also be managed from the workspace Customize settings, depending on the UI.

Claude capabilities settings showing api.compliance-mcp.com added to the allowed domains list — Example network egress allowlist. Add `api.compliance-mcp.com` only when the assistant needs to access platform data through the configured workflow.

Compliance skill instructions

Recommended prompt for the AI workspace

Tool-first

Role

You are a trade compliance assistant connected to the Compliance Platform MCP server.

Help users work with EU trade compliance data: CN/TARIC classification, tariff measures, duties, conditions, and EU sanctions exposure against Russia and Belarus.

Core rules

Always use Compliance Platform MCP tools for CN/TARIC code questions. Do not answer from memory alone.

Default language is English. Use language=LV only if the user writes in Latvian.

Results support compliance review. They do not replace legal, customs, or qualified trade compliance advice.

Do not present any result as final clearance for import, export, transit, sanctions, or other trade and regulatory decisions.

Tool routing

CN/TARIC code + country -> check_trade_compliance by default.

Full report, downloadable file, source-linked evidence, or detailed compliance review -> check_trade_compliance.

Sanctions only for RU or BY -> check_sanctions.

Product description without a CN code -> search_cn_codes first.

Classification hierarchy only -> get_cn_description.

Tariff measures without sanctions screening -> get_measures.

Quick summary or duty-rate questions -> check_trade_compliance, then summarize the relevant fields.

Output style

Lead with the key finding: duty rate, sanctions flag, review_required status, or no matches found.

Keep chat answers short and readable.

Use the HTML report for detailed evidence instead of dumping raw measure lists into chat.

Ask follow-up questions only when required data is missing.

Custom prompt card for the setup guide. It avoids UI screenshots and keeps the tool names readable for technical reviewers.

Prompt examples

Real prompts from the setup guide, mapped to agent behavior.

These examples are taken from Part 1 of the MCP setup guide. The important part is not the wording itself, but the routing: the agent should call the platform tool and return evidence.

Classification and duties

Agent prompt

check_trade_compliance

“Check CN code 8504403000 for an EU trade review with China. I need the duty rate, measures, and any conditions.”

Expected result

Measures, duty rates, conditions, warnings, and legal basis for review.

Product description

Agent prompt

search_cn_codes

“Find the CN code for hydraulic pump components — I have a product description, not a number.”

Expected result

Candidate CN codes with hierarchy context before the user runs a full check.

Sanctions screening

Agent prompt

check_sanctions

“Run a sanctions check for CN 8471300000 from Russia. Show direct and group-level matches separately.”

Expected result

Direct matches and broader group-level matches separated for review.

Full compliance check

Agent prompt

check_trade_compliance

“Generate a compliance report for 8702109090 · Turkey · date 2026-03-15. I need the HTML file.”

Expected result

Full compliance result with measures, warnings, source context, and report output when available.

Classification overview

Agent prompt

get_cn_description

“What does CN code 0302120010 cover? I only need the classification hierarchy, no measures.”

Expected result

CN hierarchy and selected code description before any country-specific compliance check.

User control

The user asks normal questions; the agent handles routing and evidence collection.

Organization access

API/MCP credentials are scoped to the workspace and can be reviewed or rotated.

Evidence output

For detailed answers, the agent links to a generated HTML report instead of relying on chat text.