| FMRS | 45 / 100 · D | 77 / 100 · B |
|---|
| Reliability | 6 / 20 | 12 / 20 |
|---|
| Security and permissions | 7 / 20 | 16 / 20 |
|---|
| Maintenance | 11 / 20 | 16 / 20 |
|---|
| Documentation | 11 / 20 | 18 / 20 |
|---|
| Setup experience | 10 / 20 | 15 / 20 |
|---|
| Best for | - Security researchers and analysts
- SOC, threat-intelligence, and fraud investigation teams
- Developers who need MCP-based tool orchestration
- OSINT practitioners conducting lawful authorized investigations
| - Hevy PRO users who want AI assistants to directly access their workout data
- People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
- Anyone needing summaries and insights from their training data
|
|---|
| Not for | - Unauthorized monitoring of people or organizations
- Illegal data collection, intrusion, or privacy violations
- Users who do not want external APIs, third-party services, or local investigation tools
- Workflows requiring all findings to come from a single verified data source
| - Users without a Hevy PRO subscription (API key required)
- Users who want to use the server without an API key
- Those needing delete workflows (Hevy API does not expose delete endpoints)
|
|---|
| Required permissions | - Requires launching a local Python MCP server over stdio.
- The default AI agent requires ANTHROPIC_API_KEY; Ollama or an OpenAI-compatible backend can also be used.
- Optional tools require credentials for HIBP, IPInfo, IP2Location, AbuseIPDB, Shodan, VirusTotal, Censys, GitHub, or Bright Data.
- Requires network access to relevant services; some features depend on holehe, sherlock, sublist3r, and phoneinfoga being available in PATH.
- The REPL saves sessions in ~/.openosint/history/ and reports in reports/.
| - Requires HEVY_API_KEY environment variable for Hevy API authentication
- Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
- Read operations can fetch workouts, routines, folders, templates, history, and user info
|
|---|
| Risks and side effects | - Use is limited to legal and authorized security research.
- Investigations may process emails, phone numbers, usernames, IPs, breach records, and other sensitive data.
- Third-party APIs may impose rate limits, charges, data-retention terms, or service restrictions.
- Live dork searches and URL scraping use Bright Data APIs, and calls may be billable.
- External sources may be incomplete, outdated, or produce false positives; findings require human verification.
| - API key can be misused if leaked; do not expose in URLs, logs, or screenshots
- Create operations may produce duplicates on retry; update operations replace existing records
- The server sends data to the Hevy API and may send telemetry to external services unless disabled
|
|---|
| Supported clients | Claude Desktop, Claude Code | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 18 | 26 |
|---|