How to Use the Cleared (ClearedIn) MCP in CrewAI

Q: How do I share Cleared (ClearedIn) tools across multiple CrewAI agents?

You pass the server URL to the mcps parameter when defining your Crew. This makes tools like listbackgroundscreenings available to all agents in your crew, allowing them to collaborate on verification tasks.

Q: How do I limit which CrewAI agents can access Cleared (ClearedIn) audit logs?

You can use toolfilter in your CrewAI setup to restrict sensitive tools like listclearedauditlogs. This ensures your MCP Server only exposes security logs to authorized agents.

Q: How does the crew handle account metadata?

Your lead agent can run getclearedaccountinfo at the start of a session. This metadata is stored in CrewAI's shared memory, so all agents know the account context before executing tasks.

Q: How is my screening data protected?

All background check details fetched via getscreeningdetails are transmitted through encrypted channels. The MCP Server acts as an ephemeral bridge, ensuring no screening data is cached or stored outside your CrewAI environment.

Deploy autonomous agent teams to manage Cleared (ClearedIn) screenings and verifications using CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Cleared (ClearedIn) MCP to CrewAI

Create your Vinkius account to connect Cleared (ClearedIn) to CrewAI 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 Cleared (ClearedIn) with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinate background screenings with CrewAI teams

Managing background checks manually takes hours. With this MCP Server, you can assign a Researcher Agent to monitor screenings using `list_background_screenings` while an Analyst Agent processes the results. When a report is ready, the Researcher passes the ID to the Analyst, who calls `get_screening_details` to verify the findings. The crew handles the entire pipeline autonomously.

Verify identities autonomously using this MCP Server

Let your agents handle compliance checks in the background. A verification agent uses `list_identity_verifications` to watch for new user sign-ups. The agent then triggers `get_verification_details` to inspect the uploaded documents. If everything matches, it updates your database; otherwise, it escalates the case to a human moderator.

Manage digital signature flows with CrewAI agents

Keep your contract pipeline moving without manual follow-ups. A signing coordinator agent checks pending documents using `list_digital_signatures` and flags outstanding files. The coordinator agent uses `get_signature_details` to see who hasn't signed yet. It then tasks a communication agent to draft and send a polite reminder to the signer.

Setup guide

Set up Cleared (ClearedIn) MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Cleared (ClearedIn) tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Cleared (ClearedIn) Analyst",
    goal="Access and analyze Cleared (ClearedIn) data via MCP.",
    backstory="Expert analyst with direct Cleared (ClearedIn) access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Cleared (ClearedIn) transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Cleared (ClearedIn) Analyst",
        goal="Access and analyze Cleared (ClearedIn) data via MCP.",
        backstory="Expert analyst with direct Cleared (ClearedIn) access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Cleared (ClearedIn) transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

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 Cleared (ClearedIn). 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 Cleared (ClearedIn) 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 Cleared (ClearedIn) MCP in CrewAI

You pass the server URL to the `mcps` parameter when defining your Crew. This makes tools like `list_background_screenings` available to all agents in your crew, allowing them to collaborate on verification tasks.

Yes, you can design a hierarchical crew where a worker agent calls `get_verification_details` and, upon detecting a failure, passes the task to a manager agent for manual review.

You can use `tool_filter` in your CrewAI setup to restrict sensitive tools like `list_cleared_audit_logs`. This ensures your MCP Server only exposes security logs to authorized agents.

Your lead agent can run `get_cleared_account_info` at the start of a session. This metadata is stored in CrewAI's shared memory, so all agents know the account context before executing tasks.

All background check details fetched via `get_screening_details` are transmitted through encrypted channels. The MCP Server acts as an ephemeral bridge, ensuring no screening data is cached or stored outside your CrewAI environment.

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