Spruce Health MCP by usefulapi
REMOTE · SPRUCE-HEALTH.USEFULAPI.IO
Read Spruce Health contacts, conversations, messages, phone lines and team members (read-only).
Available components
Last scanned (7 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2651 tokens (~110/item across 24 items; 24 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.4.0 → 1.5.0 functional
- 12 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 10 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://spruce-health.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of spruce-health.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://spruce-health.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://spruce-health.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://spruce-health.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://spruce-health.usefulapi.io/mcp |
| Authorisation server | https://spruce-health.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://spruce-health.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/spruce-health/ |
| http (plaintext) | http://spruce-health.usefulapi.io/mcp | Inconclusive | 302 | http://spruce-health.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
sprucehealth_get_contact Get a contact ~71
One contact by Spruce contact id (entity_…): demographics, phones, emails, tags, custom and organization fields, integration links. GET /contacts/{contactId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The contact id (e.g. "entity_0E5QDGJC03000"). |
No output schema declared.
No examples provided.
sprucehealth_get_conversation Get a conversation ~53
One conversation by id (t_…). GET /conversations/{conversationId}.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | The conversation id (e.g. "t_0E5QDJJC03000"). |
No output schema declared.
No examples provided.
sprucehealth_get_conversation_item Get a conversation message ~67
One conversation item (message, note, call, voicemail…) by id (ti_…). GET /conversationItems/{conversationItemId}.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_item_id | string | yes | The conversation item id (e.g. "ti_0D4QABCC06000"). |
No output schema declared.
No examples provided.
sprucehealth_get_member Get an organization member ~61
One organization member (teammate, team or the organization) by id. GET /organization/members/{memberId}.
| Name | Type | Req | Description |
|---|---|---|---|
| member_id | string | yes | The member id (e.g. "entity_0D4QABCC06000"). |
No output schema declared.
No examples provided.
sprucehealth_get_organization Get the organization ~40
Your Spruce organization (id and name). The id is the owner/member id used by other objects. Good first call. GET /organization.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sprucehealth_get_phone_line Get a phone line ~57
One phone line by id (pd_…). GET /phonelines/{phonelineId}.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_line_id | string | yes | The phone line id (e.g. "pd_26RRC7PQ6JG00"). |
No output schema declared.
No examples provided.
sprucehealth_get_transcription Get a call or voicemail transcription ~74
The full transcription text and its summary (if any) for a transcription id (the transcriptionId on a call/voicemail attachment). Status pending/completed/failed/noSpeech. GET /transcriptions/{transcriptionId}.
| Name | Type | Req | Description |
|---|---|---|---|
| transcription_id | string | yes | The transcription id (from a conversation item's audio attachment). |
No output schema declared.
No examples provided.
sprucehealth_list_contact_conversations List a contact's conversations ~66
The conversations (secure, SMS/phone, email, fax…) associated with one contact. GET /contacts/{contactId}/conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The contact id (e.g. "entity_0E5QDGJC03000"). |
No output schema declared.
No examples provided.
sprucehealth_list_contact_fields List organization contact fields ~105
The organization-wide contact fields shown on every contact. Paged; totalCount included. GET /contacts/fields.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | integer | – | Results per page (1-500). Keep it small (e.g. 25-50) for long records: an oversized page is cut, but the Paging part with the cursor always stays whole. |
| pagination_token | string | – | The paginationToken from the previous page's reply (when hasMore is true). |
No output schema declared.
No examples provided.
sprucehealth_list_contact_integration_links List a contact's integration links ~74
Links between a contact and external systems (Elation, Hint, athena, custom): type, external id, url. GET /contacts/{contactId}/integrationlinks.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The contact id (e.g. "entity_0E5QDGJC03000"). |
No output schema declared.
No examples provided.
sprucehealth_list_contact_tags List contact tags ~108
All contact tags of the organization. Paged with hasMore/paginationToken; totalCount included. GET /contacts/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | integer | – | Results per page (1-500). Keep it small (e.g. 25-50) for long records: an oversized page is cut, but the Paging part with the cursor always stays whole. |
| pagination_token | string | – | The paginationToken from the previous page's reply (when hasMore is true). |
No output schema declared.
No examples provided.
sprucehealth_list_contacts List contacts ~136
Contacts of the organization (patients, professionals, clinics): name, date of birth, phones, emails, tags, custom fields, integration links. Paged with hasMore/paginationToken; totalCount included. Use sprucehealth_search_contacts to find someone. GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | integer | – | Results per page (1-500). Keep it small (e.g. 25-50) for long records: an oversized page is cut, but the Paging part with the cursor always stays whole. |
| pagination_token | string | – | The paginationToken from the previous page's reply (when hasMore is true). |
No output schema declared.
No examples provided.
sprucehealth_list_conversation_items List conversation messages ~222
The items (messages, internal notes, calls, voicemails, faxes, attachments with short-lived signed URLs) in one conversation. Order newest_first (default) or oldest_first; start_from = only items created after that time. Paged with hasMore/paginationToken; totalCount is a best-effort count. GET /conversations/{conversationId}/items.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | The conversation id (e.g. "t_0E5QDJJC03000"). |
| order | string | – | Order of the items (default newest_first). |
| page_size | integer | – | Results per page (1-200). Keep it small (e.g. 25-50) for long records: an oversized page is cut, but the Paging part with the cursor always stays whole. |
| pagination_token | string | – | The paginationToken from the previous page's reply (when hasMore is true). |
| start_from | string | – | Only items created after this RFC 3339 date-time (with zone). |
No output schema declared.
No examples provided.
sprucehealth_list_conversation_scheduled_messages List a conversation's scheduled messages ~70
Messages scheduled to be sent later in one conversation (read only; nothing is sent or cancelled). GET /conversations/{conversationId}/scheduledmessages.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | The conversation id (e.g. "t_0E5QDJJC03000"). |
No output schema declared.
No examples provided.
sprucehealth_list_conversation_tags List conversation tags ~104
All conversation tags of the organization. Paged; totalCount included. GET /conversations/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | integer | – | Results per page (1-500). Keep it small (e.g. 25-50) for long records: an oversized page is cut, but the Paging part with the cursor always stays whole. |
| pagination_token | string | – | The paginationToken from the previous page's reply (when hasMore is true). |
No output schema declared.
No examples provided.
sprucehealth_list_conversations List conversations ~203
Conversations of the organization (title, type, tags, archived, assignee, participants, last message time), ordered by creation or last message. With start_from, only conversations whose ordering time is at or after it (useful for 'what changed since…'). Eventually consistent. Paged; give start_from OR pagination_token, not both. GET /conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| order_by | string | – | Order by creation time or last message time (default last_message). |
| page_size | integer | – | Results per page (1-200). Keep it small (e.g. 25-50) for long records: an oversized page is cut, but the Paging part with the cursor always stays whole. |
| pagination_token | string | – | The paginationToken from the previous page's reply (when hasMore is true). |
| start_from | string | – | Only conversations whose ordering time is at or after this RFC 3339 date-time (with zone). |
No output schema declared.
No examples provided.
sprucehealth_list_internal_endpoints List internal endpoints ~43
The organization's own channels: Spruce phone and fax numbers, email addresses and Spruce Links, with their owner and members. GET /internalendpoints.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sprucehealth_list_members List organization members ~122
All members of the organization: teammates (name, email, admin, suspended), teams and the organization itself. Paged with hasMore/paginationToken; totalCount included. GET /organization/members.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | integer | – | Results per page (2-500). Keep it small (e.g. 25-50) for long records: an oversized page is cut, but the Paging part with the cursor always stays whole. |
| pagination_token | string | – | The paginationToken from the previous page's reply (when hasMore is true). |
No output schema declared.
No examples provided.
sprucehealth_list_phone_lines List phone lines ~31
All phone lines of the organization (id, name); totalCount included. GET /phonelines.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sprucehealth_list_read_receipts List a message's read receipts ~70
Who has read one conversation item and when they first read it (oldest first). GET /conversationItems/{conversationItemId}/readReceipts.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_item_id | string | yes | The conversation item id (e.g. "ti_0D4QABCC06000"). |
No output schema declared.
No examples provided.
sprucehealth_list_saved_messages List saved messages ~113
Saved message templates (private and organization-wide): title, text, internal/shared flags. Paged with hasMore/paginationToken. GET /savedmessages.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | integer | – | Results per page (1-500). Keep it small (e.g. 25-50) for long records: an oversized page is cut, but the Paging part with the cursor always stays whole. |
| pagination_token | string | – | The paginationToken from the previous page's reply (when hasMore is true). |
No output schema declared.
No examples provided.
sprucehealth_list_scheduled_messages List scheduled messages ~66
All messages scheduled to be sent from the organization (read only). Paged with hasMore/paginationToken; totalCount included. GET /scheduledmessages.
| Name | Type | Req | Description |
|---|---|---|---|
| pagination_token | string | – | The paginationToken from the previous page's reply (when hasMore is true). |
No output schema declared.
No examples provided.
sprucehealth_list_team_members List a team's members ~139
The members of one team (team ids come from sprucehealth_list_members, type 'team'). Paged. GET /teams/{teamId}/members.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | integer | – | Results per page (1-500). Keep it small (e.g. 25-50) for long records: an oversized page is cut, but the Paging part with the cursor always stays whole. |
| pagination_token | string | – | The paginationToken from the previous page's reply (when hasMore is true). |
| team_id | string | yes | The team id (e.g. "entity_0D4QABCC06000"). |
No output schema declared.
No examples provided.
sprucehealth_search_contacts Search contacts ~353
Find contacts by free text and/or filters (category, tags, name, phone, email, invite state, created time). Filters combine with AND; values inside one filter match ANY (tags can use all/none). Paged; totalCount with totalCountRelation (eq = exact, gte = lower bound). A read: POST /contacts/search changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Contact categories to include. |
| created_from | string | – | Only contacts added at or after this time (RFC 3339 with zone). |
| created_to | string | – | Only contacts added at or before this time (RFC 3339 with zone). |
| email_addresses | array | – | Email addresses. |
| family_name | string | – | Family (last) name. |
| free_text | string | – | Free-text query (name, phone, email…). |
| given_name | string | – | Given (first) name. |
| invite_states | array | – | Spruce account/invite state. |
| page_size | integer | – | Results per page (1-500). Keep it small (e.g. 25-50) for long records: an oversized page is cut, but the Paging part with the cursor always stays whole. |
| pagination_token | string | – | The paginationToken from the previous page's reply (when hasMore is true). |
| phone_numbers | array | – | Phone numbers, e.g. 2065551234 or +12065551234. |
| tags | array | – | Contact tag text values (the `value` of a tag from sprucehealth_list_contact_tags). |
| tags_match | string | – | How the tags combine: any (default), all, or none (exclude). |
No output schema declared.
No examples provided.
How do I install the Spruce Health MCP by usefulapi server?
Spruce Health MCP by usefulapi is a hosted endpoint at https://spruce-health.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · spruce-health.usefulapi.io
claude mcp add --transport http io-usefulapi-spruce-health 'https://spruce-health.usefulapi.io/mcp'
What is the Spruce Health MCP by usefulapi server?
Spruce Health MCP by usefulapi is listed in the public MCP registry as io.usefulapi/spruce-health. Read Spruce Health contacts, conversations, messages, phone lines and team members (read-only). This page covers its hosted endpoint (https://spruce-health.usefulapi.io/mcp).
Is the Spruce Health MCP by usefulapi server safe to use?
Spruce Health MCP by usefulapi scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Spruce Health MCP by usefulapi server expose?
Spruce Health MCP by usefulapi exposes 24 tools: sprucehealth_get_organization, sprucehealth_list_members, sprucehealth_get_member, sprucehealth_list_team_members, sprucehealth_list_contacts, and 19 more. Their descriptions and schemas cost roughly 2,448 tokens of context every time the server is loaded.
Does the Spruce Health MCP by usefulapi server require authentication?
Yes. Spruce Health MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Spruce Health MCP by usefulapi server still maintained?
Spruce Health MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.