Censys MCP integration for AI agents.
Connect AI agents to Censys through 3 structured actions, including get certificate, get host, and get web property. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Censys integration exposes
The Censys Agent App exposes 3 provider-backed actions for security and data work. Its current contract lets an authorized agent get one censys global data certificate asset by certificate id, get one censys global data host asset by host id, and get one censys global data web property asset by web property id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Censys account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Censys capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_certificateREADGet one Censys Global Data certificate asset by certificate ID.
INPUTS: certificate_id
get_hostREADGet one Censys Global Data host asset by host ID.
INPUTS: host_id / at_time
get_web_propertyREADGet one Censys Global Data web property asset by web property ID.
INPUTS: webproperty_id / at_time
INPUT CONTRACTS
Know what the action needs before it runs.
get_certificate
certificate_idOPTIONAL- Censys certificate ID to retrieve.
get_host
host_idREQUIRED- Censys host ID to retrieve.
at_timeOPTIONAL- RFC 3339 timestamp for retrieving a historical host view.
get_web_property
webproperty_idREQUIRED- Censys web property ID in hostname:port format, such as platform.censys.io:443.
at_timeOPTIONAL- RFC 3339 timestamp for retrieving a historical web property view.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Certificate
Get one Censys Global Data certificate asset by certificate ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_certificateVerify with Get Host
Get one Censys Global Data host asset by host ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_hostSAFETY BOUNDARY
Operate Censys with explicit limits
- Authorize Censys with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Censys data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Censys rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Censys task completed successfully.
CONNECTION MODEL
API key
Censys Personal Access Token sent with the Authorization Bearer header. Create or view tokens in the Censys Platform account settings: https://platform.censys.io.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Censys.