Quarry MCP server
Commit Nov 12, 2026Automates cybersecurity investigations and regulatory evidence collection for Brazilian fintechs using an auditable LLM-driven pipeline.
Also known as Josepassinato/Security
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 12, 2026
- License
- MIT
What is Quarry MCP?
Quarry automates cybersecurity investigations and regulatory evidence collection for Brazilian fintechs using an auditable LLM-driven pipeline.
Summary generated from the project's README
About Quarry MCP server
Quarry provides an automated cybersecurity investigation and regulatory evidence collection pipeline specifically designed for Brazilian fintechs. It helps organizations meet compliance requirements for BCB 85/2021, LGPD/ANPD, and Open Finance by transforming vague incident briefs into structured, citable investigations. The system uses a LangGraph orchestrator with a parallel router to decompose alerts into sub-investigations covering areas like phishing, identity, cloud, and insider threats.
Developers can integrate this server into existing workflows using Claude Desktop, Cursor, or Cody via its MCP server implementation. The setup requires Docker 24+ and Docker Compose, along with an OpenAI API key for the underlying LLM operations. Unlike generic SIEM tools, this server includes Brazilian-specific customizations such as Sigma rules calibrated for the Pix payment ecosystem and automated evidence collection for local audits.
Every step of the process is recorded in an Investigation Ledger using a hash chain to ensure all LLM prompts, tool calls, and cited documents remain auditable. This allows security teams to defend their conclusions during Bacen audits or legal proceedings. The platform also includes a CI evaluation harness to measure detection accuracy and response quality.
What you can do with it
- 1Automate Brazilian regulatory evidence collectionA developer can use the tool to gather necessary documentation for compliance with BCB 85/2021 and LGPD requirements.
- 2Investigate Pix-related fraud incidentsAn analyst can trigger investigations into specific payment anomalies like Pix mule accounts or fraudulent transfers.
- 3Audit AI-driven security decisionsSecurity teams can review the full history of an investigation to verify the reasoning behind an automated conclusion.
- 4Integrate security investigations into IDEsDevelopers can connect their coding assistants directly to the security investigation chain.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 16, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablejosepassinato/security is public and reachablegithub.com/josepassinato/security ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/josepassinato/security ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubQuarry
Open-source Bacen Evidence Engine for Brazilian fintechs. Replace the consultant-and-spreadsheet workflow with a deterministic, citable, exportable evidence pipeline for BCB 85/2021, Bacen Comunicado 44.323/2024 (24h), LGPD/ANPD (Res. 15/2024, 3 business days), and Open Finance. Bacen-native by construction, not by retrofit. Strengthens governance, increases auditability, and preserves regulatory evidence — does not substitute regulatory obligation nor guarantee supervisor acceptance.
🌐 Live sandbox · 📘 Docs · 🛡️ Security policy · 🇧🇷 Resumo em Português
The problem
A serious investigation in a Brazilian fintech today has to correlate Pix events, mobile banking authentication, device behaviour, Open Finance access, boleto creation, account takeover attempts, mule accounts, fraud alerts and regulatory reporting. That work currently depends on a senior analyst who knows how to turn a vague incident brief into a sequence of queries, hypotheses and evidence.
It does not scale. And it does not fit an imported SIEM that was never designed for Pix, BCB 85/2021 or LGPD.
What Quarry does
Quarry makes the senior-investigator workflow executable, measurable and repeatable — without removing the human from the approval loop:
- LangGraph orchestrator with a parallel router (phishing · identity · cloud · insider) that decomposes one alert into simultaneous sub-investigations.
- Investigation Ledger — every LLM prompt, every tool call, every cited document is recorded and auditable. You can defend the conclusion in a Bacen audit or a court case.
- CI eval harness with 5 deterministic suites: MITRE accuracy, alert reduction, investigation completeness, response quality, schema coverage.
- Multi-source detection corpus (SigmaHQ · MITRE CAR · Splunk Security Content · Chronicle) with per-rule provenance.
- MCP server to plug Claude Desktop, Cursor, Cody and other assistants into the same investigation chain.
- Brazilian customizations in
customizations/: pt-BR hunts, Sigma rules calibrated for Brazil's payment ecosystem (Pix, BCB, LGPD), and compliance evidence automation for local audits.
What this is not
Quarry does not replace your SOC; it increases its throughput. It is not a managed-SOC service, and it does not try to compete with tier-1 vendors on generic features. Generic SIEM/SOAR is out of scope.
Heritage
Quarry is an independent MIT fork of AiSOC
(commit 28ce9f6b). Upstream attribution is preserved verbatim in
LICENSE, NOTICE.md, and
README.AISOC.md. Inherited components (orchestrator,
ledger, MCP server, eval harness, base detection corpus) are credited to
their original authors; Quarry-specific work lives under customizations/.
Quick start
Requirements: Docker 24+ and Docker Compose v2.
git clone https://github.com/Josepassinato/Security.git quarry
cd quarry
cp .env.example .env # fill in OPENAI_API_KEY and generate QUARRY_CREDENTIAL_KEY
docker compose -f docker-compose.demo.yml up -d
In about 2 minutes:
- API at
http://localhost:8000(GET /health) - UI at
http://localhost:3000 - Postgres, Redis, Qdrant, OpenSearch and Neo4j come up as containers
- The demo profile seeds synthetic alerts from the FinPlay Pagamentos dataset (CPFs, Pix keys and events generated by seed — no real institution)
# run an investigation against the demo dataset
curl -s http://localhost:8000/v1/investigations -X POST \
-H "Content-Type: application/json" \
-d '{"alert_id":"demo-pix-mule-001"}' | jq
# open the forensic ledger
open http://localhost:3000/investigations
For production deploys (air-gapped, self-hosted VPS, Kubernetes), see
docs/operations/.
Architecture in 30 seconds
┌─ Alert ingress (SIEM, log shipper, MCP)
│
▼
┌─────────────────────┐ ┌──────────────────────────┐
│ LangGraph Router │ ───► │ Investigation Ledger │
│ (parallel sub- │ │ (Postgres + hash chain) │
│ investigators) │ └──────────────────────────┘
└─────────────────────┘ ▲
│ │
▼ │
┌─────────────────────┐ │
│ Detection corpus │ │
│ + Brazilian Sigma │ ─── evidence ────┘
│ + Hunt templates │
└─────────────────────┘
│
▼
Citation-validated report ──► Analyst review ──► Action / SAR / ANPD draft
Deep dive: docs/pt-br/orchestrator-deep-dive.md.
Current status
Quarry is in early access. The core inherited from AiSOC (eval harness, ledger, MCP server) is stable; the Brazilian customizations are being validated with synthetic data and private pilots.
| Capability | State |
|---|---|
| LangGraph orchestrator + auditable ledger | ✅ Stable (upstream AiSOC) |
| CI eval harness (5 suites) | ✅ Stable |
| MCP server | ✅ Stable |
| Detection corpus + provenance | ✅ Stable |
| Brazilian customizations (Pix, BCB 85, LGPD) | 🟡 Validating — 11 patterns published |
| FP reduction benchmark (FinPlay BR) | ✅ Published under customizations/benchmarks/ |
| Public demo | 🟢 quarry.12brain.org |
| Production-ready in regulated fintech | ⏳ Pilots under NDA — get in touch |
⚠️ Do not run in production without a guided pilot. The project is open-source, but the compliance, detection calibration and integration work is still done per pilot. See
SECURITY.mdfor vulnerability reports.
Repository layout
quarry/
├── apps/ Next.js frontend + docs site
├── services/ 14 microservices (Python + Go)
├── packages/ Shared SDKs and libraries
├── detections/ Imported corpus with per-rule provenance
├── playbooks/ Response playbooks
├── customizations/ ⭐ Everything Quarry-specific (BR, Pix, BCB, LGPD)
│ ├── detections/ Sigma rules calibrated for Brazil
│ ├── threat-intel/br-fintech/ 11 patterns (Pix / ATO / Boleto / QR / …)
│ ├── hunts/ pt-BR hunt templates
│ ├── prompts/ pt-BR prompts
│ ├── compliance/ BCB 85/2021 and LGPD evidence
│ └── benchmarks/ Publishable runs (auto-triage on FinPlay BR)
├── infrastructure/ IaC (VPS, Kubernetes, Helm)
├── docs/
│ ├── adrs/ Architecture Decision Records
│ ├── pt-br/ Portuguese manuals and runbooks
│ ├── operations/ Deploy, hardening, air-gap
│ └── compliance/ ISO 27001, NIST CSF mappings
└── examples/ Ready-to-clone examples
Design principles
- Customization is kept separate from upstream. Anything Quarry-specific
lives under
customizations/. This enables controlled cherry-picks of upstream AiSOC improvements. - English in code, Portuguese in operations. Identifiers, logs and
conventional commits (
feat:/fix:) are English; runbooks and ADRs are Portuguese. - Adversarial-agent assumptions. Human operators may be hostile or compromised. Auditability is a design constraint, not an optional feature.
- Rigorous attribution.
NOTICE.mdlists AiSOC and every detection corpus (SigmaHQ/DRL-1.1, MITRE CAR/Apache, Splunk/Apache, Chronicle/Apache, Anthropic Cybersec/Apache-2.0). - No rebrand of public research. Quarry does not present inherited work
as original. See
README.AISOC.md.
Community & Contributing
Issues, PRs and bug reports are welcome. The community surfaces are:
- GitHub Discussions — open questions, ideas, roadmap input
- Issues — bug reports and feature requests (good first issues are tagged for newcomers)
- Pull Requests — see
CONTRIBUTING.mdfor flow, commit conventions and how to run the eval suite - Vulnerabilities — do not open a public issue, follow
SECURITY.md - Code of conduct —
CODE_OF_CONDUCT.md
A chat server (Discord / Slack) will be set up once the community needs it. For now, GitHub Discussions is the canonical place to talk.
Areas open for contribution right now:
- 🇧🇷 pt-BR hunts for other verticals (government, retail, healthcare)
- 🧠 Prompts and few-shots for the orchestrator
- 📚 Detection rules calibrated to Brazilian threat actors
- 🧪 Eval harness extensions and synthetic dataset additions
Sponsors: if you want to fund maintenance time, see the Sponsor
button on the repo home
or check .github/FUNDING.yml.
License
MIT — see LICENSE. Upstream attributions in
NOTICE.md and README.AISOC.md.
Resumo em Português
Quarry — SOC soberano open-source para fintechs brasileiras reguladas pelo Bacen.
Investigação assistida por LLM com cadeia probatória citável, rodando dentro do seu perímetro. Mapeamento direto com Resolução BCB 85/2021 e LGPD.
- Para quem é: fintechs Bacen-licenciadas (SCD, SEP, Conta de Pagamento, PSTI, Payment Initiator, CCB) que precisam atender o monitoramento contínuo da Res. BCB 85/2021 sem o custo de um MSSP enterprise.
- Como funciona: orquestrador LangGraph com router paralelo, Ledger de
Investigação auditável (hash chain), eval harness em CI, MCP server para
Claude Desktop / Cursor / Cody, e customizações brasileiras (Pix, BCB,
LGPD) em
customizations/. - Demo público: quarry.12brain.org
- Licença: MIT (herdada do upstream AiSOC)
- Status: early access. Pilotos sob NDA em curso. Não rodar em produção sem piloto guiado — a calibração de detecção e a integração regulatória são feitas por piloto.
Reports de vulnerabilidade: SECURITY.md. Contribuições:
CONTRIBUTING.md.
Quarry MCP questions
What is Quarry used for?
It provides a deterministic, citable, and exportable evidence pipeline for Brazilian regulatory requirements like BCB 85/2021, ANPD, and Open Finance.
Can I use this with my AI coding assistant?
Yes, it includes an MCP server that allows you to plug Claude Desktop, Cursor, Cody, and other assistants into the investigation chain.
Is it suitable for production use in a regulated environment?
It is currently in early access; you should not run it in production without a guided pilot to ensure detection calibration and regulatory integration.