Your Heart workout log: workouts, records, templates, programs. Holds no health data.
MCPpedia last refreshed this data
me.heart-of/heart is an MCP server that your Heart workout log: workouts, records, templates, programs. Holds no health data. Its tool list has not been published yet over http, requires no API key, and scores 38/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
https://mcp.heart-of.meRemote servers are added as connectors, not in claude_desktop_config.json, which is for local servers.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Your Heart workout log: workouts, records, templates, programs. Holds no health data.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in health
MCP server for the ClinicalTrials.gov v2 API. Search trials, retrieve study details and results, and match patients to eligible trials.
Search ClinicalTrials.gov: find studies, retrieve results, match patients to candidate trials.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Control FL Studio with Claude: in-DAW mixing, diagnosis, routing, and composition.
MCP Security Weekly
Get CVE alerts and security updates for me.heart-of/heart and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Backend for the Heart of Yours fitness app. Dart server on AWS Lambda behind API Gateway, Postgres via Supabase, all CDN/storage on AWS.
heart-go/
├── api/ # Dart server (Lambda entrypoint)
├── shared/
│ ├── heart_models/ # Data classes + service interfaces (used by api + the Flutter client)
│ └── heart_aws/ # Boto3-shaped AWS clients (S3, SQS, SNS, Scheduler) on aws_signature_v4
├── database/
│ ├── migrations/ # Forward-only SQL migrations
│ ├── tests/ # pgtap suite — public/{tables,functions}, archive/...
│ └── test_utils/ # Test helpers (builders + JSON validators)
├── firebase/ # Python Lambda: FCM push + Firebase auth cleanup (uv workspace member)
├── assets/ # Python Lambda: exercise media processing pipeline (uv workspace member)
├── infrastructure/ # Terraform stacks (api, assets, cdn, content, firebase, monitoring)
│ # + environments/{dev,prod} — see infrastructure/README.md
├── content/ # Exercise library YAML + schema + sample templates JSON, synced to CDN
├── scripts/ # Migration runner, db test runner, library sync/validation
├── site/ # Static marketing/legal pages
├── docs/ # Dated design docs; handoff.md is the definition of done, style.md the house style
├── agents/ # Autonomous agent launchers + guard hook (see agents/README.md)
└── .github/workflows/ # CI: deploy-api, deploy-assets, deploy-firebase, exercise-library
# (each split into a reusable workflow + dev/prod wrappers)
Per-component docs:
| Layer | Tech |
|---|---|
| Server runtime | Dart 3.10 + relic, compiled to native + Lambda Web Adapter |
| Storage | Postgres (Supabase), no ORM — raw SQL |
| Object storage / CDN | S3 + CloudFront |
| Auth | Firebase OIDC token verification |
| Async | EventBridge S3-rules → SQS → /events (Lambda routes events back to itself) |
| Scheduled jobs | EventBridge Scheduler → SQS → /events |
| Side services | Python 3.13 Lambdas in a uv workspace: firebase/ (push, auth cleanup), assets/ (media) |
| IaC | Terraform (with Supabase provider) |
| CI/CD | GitHub Actions, OIDC role for AWS |
| Tests | Dart test + mockito for app code, pgtap for the database, pytest for the Python services |
make bootstrap # dart pub get + mocks for all packages, uv sync, git hooks
make db-up # containerized Postgres 17 + pgtap (skip if you run a native one)
make test # the full matrix: Dart x3, migrations + pgtap, pytest x3
make lint # dart analyze x3 + ruff
Each suite can also run individually — make test-dart / test-db / test-python,
or the underlying commands directly (see the Makefile and per-component READMEs).
The api package can be run locally