QoreNext Trade Screening MCP
Server Name:
QoreNext Trade Screening MCP
Description:
Real-time trade screening intelligence for Claude and other AI clients — screen entities against trade screening and restricted-party information through an MCP-compatible interface, enabling faster compliance research and reducing manual screening effort.
GitHub Repository:
https://github.com/QoreNext/qorenext-tradescreening-mcp
MCP Endpoint:
https://mcp.qorenext.com/tradescreening
Category:
Compliance / Trade Screening / Risk & Data Intelligence / Productivity
Features
submit_sanctions_screening
Submit entities for sanctions screening against USA sanctions lists (OFAC, MEU, EntityList, etc.).
Required per entity: entityEnglishName or entityNativeName (at least one)
Optional: country, address
submit_trade_screening
Submit a company for trade screening due-diligence: denied/restricted-party list checks, red-flag keyword analysis, risk assessment, and negative-news findings.
Required: address, website, and companyEnglishName or companyNativeName (at least one)
Optional: parentEntityEnglishName, parentEntityWebsite
get_trade_screening_status
Poll a trade screening request for status and the full due-diligence report.
Parameter: request_id (int) — the NativeId returned by submit_trade_screening
Status values: Pending · Processing · Completed · Failed
Use Cases
The QoreNext Trade Screening MCP enables AI assistants and MCP-compatible applications to interact with trade screening capabilities through the Model Context Protocol.
It can be used to support compliance research, entity screening, risk assessment, and trade-related due diligence workflows.
Compatibility
MCP-compatible AI clients and applications.
Server Type
Remote MCP Server
Transport / Connection
Remote MCP endpoint:
https://mcp.qorenext.com/tradescreening
Documentation
GitHub repository:
https://github.com/QoreNext/qorenext-tradescreening-mcp
Please review and consider listing the QoreNext Trade Screening MCP in the MCP.so directory.
Thank you.
QoreNext Trade Screening MCP
Server Name:
QoreNext Trade Screening MCP
Description:
Real-time trade screening intelligence for Claude and other AI clients — screen entities against trade screening and restricted-party information through an MCP-compatible interface, enabling faster compliance research and reducing manual screening effort.
GitHub Repository:
https://github.com/QoreNext/qorenext-tradescreening-mcp
MCP Endpoint:
https://mcp.qorenext.com/tradescreening
Category:
Compliance / Trade Screening / Risk & Data Intelligence / Productivity
Features
submit_sanctions_screening
Submit entities for sanctions screening against USA sanctions lists (OFAC, MEU, EntityList, etc.).
Required per entity: entityEnglishName or entityNativeName (at least one)
Optional: country, address
submit_trade_screening
Submit a company for trade screening due-diligence: denied/restricted-party list checks, red-flag keyword analysis, risk assessment, and negative-news findings.
Required: address, website, and companyEnglishName or companyNativeName (at least one)
Optional: parentEntityEnglishName, parentEntityWebsite
get_trade_screening_status
Poll a trade screening request for status and the full due-diligence report.
Parameter: request_id (int) — the NativeId returned by submit_trade_screening
Status values: Pending · Processing · Completed · Failed
Use Cases
The QoreNext Trade Screening MCP enables AI assistants and MCP-compatible applications to interact with trade screening capabilities through the Model Context Protocol.
It can be used to support compliance research, entity screening, risk assessment, and trade-related due diligence workflows.
Compatibility
MCP-compatible AI clients and applications.
Server Type
Remote MCP Server
Transport / Connection
Remote MCP endpoint:
https://mcp.qorenext.com/tradescreening
Documentation
GitHub repository:
https://github.com/QoreNext/qorenext-tradescreening-mcp
Please review and consider listing the QoreNext Trade Screening MCP in the MCP.so directory.
Thank you.