Skip to main content
Glama
fulcradynamics

Fulcra MCP Server

by fulcradynamics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Fulcra MCP Server

No user-submitted related servers found.

    Related Servers

    • Oura MCP Server

      koji117
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides access to Oura Ring health data, including sleep, activity, readiness, and stress metrics via the Model Context Protocol. It enables users to query their personal biometric information and daily health summaries through natural language in MCP-compatible clients.
      2,090 npm
      MIT

    • oura-mcp

      louis030195
      A
      license
      B
      quality
      D
      maintenance
      Enables users to query their Oura Ring data (sleep, readiness, activity, heart rate) via natural language through any MCP-compatible LLM.
      4
      16 npm
      1
      MIT

    • ultrahuman_mcp

      crixalis17
      F
      license
      A
      quality
      D
      maintenance
      Exposes real-time health data from the Ultrahuman Ring to AI agents via the Model Context Protocol, providing optimized summaries with trend analysis and actionable insights.
      7
      -

    • ContextFlow MCP Server

      Diwakarsrd
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible agents such as Claude and Cursor to retrieve permission-aware, structured context from local or hosted data stores. Exposes tools for semantic search, entity and relationship lookup, memory access, context pack compilation, source attribution, and retrieval explanation.
      1
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific data types or operations: location retrieval (get_location_at_time, get_location_time_series), metric data (get_metric_samples, get_metric_time_series), metadata (get_metrics_catalog, get_user_info), and specialized analyses (get_sleep_cycles, get_workouts). There is no functional overlap between tools, making selection unambiguous.

    Naming Consistency5/5

    All eight tools follow a consistent 'get_*' verb_noun pattern with snake_case throughout. The naming convention is perfectly uniform, making the tool set predictable and easy to understand at a glance.

    Tool Count5/5

    With 8 tools, this server is well-scoped for its purpose of retrieving user context data (location, metrics, sleep, workouts, and metadata). Each tool serves a distinct and necessary function without redundancy, making the count ideal for the domain.

    Completeness4/5

    The tool set provides comprehensive read-only coverage for retrieving user context data across multiple domains (location, metrics, sleep, workouts, and user info). A minor gap exists in the lack of update or delete operations, but this is reasonable for a context retrieval server focused on data access rather than modification.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources