How to Use the eCompliance MCP in LlamaIndex

Q: How do I load eCompliance tools into LlamaIndex?

Install llama-index-tools-mcp. Initialize a BasicMCPClient with your URL, wrap it in an McpToolSpec, and call await mcptoolspec.totoollistasync() to feed your agent.

Q: Can LlamaIndex query eCompliance corrective actions directly?

Yes. Your agent can call listcorrectiveactions in real-time to answer user queries about pending safety fixes without needing to pre-index the entire database.

Q: Does the agent know the current account limits?

It can check them. The agent runs getecompliancemetadata to see your API rate limits and account status before it decides to pull massive lists of historical incidents.

Q: What is the security model for incident data in the MCP Server?

The getincidentdetails tool transmits sensitive injury descriptions and investigation notes. The Vinkius zero-trust architecture ensures this data only passes through an ephemeral sandbox directly to your client. No logs are kept.

Index your eCompliance MCP Server safety records into LlamaIndex. Query live inspection data against your internal knowledge base.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect eCompliance MCP to LlamaIndex

Create your Vinkius account to connect eCompliance to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup eCompliance with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Vectorize safety audits with LlamaIndex

`get_inspection_details` feeds your active safety findings directly into a LlamaIndex vector store. Your RAG application ingests these raw compliance checks alongside your written safety manuals. When a manager asks about fall protection compliance, the agent doesn't guess. It queries the index, retrieves the actual failed inspections from last week, and grounds its answer in hard data. You get answers based on reality.

Search incidents by semantic meaning

The `search_safety_incidents` tool lets your agent pull historical accident reports based on text keywords. LlamaIndex takes those records and embeds them into your searchable knowledge graph. You stop relying on exact keyword matches. The system cross-references the fresh outputs from `list_latest_incidents` with years of indexed safety data. It spots patterns in equipment failures before someone gets seriously hurt.

Ground answers in real employee records

`list_site_employees` pulls the current active roster for any given site. Your LlamaIndex `FunctionAgent` uses this tool to verify who was actually present during a specific event. The agent combines this roster data with the output from `list_corrective_actions`. It maps overdue safety fixes to specific personnel, giving you a completely factual breakdown of where the bottlenecks are.

Setup guide

Set up eCompliance MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all eCompliance MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to eCompliance tools.",
)
response = await agent.run("List recent eCompliance data")

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by eCompliance. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect eCompliance now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about eCompliance MCP in LlamaIndex

Install `llama-index-tools-mcp`. Initialize a `BasicMCPClient` with your URL, wrap it in an `McpToolSpec`, and call `await mcp_tool_spec.to_tool_list_async()` to feed your agent.

Yes. Your agent can call `list_corrective_actions` in real-time to answer user queries about pending safety fixes without needing to pre-index the entire database.

You set up a unified query engine. The system routes conceptual questions to your document index and real-time status questions to the eCompliance tools.

It can check them. The agent runs `get_ecompliance_metadata` to see your API rate limits and account status before it decides to pull massive lists of historical incidents.

The `get_incident_details` tool transmits sensitive injury descriptions and investigation notes. The Vinkius zero-trust architecture ensures this data only passes through an ephemeral sandbox directly to your client. No logs are kept.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript