WitnessAI
MCP authentication and authorization: OAuth for AI agents (2026-09-28) commercialThe section your link pointed to isn't on WitnessAI's page any more, so we've brought you to the top.
WitnessAI sits in the network path and monitors, controls and protects employee, application and agent AI activity.
Summary
WitnessAI is a commercial AI security tool that monitors, controls, and protects employee, application, and agent AI activity as it passes through the network path. It operates as a service and is designed for governance of AI usage, fitting into the ai-governance category. Its documentation positions it alongside other network visibility tools. The product was launched in 2023.
WitnessAI sits in the network path and monitors, controls and protects employee, application and agent AI activity.
How WitnessAI helps
Which AI tools and MCP connections are actually in use across the network, including ones nobody registered?
scans network-level traffic for AI application signatures and MCP connections, cataloging thousands of applications — including native apps like Windows Copilot and Microsoft 365 — and ties each captured action back to the human identity behind it, all without installing endpoint clients or browser extensions
Which employees or agents sent sensitive data to an external model, and what did the model send back?
keeps auditable records of prompts, uploads, and responses routed through the network path, showing who sent what to which model and what came back, usable as evidence in AI risk reviews under frameworks such as DORA and the EU AI Act
Which agent tool calls should never have been allowed to run?
checks agent and tool-call activity against an approved-tool and MCP allow-list before execution, blocking unauthorized calls and keeping an audit trail of governed activity across more than 100 LLM types
Can a sensitive value like a customer's SSN leave the building through a prompt?
tokenizes classified sensitive values before a prompt leaves the enterprise, then restores the original value only in responses to users authorized for policy-enforced detokenization
Would this query have been flagged if it were phrased differently?
classifies conversational intent and context with machine learning rather than keyword or regex matching, so paraphrased or indirect attempts to expose sensitive data or violate policy still surface, each with a confidence score adjusted by contextual signals
Should a given query have gone to an external model at all?
routes queries carrying classified sensitive intent, such as non-public drug research or financial data, away from external models to approved internal ones automatically
Languages
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for WitnessAI, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail WitnessAI puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
witness.ai, every changeWitnessAI's home page and 18 more pages as they looked each month from May 2024 to October 2026: 101 renders, 19 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
2 entries
No entries match these filters.
- September 20262
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.