Adaption
Import, adapt and expand training datasets, then launch AutoScientist fine-tuning runs from an AI agent.
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
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
update_finding can close security findings. Any user whose role allows it in Atlas can do so from chat after confirming.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.
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.
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.
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.
POST initialize against https://api.esentire.com/mcp/rpc (2026-11-18): HTTP 401 with WWW-Authenticate naming https://api.esentire.com/.well-known/oauth-protected-resource, which returned HTTP 200 with the four OpenID Connect scopes. The RFC 8414 document at https://api.esentire.com/.well-known/oauth-authorization-server returned HTTP 200 naming https://esentire.okta.com as issuer. The path-insert descriptor form returned HTTP 403. · retrieved 2026-11-18docs/marketing/data/anthropic-directory-2026-11-17.json. Source for the partner tier, the 2026-09-18 listing date, the endpoint and the 19 tool names. · retrieved 2026-11-17Connect atlasFindings once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.