atlasFindings

Search eSentire Atlas findings, assets and tickets from Claude.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the atlasFindings connector does

The atlasFindings MCP server connects Claude to eSentire Atlas, the platform behind eSentire's managed detection and response service. Customers can search security findings, look up assets, review vulnerabilities and missing patches, and work support tickets in plain language. Three tools change data, and eSentire says each asks for confirmation. Sign-in is Okta OAuth.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

atlasFindings tools (19)

  • create_ticket
  • find_org_list
  • get_asset
  • get_finding
  • get_organization
  • get_organization_tree
  • get_signal_data
  • get_ticket
  • get_ticket_comments
  • get_ticket_options
  • get_vulnerability
  • list_assets
  • list_findings
  • list_missing_patches
  • list_tickets
  • list_vulnerabilities
  • update_finding
  • update_ticket
  • verify_child_customer

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Customers only. There is no trial or public data; the connector needs an eSentire account with API access.
  • Closing a finding is in reach. update_finding can close security findings. Any user whose role allows it in Atlas can do so from chat after confirming.
  • Unfinished vendor page. eSentire's connector page carried placeholder text in its setup and privacy sections when we read it on 2026-11-18, and it names two different hosting regions (us-west-2 and eu-west-1) without reconciling them.
  • Four undocumented tools. The organization tools in the directory listing have no vendor description.
  • Identity-only consent. The OAuth scopes carry no read or write split; limits come from Atlas role-based access.
  • Not advice. Findings and vulnerability data describe your environment; remediation decisions stay with your team and eSentire's analysts.
  • We read no live schemas. We did not authenticate or call any tool.

Frequently asked questions

Who can use the eSentire Atlas MCP connector?

Existing eSentire customers whose user has API access enabled. eSentire's connector page sends non-customers to sales and lists three prerequisites: an active customer account, API access for the user, and Claude Desktop or Claude Code. What each user can see and change follows their eSentire role-based permissions, because the access token is scoped to the person who signed in through Okta.

Can Claude change findings or tickets without my approval?

No, according to eSentire. Its FAQ says the write tools require confirmation, and its tool list says the three that change data always prompt before acting. Those three can open a support case, update a ticket's status or comments, and close a finding or change its status. We could not inspect the live annotations, so this is eSentire's statement rather than something we observed.

What happens when a user's Okta access changes?

The connector follows it on the next request. eSentire's FAQ says changes made in Okta are reflected immediately on the next call, so removing a user's access or changing their role takes effect without reconnecting. Because tokens are scoped to the authenticated user, the connector never reaches beyond what that person could already see or do in Atlas under their own permissions.

How is the MCP connector different from Claude inside Atlas?

They run in opposite directions. eSentire's FAQ says Claude inside Atlas performs investigations automatically as part of the eSentire service. The MCP connector instead lets your own team query and act on Atlas data from your own Claude environment, in chat or Claude Code. You choose the questions, and any write still needs confirmation under your own eSentire permissions.

Sources

Use it in an agent

Put atlasFindings to work.

Connect atlasFindings once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.