ASM MCP Server

Use the ASM Model Context Protocol (MCP) Server to give your AI agents and workflows secure, governed, and direct access to your ASM inventory, empowering you to explore and understand your attack surface at machine speed.

MCP is an open standard designed by Anthropic to help AI agents leverage trusted external data and tools.

The MCP Server is a service hosted by Censys. The server can be used by any ASM user with access to the API.

Prerequisites

  • Obtain your API key. It is located at the top of the Integrations page in the ASM web console.
  • Obtain your workspace ID. This is shown in the URL after edit/ on the Manage Workspace page in the ASM web console.
    • To access the Manage Workspace page, click the gear icon next to your workspace name in the workspace dropdown menu.

    • The ASM MCP Server currently only supports connecting to one workspace per organization.

Integrate with the Censys hosted ASM MCP Server

Use the instructions below to integrate the Censys hosted ASM MCP Server with your tools. Note that the following are just some examples; the ASM MCP Server can be incorporated into many different applications.

Add the following to your Cursor MCP configuration file (~/.cursor/mcp.json). You can access this file in the UI by going to Cursor Settings > Tools & Integrations and clicking + New MCP Server.

{
  "mcpServers": {
    "censys-asm-mcp-server": {
      "url": "https://mcp.asm.censys.io/asm/mcp/",
      "headers": {
        "x-censys-workspace-id": "your-workspace-id",
        "Authorization": "Bearer your-asm-api-token"
      }
    }
  }
}

After configuring your integration, test it by prompting your agent with a question like "How many domains are in my attack surface?"

The output may depend on your specific configuration, but your agent should use the search_assets tool to retrieve information about your attack surface.

Example use cases

The ASM MCP Server currently works best for retrieving and summarizing information about assets in your inventory, aggregating information about your inventory, and examining specific components of your attack surface to surface risks and other issues.

The following prompts are some useful examples.

  • Are any assets in my inventory vulnerable to CVE-2025-54309?
  • Which cloud vendors are present in my attack surface?
  • Which of my assets has the highest number of critical vulnerabilities?
  • Which critical risk is most prevalent in my attack surface?