OSINT MCP Gateway
bonetrees/osint-mcp-gateway
Gateway MCP modular para investigações de inteligência de ameaças multi-fonte
Ver no GitHubPlataforma modular de servidores MCP para investigações OSINT e inteligência de ameaças. Agrega VirusTotal, Shodan, DNS, WHOIS, RIPEStat e OTX através de um gateway centralizado com busca BM25, permitindo que Claude acesse ~50 ferramentas de reconhecimento através de 4 ferramentas visíveis.
Instalação
npx convez-ai bonetrees/osint-mcp-gateway1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Investigações de segurança e threat intelligence automatizadas
- Pesquisa de reputação de IPs, domínios e URLs em tempo real
- Análise de vulnerabilidades e indicadores de comprometimento
- Integração de múltiplas fontes OSINT num único ponto de acesso
Veredito

Solução técnica robusta e bem arquitetada para equipes de segurança que precisam integrar múltiplas fontes OSINT via Claude. Excelente para automação de investigações de ameaças, mas requer conhecimento DevOps e APIs de inteligência pagos (Shodan, VirusTotal, OTX) para máximo valor.
README
A tradução para o português deste README ainda está na fila.
OSINT MCP Tools
Modular, conversational MCP servers for OSINT and threat-intelligence investigation. Each server wraps one intelligence source and is independently deployable; an OSINT Gateway aggregates them and exposes a single BM25-searchable tool catalog to Claude.
Servers
| Server | What it does | Port | API key |
|---|---|---|---|
| OSINT Gateway | Aggregates all backends; BM25 tool search across the catalog | 9000 | — |
| Shodan | IP / service / vulnerability lookups | 9102 | SHODAN_API_KEY |
| VirusTotal | File / URL / domain / IP intel | 9103 | VT_API_KEY |
| DNS OSINT | DNS reconnaissance (resolution, PTR, axfr probes, SPF/DMARC) | 9104 | — |
| WHOIS | RDAP registration and routing data | 9105 | — |
| RIPEStat | BGP, prefix, ASN, geolocation, abuse contacts | 9106 | — |
| OTX | AlienVault community threat intel — pulses and indicators | 9107 | OTX_API_KEY |
API keys live in .env at repo root.
Quick start
Build from source (local development)
# Start everything
docker compose up --build
# Or one server
docker compose up --build shodan
# Health checks
curl http://localhost:9000/health # Gateway
curl http://localhost:9102/health # Shodan
# ...
Use prebuilt images from GHCR
Images for every server are published to ghcr.io/bonetrees/<service> on every merge to main, tagged latest and short-SHA.
# One-time auth
gh auth refresh -s read:packages && gh auth token | docker login ghcr.io -u "$(gh api user -q .login)" --password-stdin
# Pull and run
docker compose -f docker-compose.yml -f docker-compose.ghcr.yml pull
docker compose -f docker-compose.yml -f docker-compose.ghcr.yml up -d
# Pin a specific build for rollback
IMAGE_TAG=<short-sha> docker compose -f docker-compose.yml -f docker-compose.ghcr.yml up -d
See CLAUDE.md for the full command reference.
Architecture
- One container per server — each server is independently deployable
- Streamable-HTTP transport — same container runs locally and in Cloud Run
- Composition via gateway — clients see ~4 visible tools (
search_tools,call_tool,list_backends,gateway_status); the gateway proxies the underlying ~50-tool catalog with BM25 search for discovery - Self-contained — no shared runtime dependencies between servers; each is a standalone Poetry project
Project structure
├── CLAUDE.md # Project-level instructions and command reference
├── docker-compose.yml # All servers, build-from-source
├── docker-compose.ghcr.yml # Override that pulls prebuilt GHCR images
├── docs/
│ ├── PROJECT_VISION.md # "Vibe Investigate" concept
│ ├── MCP_SERVER_TEMPLATE.md # Architecture template for new servers
│ └── GATEWAY_TEMPLATE.md # Gateway-specific patterns
├── tools/
│ ├── osint-gateway/
│ ├── shodan_mcp/
│ ├── dns-osint-mcp/
│ ├── vt_mcp/
│ ├── whois-mcp/
│ ├── ripestat-mcp/
│ └── otx-mcp/
└── .github/workflows/
└── build-images.yml # GHCR build-and-push pipeline
Documentation
- CLAUDE.md — project-level instructions, command reference, cross-server conventions
- docs/PROJECT_VISION.md — what we're building and why
- docs/MCP_SERVER_TEMPLATE.md — canonical architecture template for new servers
- docs/GATEWAY_TEMPLATE.md — gateway-specific patterns
- Per-server READMEs: Gateway · Shodan · DNS OSINT · VirusTotal · WHOIS
Development
Each server is a standalone Poetry project. Per-server commands (install, test, lint) live in each server's CLAUDE.md. New servers should follow docs/MCP_SERVER_TEMPLATE.md — including the description-enrichment guidance for BM25 discovery.
Code style: Python ≥3.13, Black + Pylint, type hints throughout, %s lazy formatting in logs.