Sensor Bio MCP Serverofficial
A
licenseA
qualityD
maintenanceConnects Sensor Bio wearable data to AI assistants via the Model Context Protocol, enabling queries about sleep, heart rate, activity, and other biometrics.
13
1
MIT
bsp-mcp
OfficialRelated Servers
Alternatives to bsp-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to access Sapphire Wellness user data, including health alerts, personalized recommendations, and partner service subscriptions.-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to access user profile data from the Sapphire Wellness App, including health alerts, personalised recommendations, and partner service subscriptions.-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to access Sapphire Wellness user profile data, including health alerts, personalized recommendations, and partner service subscriptions.-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to access Sapphire Wellness user profile data, including health alerts, personalized recommendations, and partner service subscriptions.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access your Oura Ring health data through OAuth2-authenticated API calls.6 npm9MIT
TDQS
A3.9/5.0
Scored across 13 tools
Disambiguation4/5
Most tools target clearly distinct resources and actions: BEO lifecycle, consent, records, taxonomy, and network listings. The only real ambiguity is between bsp_check_consent and bsp_verify_consent, though their descriptions distinguish session-level configuration from validating a specific token.
Naming Consistency5/5
All tools share the bsp_ prefix and follow a consistent verb_noun pattern: list_beos, get_biorecords, submit_biorecord, destroy_beo, lock_beo, revoke_all_tokens, etc. Even near-synonyms like check and verify do not break the naming scheme.
Tool Count5/5
13 tools is well-scoped for this domain and each tool maps to a distinct operation: discovery, consent checking, record reads/writes, taxonomy lookup, and emergency controls. There is no obvious redundancy or padding.
Completeness4/5
Core workflows are well covered: list available entities, check/verify consent, summarize and read BioRecords, submit new records, resolve biomarkers, and handle emergency lock/revoke/destroy actions. Minor gaps exist, such as no explicit consent token issuance or update/delete for individual records, but these may reasonably be outside the server's intended role.
Maintenance
ActivityInactive
ResponsivenessNo issues