Documentation Index
Fetch the complete documentation index at: https://docs.q-uestionable.ai/llms.txt
Use this file to discover all available pages before exploring further.
What is q-ai?
q-ai tests the security of MCP (Model Context Protocol) servers and agentic AI systems. It scans servers for vulnerabilities, tests whether models follow poisoned tool descriptions, intercepts MCP traffic, and measures whether adversarial documents survive RAG retrieval. Findings include execution-level proof that vulnerabilities are exploitable end-to-end, not just scan results. All findings are mapped to four security frameworks: OWASP MCP Top 10, OWASP Agentic Top 10, MITRE ATLAS, and CWE.Bring what you have, prove what matters
Already running Garak or PyRIT? qai picks up where they leave off. Import your existing results, associate them with a target, and qai uses those findings to drive its native modules — prioritizing inject payloads based on the compliance patterns your tools already discovered.Modules
| Module | What it does |
|---|---|
| audit | Scans MCP servers for vulnerabilities, maps findings to the OWASP MCP Top 10 and MITRE ATLAS, outputs SARIF |
| proxy | Intercepts MCP traffic between client and server for inspection, modification, and replay |
| inject | Tests AI agent susceptibility to tool poisoning and prompt injection using configurable payloads |
| chain | Composes multi-step attack sequences across audit findings and inject techniques |
| ipi | Generates adversarial documents with hidden instructions, tracks execution via authenticated callbacks |
| cxp | Builds poisoned instruction files for coding assistants, validates whether models comply |
| rxp | Measures whether adversarial documents appear in top-k retrieval results across embedding models |
Research
qai’s research program studies Capability Trust Propagation Failure — how trust properties (provenance, integrity, authorization scope, intended audience) fail to propagate across capability boundaries in multi-step AI systems. It shows up across existing OWASP MCP Top 10 and OWASP Agentic Top 10 categories rather than needing a new one. Findings carry execution-level proof. Authenticated callbacks confirm that an attack ran end-to-end through a real agentic system — not that a model was convinced to write attacker-supplied text. Coding assistant context-file poisoning (thecxp module) targets real products directly. Positive findings can be filed as CVEs, creating a path to CVE-attributed research rather than research that only lives in published form.
Quick start
Install via pip (requires Python 3.11+):Mitigation guidance system
Every finding includes automated mitigation guidance. The guidance system maps findings to remediation strategies grouped by severity and remediation effort. Use the web UI to toggle guidance on/off per finding, or access it via the CLI.Learn more
- Quick Start — Install, configure a provider, run your first scan
- Core Concepts — MCP threat model, framework mappings, module methodologies
- Responsible Use — Authorization requirements and responsible disclosure
- GitHub