Censys MCP connector
The Censys connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and other AI clients look up hosts, certificates, web properties and DNS records in Censys through one governed Elaichi endpoint, with every call logged under the person who made it.
- Connects with an API key
- Free 14-day trial
- No credit card
Claude
Elaichi connected
Show new Censys hosts added in the last week.
Working in Censys with Elaichi
-
Get single Censys host by ID
-
-
Governance
/
Audit log
Last 24 hours
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
ChatGPT · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Censys to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Censys MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Censys MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Censys MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Censys MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Censys MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Censys to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Censys through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Censys is logged.
-
Security operations
Check what an IP is exposing right now
Ask for a Censys host by its address and get back the open services, software and location, then pull its service history to see what changed and when.
-
Threat intelligence
Chase a suspicious certificate across the internet
Look up a certificate in Censys by fingerprint, read the raw details, and find every host presenting it so a single indicator turns into a full picture.
-
Attack surface management
Build a running inventory of external assets
Run Censys searches for your organization's names and ranges, aggregate the results by service or location, and list the web properties that belong to you.
-
Incident response
Reconstruct a host's timeline during an incident
Pull the event history for a Censys host to see when services appeared, disappeared or changed, and enrich the record with everything Censys knows about it.
-
Vulnerability management
Confirm a fix by rescanning the host
After a patch or a firewall change, trigger a Censys rescan and check the scan result so the ticket closes on evidence rather than assumption.
-
IT and infrastructure
Trace a domain to the addresses behind it
Resolve a name to its IP ranges in Censys, or work backward from an address to the names pointing at it, to untangle what is really serving a site.
Try asking
- “Show new Censys hosts added in the last week.”
- “Which Censys certificates expire in the next 30 days?”
- “List web properties on our Censys perimeter by team.”
What connecting Censys gets you
6 screens from Elaichi, each doing one job for your Censys account.
Ask Elaichi to work across your apps.
Show new Censys hosts added in the last week.
Which Censys certificates expire in the next 30 days?
List web properties on our Censys perimeter by team.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about hosts, get answers from Censys.
Type a question in plain language and read live host and certificate records.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Censys works in Claude, ChatGPT, Cursor and Microsoft Copilot.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiToolsTool catalog
47 Censys tools ready to call.
Hosts, certificates and web properties are covered with no custom code to write.
ElaichiToolboxesToolboxes
Every team gets its own Censys toolbox.
Curate one toolbox per team so each sees only the Censys tools it needs.
ElaichiConnectionsShared connections
Share a Censys account, never the key.
Teammates query hosts and certificates through a connection without ever seeing a credential.
ElaichiAudit logAudit log
Every Censys call is on the record.
When, who, what happened, type and resource, appended for each host and certificate lookup.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Censys digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch hosts
Censys
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Censys
Queued
Automations
A schedule turns Censys hosts into action.
Fetch hosts, group them, draft a digest, get approval, post back to Censys.
Censys health
Refreshed 4 minutes ago · every 15 minutes · from the hosts collection
Hosts
1,284 ↓ 12%
Certificates
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Hosts created
Last 14 days
By team
Share of activity
Security operations 34%
Threat intel 27%
Attack surface 21%
Vulnerability management 18%
Collections and dashboards
Censys health numbers arrive without being asked.
Four metrics, 14 days of records created and a team breakdown, computed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Censys
All three can connect Censys to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Censys tools | Allow or restrict single Censys tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Censys call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Censys tools for your AI agents
47 tools are ready to call through Elaichi's MCP endpoint the moment you connect Censys, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Censys to Claude?
In Elaichi, choose Censys and paste in a Censys API key from your Censys account; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the Elaichi endpoint https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks, and Censys is available in your conversations.
Does Censys work with ChatGPT and Cursor as well as Claude?
Yes. Once Censys is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Censys once and every client you use picks it up.
What can an AI agent actually do with my Censys data?
An agent connected to Censys can look up hosts by IP and report their open services, pull a host's event and service history, fetch certificates and their raw details, list your web properties, run and aggregate searches, resolve names to IP ranges and back, and trigger a rescan of a host. Because Censys offers many actions, the agent searches for the right one as you ask, so short concrete requests such as "show the certificate history for this host" work better than long paragraphs.
Does connecting Censys give the AI access to my whole Censys organization?
The AI sees exactly what the Censys account behind the API key can see, and nothing more; if that account cannot view certain hosts or run certain searches, neither can the agent. Elaichi can narrow that access further, for example by removing the ability to rescan, but it can never widen what Censys itself allows. Every request still runs under the Elaichi user who made it, so the audit log names the person, not just the key.
Can I stop an agent from triggering rescans or changing things in Censys?
Yes. Restrictions in Elaichi work action by action, so you can keep Censys read-only by restricting rescans while leaving host, certificate and search lookups available. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.
What happens to a Censys connection when someone leaves?
Offboarding a person in Elaichi ends their access to Censys and every other connected application at once, without touching the Censys API key. A Censys connection shared with a team keeps working for everyone still on it. If you want Censys gone entirely, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Censys MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Censys is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Censys?
Yes. Both let Claude, ChatGPT or Cursor use Censys. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Censys call.
How is Elaichi different from Composio for Censys?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Censys: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Censys in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
- ChatGPT
- Claude
- Cursor
- Microsoft Copilot