How to Use the Censys MCP in CrewAI

Q: How does CrewAI handle large search results from Censys?

Tools like searchhosts support pagination using cursors. Your agents can query successive pages of host data autonomously, processing batches of IPs without overloading their context windows.

Q: Can my crew check API quota limits before running a scan?

Yes, your lead agent can run getaccountinfo at the start of a task. Based on the remaining quota, the crew can decide to run a deep scan or scale back their search queries.

Deploy specialized agent teams to hunt threats and analyze attack surfaces using CrewAI and Censys.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Censys MCP to CrewAI

Create your Vinkius account to connect Censys 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 Censys with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous Recon Teams with CrewAI and Censys

This MCP Server lets your research agent scan public networks for exposed services and active protocols using `search_hosts`. The agent passes these raw IP addresses to an analyst agent to inspect the configuration details. This multi-agent setup uses shared memory to build a complete picture of your exposure. One agent finds the targets, while another determines if the open ports pose an immediate security risk.

Deep Certificate Audits via CrewAI MCP Server

`get_certificate` retrieves complete parsed certificate data including subject names, issuers, and validity windows. Your certificate auditor agent can inspect these fields to verify that your TLS configurations comply with internal standards. The auditor can then hand off the findings to a domain-mapping agent using `get_certificate_hosts`. Together, they uncover hidden subdomains and associated hosts sharing the same credentials.

Compare Host Configurations Dynamically

`view_host_diff` compares two distinct hosts to identify differences in their active services, ports, and operating systems. A monitoring agent can run this comparison daily against your known baseline servers. If any discrepancies show up, `get_host_history` is called to trace when the services changed. The crew then compiles a unified incident report and escalates it to your security team.

Setup guide

Set up Censys 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 Censys tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Censys 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="Censys Analyst",
        goal="Access and analyze Censys data via MCP.",
        backstory="Expert analyst with direct Censys access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Censys 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 Censys. 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 Censys 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 Censys MCP in CrewAI

You can pass your Vinkius HTTP URL directly into the server configuration list when defining your agents. For more control, use the HTTP server class from the CrewAI package to filter which tools each agent can access.

Yes, you can restrict tool access so your recon agent only uses `search_hosts` while your compliance agent is limited to `get_certificate`. This keeps your agent roles focused and efficient.

Tools like `search_hosts` support pagination using cursors. Your agents can query successive pages of host data autonomously, processing batches of IPs without overloading their context windows.

Yes, your lead agent can run `get_account_info` at the start of a task. Based on the remaining quota, the crew can decide to run a deep scan or scale back their search queries.

Vinkius runs the server in an ephemeral sandbox, meaning your scanned host histories and IP lists are never stored. Your credentials and query parameters are kept strictly within your secure execution 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