WitFoo
WitFoo Analytics and WitFoo Reporter run on your organisation's own appliance. This connector lets an analyst ask that appliance questions in plain language, instead of exporting data. Answers come from WitFoo's correlated record: work units, artifacts, hosts, accounts, observations, compliance readiness and reports. Every record links back to its evidence, so the analyst can check the work. What you can do - Find and triage work units, and see the hosts, accounts and observations behind them. - Look up what WitFoo knows about an IP address, host or user. - Read the latest executive summary, compliance readiness and appliance health. - With permission, add notes, assign work, and manage tasks, playbooks, observations and work collections. Reading and changing data are separate tools, and every tool is labelled. An app can use the tools that make changes only if the organisation's administrator allows it and the user ticks "Also let this app make changes for you" when approving the app. Both are off by default. Scoped to the person who asked Each user signs in to their own appliance with their own WitFoo account. The app acts with that user's WitFoo permissions and reaches only their organisation's data. Users and administrators can revoke an app at any time. Where the data goes The connection runs through WitFoo's relay, which the appliance's administrator switches on. The relay is fronted by Cloudflare, which can see traffic in transit. WitFoo's relay stores no request or response content, only request details such as time, path and status. The result of each tool call goes to the AI assistant you are using, under that provider's terms. Before you connect You need a WitFoo Analytics or Reporter appliance on release 1.2.1 or later with WFA 2.5.5 or later, with the AI connector and the relay enabled by your administrator, and a WitFoo account that holds the mcp:connect permission. Setup is described at docs.witfoo.com.
Where it stands
Tools
add_work_ collection_ members assign_incident create_dashboard create_incident_ note create_observation create_playbook create_responder_ job create_task create_work_ collection delete_observation delete_playbook delete_work_ collection execute_playbook execute_responder_ job generate_report get_audit_ compliance get_audit_ remediation get_business_ settings get_compliance_ status get_cost_ savings get_executive_ summary get_incident_ audit_ log get_incident_ details get_incident_ facets get_incident_ linked get_incident_ observation_ matches get_incident_ suspicion_ details get_playbook get_playbook_ executions get_responder_ job get_system_ health get_tool_ effectiveness get_work_ collection_ details list_dashboards list_incident_ assignments list_incident_ notes list_playbooks list_responder_ jobs list_tasks list_work_ collections mcp_info remove_work_ collection_ members search_artifacts search_audit_ findings search_chat_ messages search_chat_ rooms search_directory search_incidents search_nodes search_observations search_users send_chat_ message unassign_incident update_business_ settings update_dashboard update_incident_ status update_observation update_task_ status