6sense

No. 6sense states that the current MCP release supports read-only retrieval scenarios, and the two listed tools are an agent and a market-research tool. Nothing in the published surface creates, updates or deletes 6sense data, so the risk this connector carries is about what it exposes rather than what it changes.

Whatever your own 6sense account can see. 6sense describes the integration as retrieving relevant 6sense data and insights using natural-language queries, based on data available to you in your account. Its documented scenarios cover account insights, activity and engagement signals, 6QA trend analysis, keyword trends and campaign performance.

An administrator. 6sense documents AI and MCP settings under Settings then AI and MCP, where admins configure how AI and MCP capabilities are enabled and governed across the organization. 6sense advises reviewing internal policies on AI usage, customer data, privacy, legal review and third-party integrations before adjusting them.

Getting answers without opening the 6sense app. 6sense names preparing for account research or meetings, reviewing account activity and engagement signals, analyzing trends across accounts or keywords, and evaluating campaign performance. It is most useful when you are already working inside an AI assistant and want 6sense context in the same workflow.

Anthropic's directory lists revvy_agent and revvy_market_research. The names match 6sense's RevvyAI product family, which its documentation covers across Revenue Marketing and Sales Intelligence. 6sense's own article describes capabilities and example queries rather than enumerating tools, so no per-tool behaviour is stated on this page.

No, it uses OAuth. We confirmed the server returns HTTP 401 with a Bearer challenge and publishes RFC 9728 metadata advertising a single scope, mcp:use, with an authorization server under auth.6sense.com. The descriptor also points at api.6sense.com/docs as its resource documentation.