FYI MCP

FYI CLI

A multi-jurisdiction Freedom-of-Information (FOI) client for Alaveteli-based platforms — track, submit, and archive official information requests across New Zealand, Australia, the UK, and any other Alaveteli deployment (foi-repository, WhatDoTheyKnow, FragDenStaat, and more), from a single privacy-focused CLI.

The project's core is a Rust workspace (fyi-core, fyi-cli, fyi-mcp); a legacy Python package (fyi_system) remains available as a reference implementation but is no longer extended.

Where fyi-cli / fyi-mcp is listed

Draft / not yet submitted: Scoop, WinGet, Homebrew, Chocolatey, GHCR multi-arch workflow, PulseMCP, mcp.so, Docker MCP Catalog, mcp-get, OpenTools, AUR, nixpkgs, Snap, Flatpak, asdf/mise, Debian/PPA, Fedora/COPR.

cargo-binstall is already assets-ready and wired in-repo, but still depends on matching GitHub Release assets before it can be treated as a live distribution path. Codex and Anthropic packets are assets-ready but still require external submission.

Full status matrix (including planned channels): docs/registry-distribution-matrix.md.

---

🚀 Quick Start

# Install (Rust workspace, recommended)

cargo install --path crates/fyi-cli

or: cargo install fyi-cli (once published to crates.io)

Initialize

fyi-cli init-db

Create your first request

fyi-cli register-request ministry-of-justice "OIA Request" "Request body..." --status draft

Track and manage requests

fyi-cli list-requests

Full guide: QUICKSTART.md

---

✨ Features

• 🌐 Multi-Jurisdiction: Works with any Alaveteli deployment — foi-repository (NZ), WhatDoTheyKnow (UK), FragDenStaat (Germany), righttoknow.org.au (Australia), and more, with jurisdiction-aware metadata and localization on the way
• 🔒 Privacy-First: All data stored locally, optional encryption, Tor support
• 📊 Track Requests: Monitor FOI/OIA requests from creation to completion
• 🤖 Automated Monitoring: Watch instances for updates automatically
• 📈 Reports & Analytics: Generate dashboards, attention reports, handover docs
• 🔐 Secure Storage: Encrypted credentials, OS keyring integration
• 💻 CLI + MCP: Command-line tool and an MCP server for AI assistants
• 📦 Export Options: JSON, CSV, HTML export capabilities
• 🗄️ Faithful Archiving: WARC/WACZ capture of requests, correspondence, and attachments

---

📦 Installation

Full guide (Rust-first, all channels): [INSTALL.md](INSTALL.md) · version 0.1.2 · homepage github.com/edithatogo/fyi-cli

git clone https://github.com/edithatogo/fyi-cli.git

cd fyi-cli cargo install --path crates/fyi-cli --locked fyi-cli --help

Live listings and draft status: [Where fyi-cli / fyi-mcp is listed](#where-fyi-cli--fyi-mcp-is-listed) · full matrix: docs/registry-distribution-matrix.md · MCP catalog checklist: packaging/mcp-catalogs/SUBMISSION_CHECKLIST.md.

---

📖 Documentation

---

📚 Citation and Zenodo

Release metadata is versioned in CITATION.cff, .zenodo.json, and artifacts/release/zenodo-mirror-manifest.json. DOI fields remain unset until the live Zenodo record is verified for the tagged release.

---

🛡️ Security

Reporting a Vulnerability

Please do NOT report security vulnerabilities through public GitHub issues.

Use GitHub's private vulnerability reporting: https://github.com/edithatogo/fyi-cli/security/advisories/new

Security Policy: SECURITY.md

Security Features

• ✅ AES-256-GCM encryption for sensitive data
• ✅ PBKDF2-HMAC-SHA256 key derivation
• ✅ OS keyring integration for credential storage
• ✅ Tamper-evident audit logging
• ✅ Secure session management
• ✅ Input validation and sanitization
• ✅ Security headers (CSP, HSTS, X-Frame-Options)
• ✅ Automated security scanning (CodeQL, pip-audit, bandit)

---

🧪 Testing

# Rust release checks used by this repository

cargo +stable-x86_64-pc-windows-gnu fmt --all -- --check cargo +stable-x86_64-pc-windows-gnu clippy --workspace --all-targets --all-features -- -D warnings cargo +stable-x86_64-pc-windows-gnu test --workspace --all-features

Python legacy/support checks

.\.venv\Scripts\python.exe -m pytest tests/test_release_readiness.py

Opt-in live smoke test

FYI_LIVE_SMOKE=1 .\.venv\Scripts\python.exe -m pytest -m smoke tests/test_discovery_smoke.py

Test Coverage: Rust workspace checks are the release gate. Python support tests remain available for legacy docs and archive tooling.

---

🤝 Contributing

We welcome contributions! See CONTRIBUTING.md for guidelines.

Quick Start for Contributors

# Fork and clone

git clone https://github.com/YOUR_USERNAME/fyi-cli.git cd fyi-cli

Build & test the Rust workspace

cargo build --workspace --all-features cargo test --workspace --all-features

Make your changes, then submit a PR

git commit -m "feat: Add awesome feature" git push origin feature/awesome-feature

See CONTRIBUTING.md for the full development setup, including the legacy Python fyi_system package.

Code of Conduct

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

---

📊 Project Status

GitHub Projects

The project board for this repository is fyi-cli Conductor Roadmap. It mirrors the local .conductor/tracks.md registry and tracks completed Conductor work, release-readiness items, and external MCP registry follow-ups.

The umbrella Rare Insights on Open Policy from Aotearoa project is synchronized at the item level. GitHub Projects does not support nested projects, so synchronization is handled by scripts/sync_github_projects.py and the manual/scheduled project-sync workflow.

# Preview synchronization without changing either project

.\.venv\Scripts\python.exe scripts\sync_github_projects.py --dry-run

Apply synchronization from fyi-cli project 6 into RIOPA project 4

.\.venv\Scripts\python.exe scripts\sync_github_projects.py

The workflow requires a repository secret named PROJECT_SYNC_TOKEN with GitHub Projects access for user-level ProjectsV2 write