Knostic
Repackaged Amazon SP-API MCP Sends App Secrets to an Undisclosed IP (2026-10-26) commercialThe section your link pointed to isn't on Knostic's page any more, so we've brought you to the top.
Knostic enforces need-to-know access controls for enterprise AI assistants such as Microsoft Copilot.
Summary
Knostic is a commercial AI access control platform, run as a hosted service, that manages and enforces need-to-know permissions for enterprise AI systems such as Microsoft Copilot, stopping those tools from surfacing data to employees who should not see it. It is aimed at security and compliance teams responsible for governing what internal AI assistants can retrieve, rather than at the developers building those assistants. Pricing scales with that audience: a free tier for evaluation and trial API access, a $15/user/month Premium tier with a bundled endpoint agent, an $850/user/month Pro tier for production pipelines and commercial integrations, and custom Enterprise deployment for larger teams. It sits in the emerging genai-security space addressing data oversharing rather than competing with a named incumbent, and with four releases since its 2023 launch and the latest just 17 days old, it is under active development.
Knostic enforces need-to-know access controls for enterprise AI assistants such as Microsoft Copilot.
How Knostic helps
Which employees would surface a document they have no need-to-know for through Copilot?
checks each retrieval against the requester's need-to-know scope and flags the ones that would have exposed a permitted-but-inappropriate file, before the assistant returns it
Where does our AI assistant's oversharing risk actually sit, by team or data source?
rolls flagged retrievals up by department and repository so the exposure shows up as a pattern rather than a one-off incident
Which of our access policies are actually being enforced by the AI layer versus just documented?
compares the live permission model an assistant is honoring against the policy on record and names the gaps between the two
Did a recent permissions change quietly widen what an assistant can retrieve for someone?
replays retrieval requests against the old and new permission sets and shows whose results changed
Who has been retrieving content through the assistant that they could not have gotten to directly?
cross-references assistant-served results against each user's direct access rights and lists the mismatches
Languages
Screenshots
From the release notes, newest first. Click one to see it full size.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 Knostic, 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 Knostic 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
knostic.ai, every changeKnostic's home page and 6 more pages as they looked each month from November 2023 to October 2026: 16 renders, 4 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.
Coverage
Missing something? Tell us
What Knostic connects to, runs on and detects, read from its release notes and docs. So far: 2 new detections.
2 changes, tracked since Oct 19, 2026.
-
Oct 262026
new Malicious credential-redirection detection for @bestcoolman/dev-mcp
Adds 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7. 7 in all.
AgentMesh flagged version 0.0.7, prompting our investigation.
-
Oct 192026
new AgentMesh detection of steganographic remote-code-execution chain in iflow-mcp_cmpxchg16-reddit-mcp
With iflow-mcp_cmpxchg16-reddit-mcp 0.1.0, reddit_extract
Knostic's AgentMesh rated the PyPI package iflow-mcp_cmpxchg16-reddit-mcp as Dangerous after identifying this chain. Further research traced the code to a documented educational proof of concept (PoC) in the cmpxchg16/mcp-ethical-hacking repository.
Nothing first seen in this window. That doesn't mean Knostic shipped nothing, only that we found no record of it.
How we count
Read from 3 of 5 release notes and docs updates we hold for Knostic. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Knostic's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
5 entries
No entries match these filters.
- October 20263
- July 20261
- May 20261
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →