M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionAssetOpsBenchA multi-agent MCP benchmark and framework for industrial asset operationsHevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS45 / 100 · D77 / 100 · B
Reliability6 / 2012 / 20
Security and permissions7 / 2016 / 20
Maintenance14 / 2016 / 20
Documentation10 / 2018 / 20
Setup experience8 / 2015 / 20
Best for
  • Maintenance engineers
  • Reliability specialists
  • Facility planners
  • Industry 4.0 researchers
  • 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
  • Users requiring verified production connectors, authentication, or transport details.
  • Users seeking general-purpose chat or non-industrial asset-maintenance tools.
  • Users expecting to run the complete scenarios without consulting the project setup documentation.
  • 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 access to the simulated industrial environment data used by the project.
  • Depending on the task, it may need to read sensor, asset, FMEA, alert, and work-order records.
  • Specific authentication, authorization, and write permissions are not described in the provided material.
  • 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
  • The server manifest is unavailable, so the actual tool surface, startup method, transport, and authentication details require confirmation.
  • The project is under active development; the main branch may differ from branches used for publications.
  • Operations such as adding failure modes, registering models, and running recipes may change records in the project environment; permissions and rollback behavior are not described.
  • 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 clientsClaude Desktop, Cursor, Codex, Antigravity
Tools3826