Can I see if a user has finished their background check?

Yes! Use the `get_screening_details` tool with the screening ID. The agent will return the current status and the final result of the check.

How do I find out who accessed a specific verification record?

Use the `list_cleared_audit_logs` tool. Your agent will fetch the account's security logs, allowing you to audit access to sensitive personal information.

Where do I find my Cleared API Key?

Log in to your Cleared (ClearedIn) Admin Portal and navigate to the **Integrations** section. You can generate and copy your API key from there.

Cleared (ClearedIn) MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: Cleared (ClearedIn)
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to Cleared (ClearedIn) through Vinkius, pass the Edge URL in the `mcps` parameter and every Cleared (ClearedIn) tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Cleared (ClearedIn) Specialist",
    goal="Help users interact with Cleared (ClearedIn) effectively",
    backstory=(
        "You are an expert at leveraging Cleared (ClearedIn) tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Cleared (ClearedIn) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Cleared (ClearedIn) MCP Server

Connect your Cleared (ClearedIn) account to any AI agent and take full control of your identity verification and screening workflows through natural conversation. Streamline how you verify users and maintain trust natively.

When paired with CrewAI, Cleared (ClearedIn) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Cleared (ClearedIn) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Verification Oversight — List and retrieve details for all identity verification requests and their status natively
Screening Intelligence — Access and monitor background screening requests and retrieve detailed results flawlessly
Digital Signatures — List all digital signature requests and track their completion status securely
Audit Logistics — Access security audit logs to track who accessed sensitive data and when flawlessly
Identity Management — Retrieve core account and user metadata directly within your workspace flawlessly
Trust Logistics — Monitor the lifecycle of verification sessions from 'Pending' to 'Verified' or 'Rejected' in real-time

The Cleared (ClearedIn) MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Cleared (ClearedIn) to CrewAI via MCP

Follow these steps to integrate the Cleared (ClearedIn) MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 8 tools from Cleared (ClearedIn)

Why Use CrewAI with the Cleared (ClearedIn) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Cleared (ClearedIn) through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Cleared (ClearedIn) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Cleared (ClearedIn) MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Cleared (ClearedIn) for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Cleared (ClearedIn), analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Cleared (ClearedIn) tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Cleared (ClearedIn) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Cleared (ClearedIn) MCP Tools for CrewAI (8)

These 8 tools become available when you connect Cleared (ClearedIn) to CrewAI via MCP:

get_cleared_account_info

Retrieve core account and user metadata

get_screening_details

Get detailed results for a specific screening

get_signature_details

Get detailed status for a specific signature request

get_verification_details

Get detailed information for a specific verification

list_background_screenings

List all background screening requests

list_cleared_audit_logs

List security audit logs for the account

list_digital_signatures

List all digital signature requests

list_identity_verifications

List all identity verification requests

Example Prompts for Cleared (ClearedIn) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Cleared (ClearedIn) immediately.

"List the last 5 identity verifications in Cleared."

"Show me the results for screening ID 'scr_12345'."

"What is the status of the signature request for 'Employment Contract'?"

Troubleshooting Cleared (ClearedIn) MCP Server with CrewAI

Common issues when connecting Cleared (ClearedIn) to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Cleared (ClearedIn) + CrewAI FAQ

Common questions about integrating Cleared (ClearedIn) MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.