Estonian Cybersecurity MCP
# Estonian Cybersecurity MCP
<!-- ANSVAR-CTA-BEGIN -->
> ### ▶ Try this MCP instantly via Ansvar Gateway
> **50 free queries/day · no card required · OAuth signup at [ansvar.eu/gateway](https://ansvar.eu/gateway)**
>
> One endpoint, one OAuth signup, access from any MCP-compatible client.
### Connect
**Claude Code** (one line):
```bash
claude mcp add ansvar --transport http https://gateway.ansvar.eu/mcp
```
**Claude Desktop / Cursor** — add to `claude_desktop_config.json` (or `mcp.json`):
```json
{
"mcpServers": {
"ansvar": {
"type": "url",
"url": "https://gateway.ansvar.eu/mcp"
}
}
}
```
**Claude.ai** — Settings → Connectors → Add custom connector → paste `https://gateway.ansvar.eu/mcp`
First request opens an OAuth flow at [ansvar.eu/gateway](https://ansvar.eu/gateway). After signup, your client is bound to your account; tier (free / premium / team / company) determines fan-out, quota, and which downstream MCPs are reachable.
---
## Self-host this MCP
You can also clone this repo and build the corpus yourself. The schema,
fetcher, and tool implementations all live here. What is not in the repo is
the pre-built database — TDM and standards-licensing constraints on the
upstream sources mean we host the corpus on Ansvar infrastructure rather
than redistribute it as a public artifact.
Build your own: run this repo's ingestion script (entry-point varies per
repo — typically `scripts/ingest.sh`, `npm run ingest`, or `make ingest`;
check the repo root).
<!-- ANSVAR-CTA-END -->
**Estonian cybersecurity data for AI compliance tools.**
[](https://opensource.org/licenses/Apache-2.0)
[](https://github.com/Ansvar-Systems/estonian-cybersecurity-mcp/actions/workflows/ci.yml)
Query Estonian cybersecurity data -- regulations, decisions, and requirements from RIA/CERT-EE (Information System Authority) -- directly from Claude, Cursor, or any MCP-compatible client.
Built by [Ansvar Systems](https://ansvar.eu) -- Stockholm, Sweden
---
## Available Tools (6)
| Tool | Description |
|------|-------------|
| `ee_cyber_search_guidance` | Full-text search across RIA cybersecurity guidelines, directives, and technical standards. Covers ISKE security frame... |
| `ee_cyber_get_guidance` | Get a specific RIA guidance document by reference (e.g., |
| `ee_cyber_search_advisories` | Search CERT-EE security advisories and incident alerts. Returns advisories with severity, affected products, and CVE ... |
| `ee_cyber_get_advisory` | Get a specific CERT-EE security advisory by reference (e.g., |
| `ee_cyber_list_frameworks` | List all RIA/CERT-EE cybersecurity frameworks covered in this MCP, including ISKE, national cybersecurity strategy, a... |
| `ee_cyber_about` | Return metadata about this MCP server: version, data source, coverage, and tool list. |
All tools return structured data with source references and timestamps.
---
## Data Sources and Freshness
All content is sourced from official Estonian regulatory publications:
- **RIA/CERT-EE (Information System Authority)** -- Official regulatory authority
### Data Currency
- Database updates are periodic and may lag official publications
- Freshness checks run via GitHub Actions workflows
- Last-updated timestamps in tool responses indicate data age
See `sources.yml` for full provenance metadata.
---
## Security
This project uses multiple layers of automated security scanning:
| Scanner | What It Does | Schedule |
|---------|-------------|----------|
| **CodeQL** | Static analysis for security vulnerabilities | Weekly + PRs |
| **Semgrep** | SAST scanning (OWASP top 10, secrets, TypeScript) | Every push |
| **Gitleaks** | Secret detection across git history | Every push |
| **Trivy** | CVE scanning on filesystem and npm dependencies | Daily |
| **Docker Security** | Container image scanning + SBOM generation | Daily |
| **Socket.dev** | Supply chain attack detection | PRs |
| **Dependabot** | Automated dependency updates | Weekly |
See [SECURITY.md](SECURITY.md) for the full policy and vulnerability reporting.
---
## Important Disclaimers
### Not Regulatory Advice
> **THIS TOOL IS NOT REGULATORY OR LEGAL ADVICE**
>
> Regulatory data is sourced from official publications by RIA/CERT-EE (Information System Authority). However:
> - This is a **research tool**, not a substitute for professional regulatory counsel
> - **Verify all references** against primary sources before making compliance decisions
> - **Coverage may be incomplete** -- do not rely solely on this for regulatory research
**Before using professionally, read:** [DISCLAIMER.md](DISCLAIMER.md) | [PRIVACY.md](PRIVACY.md)
### Confidentiality
Queries go through the Claude API. For privileged or confidential matters, use on-premise deployment. See [PRIVACY.md](PRIVACY.md) for details.
---
## Development
### Setup
```bash
git clone https://github.com/Ansvar-Systems/estonian-cybersecurity-mcp
cd estonian-cybersecurity-mcp
npm install
npm run build
npm test
```
### Running Locally
```bash
npm run dev # Start MCP server
npx @anthropic/mcp-inspector node dist/index.js # Test with MCP Inspector
```
### Data Management
```bash
npm run build:db # Rebuild SQLite database from seed data
npm run check-updates # Check for new regulatory data
```
---
## More Ansvar MCPs
Full fleet at [ansvar.eu/gateway](https://ansvar.eu/gateway).
## Contributing
Contributions welcome! See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
---
## License
Apache License 2.0. See [LICENSE](./LICENSE) for details.
### Data Licenses
Regulatory data sourced from official government publications. See `sources.yml` for per-source licensing details.
---
## About Ansvar Systems
We build AI-powered compliance and legal research tools for the European market. Our MCP fleet provides structured, verified regulatory data to AI assistants -- so compliance professionals can work with accurate sources instead of guessing.
**[ansvar.eu](https://ansvar.eu)** -- Stockholm, Sweden
---
<p align="center">
<sub>Built with care in Stockholm, Sweden</sub>
</p>
TDQS
Scored across 6 tools
Each tool targets a distinct operation and resource type: guidance search/retrieval, advisory search/retrieval, framework listing, and server metadata. There is no meaningful overlap between the search and get tools since one returns result sets and the other fetches a specific document by reference.
Tool names follow a consistent ee_cyber_ prefix with clear verb-noun patterns for most tools, such as search_guidance, get_guidance, search_advisories, and list_frameworks. The 'about' tool deviates slightly from the verb_noun convention but is still predictable and readable.
Six tools is an appropriate, focused size for a read-only cybersecurity document and advisory retrieval server. Each tool serves a clear purpose without bloat, and the count matches the apparent scope well.
The tool set covers the core domain needs: searching and retrieving both guidance documents and advisories, listing available frameworks, and providing server metadata. For a read-only reference server, this is a complete and usable surface with no obvious dead ends.