mcp

This MCP server provides an experimental, stdio-based MCP implementation for creating agentic integrations with Trulioo’s KYB products. The server is built on .NET 8 and exposes an MCP protocol interface over standard input/output. Once running, clients can communicate with the MCP endpoint to register, configure, and manage agents that interact with Trulioo’s KYB services. The server handles translation between MCP messages and Trulioo KYB operations, enabling automated workflows such as identity verification steps, risk checks, and consent-driven data retrieval via the MCP protocol. To use it, start the server and connect an MCP client to it; implement or reuse existing MCP client tooling to send the standard MCP commands (e.g., initialize, negotiate capabilities, create or update agents, and execute KYB tasks). As you send requests, monitor the server’s standard output for logging and troubleshooting information. If you have a client toolchain built for other MCP servers, you may adapt its request/response payloads to match Trulioo’s KYB MCP implementation used by this server.

Prerequisites:

• .NET 8.0 SDK or higher
• A compatible operating system (Windows, macOS, or Linux)
• Basic understanding of the MCP protocol and agent-based architectures

Installation steps:

1. Install .NET 8 SDK

   • Windows: download from https://dotnet.microsoft.com/download/dotnet/8.0
   • macOS/Linux: use your package manager or install from the official site

2. Clone the repository

   • git clone https://github.com/your-org/trulioo-mcp-server.git
   • cd trulioo-mcp-server

3. Restore and build

   • dotnet restore
   • dotnet build -c Release

4. Run the MCP server

   • dotnet src/Trulioo.MCPServerForKYB.dll

5. (Optional) Configure environment variables or runtime options as needed in your deployment environment. For example, you can set ASPNETCORE_ENVIRONMENT to Production to optimize logging and behavior in production deployments.

Tips and common considerations:

• Ensure the running environment has .NET 8 SDK/runtime installed and accessible in PATH.
• If you deploy in containers, map standard input/output correctly since this is an stdio-based MCP server.
• Set ASPNETCORE_ENVIRONMENT to match your deployment (Development/Production) for appropriate logging levels.
• Monitor server logs for MCP negotiation, capability advertisement, and KYB task execution results to diagnose integration issues.
• If you encounter DLL path issues, confirm the built output location and that the Trulioo.MCPServerForKYB.dll file exists at the specified path.
• Consider adding health checks or readiness probes in your orchestration layer to verify the MCP server is accepting connections.