Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Groove MCP by usefulapi

REMOTE · GROOVE-HQ.USEFULAPI.IO

Read Groove shared-inbox conversations, contacts, agents and tags; close, assign, snooze and tag.

−59 this week 18 Trust /100

Last scanned (10 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

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.

  • 2 Nov 26 −62
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 31 Oct 26 +3
    • Authorization: partial → pass ▲ security
    • MCP protocol: fail → pass ▲ functional
    • New prompt “assign_conversations_to_an_agent_or_team” functional
    • New prompt “close_reopen_snooze_or_star_conversations” functional
    • New prompt “find_open_conversations_that_nobody_owns” functional
    • New prompt “look_up_a_customer_and_how_often_they_wrote_in” functional
    • New prompt “search_conversations_by_keyword_or_tag” functional
    • New prompt “tag_or_untag_conversations” functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • Server version: 1.31.0 → 1.33.0 functional
    • Server version: 1.30.0 → 1.31.0 functional
    • Server version: 1.29.2 → 1.30.0 functional
  • 30 Oct 26 0
    • Server version: 1.29.1 → 1.29.2 functional
    • Server version: 1.29.0 → 1.29.1 functional
  • 29 Oct 26 0
    • Server version: 1.28.0 → 1.29.0 functional
    • Server version: 1.27.0 → 1.28.0 functional
  • 28 Oct 26 0
    • Server version: 1.25.0 → 1.27.0 functional
  • 27 Oct 26 0
    • Server version: 1.24.0 → 1.25.0 functional
  • 25 Oct 26 0
    • Server version: 1.23.0 → 1.24.0 functional
    • Server version: 1.22.0 → 1.23.0 functional
    • Server version: 1.21.3 → 1.22.0 functional
    • Server version: 1.21.0 → 1.21.3 functional
  • 24 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 1.20.0 → 1.21.0 functional
    • Server version: 1.19.0 → 1.20.0 functional
    • Server version: 1.17.0 → 1.19.0 functional
Diagnostics

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 5 Nov 2026 · Probed https://groove-hq.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 groove-hq.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://groove-hq.usefulapi.io/mcp Redirected 302 https://usefulapi.io/groove-hq/
http (plaintext) http://groove-hq.usefulapi.io/mcp Inconclusive 302 http://groove-hq.usefulapi.io/mcp
MCP tools · 16 exposed · ~1,333 tokens

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 →

Tool Tokens
groove_assign_conversation ~90

ASSIGNS a conversation to an agent and/or team. Pass agent_id, team_id, or both (at least one is required). Groove GraphQL: conversationAssign.

NameTypeReqDescription
agent_idstring–Agent id to assign the conversation to.
idstringyesThe conversation id (opaque GraphQL ID).
team_idstring–Team id to assign the conversation to.

No output schema declared.

No examples provided.

groove_close_conversation ~46

CLOSES a conversation (marks it resolved) in the shared inbox. Groove GraphQL: conversationClose.

NameTypeReqDescription
idstringyesThe conversation id (opaque GraphQL ID).

No output schema declared.

No examples provided.

groove_get_contact ~60

Get a single contact by id — name, email, role, type, and conversation count. Groove GraphQL: contact(contactId: ID!).

NameTypeReqDescription
idstringyesThe Groove object id (opaque GraphQL ID, passed as a string).

No output schema declared.

No examples provided.

groove_get_conversation ~63

Get a single conversation by id — subject, state, assignment, contact, channel, counts, and tags. Groove GraphQL: conversation(id: ID!).

NameTypeReqDescription
idstringyesThe Groove object id (opaque GraphQL ID, passed as a string).

No output schema declared.

No examples provided.

groove_list_agents ~82

List agents (support staff / users) in the account, with role and state. Paginate with first/after. Groove GraphQL: agents.

NameTypeReqDescription
afterstring–Relay pagination cursor — pass the previous page's `endCursor` to get the next page.
firstinteger–How many records to return (Relay pagination `first`).

No output schema declared.

No examples provided.

groove_list_channels ~85

List channels (mailboxes / inboxes — email, chat, etc.) configured in the account. Paginate with first/after. Groove GraphQL: channels.

NameTypeReqDescription
afterstring–Relay pagination cursor — pass the previous page's `endCursor` to get the next page.
firstinteger–How many records to return (Relay pagination `first`).

No output schema declared.

No examples provided.

groove_list_contacts ~98

List customer contacts (people who wrote in). Optional keyword search over name/email; paginate with first/after. Groove GraphQL: contacts(keywords: String).

NameTypeReqDescription
afterstring–Relay pagination cursor — pass the previous page's `endCursor` to get the next page.
firstinteger–How many records to return (Relay pagination `first`).
keywordsstring–Keyword search across contacts (name/email).

No output schema declared.

No examples provided.

groove_list_conversations ~222

List support conversations (tickets) in the shared inbox, with rich filters. Filter by state, channel_id, folder_id, tag_name, assigned, starred, or keywords; paginate with first/after. Groove GraphQL: conversations(filter: ConversationFilter).

NameTypeReqDescription
afterstring–Relay pagination cursor — pass the previous page's `endCursor` to get the next page.
assignedboolean–If set, filter to assigned (true) or unassigned (false) conversations.
channel_idstring–Filter to a single channel (mailbox) id.
firstinteger–How many records to return (Relay pagination `first`).
folder_idstring–Filter to a single folder id.
keywordsstring–Full-text keyword search across conversations.
starredboolean–If set, filter to starred (true) or unstarred (false) conversations.
statestring–Filter by conversation state.
tag_namestring–Filter to conversations carrying this tag name.

No output schema declared.

No examples provided.

groove_list_folders ~82

List folders (saved views / smart folders that group conversations), with conversation counts. Paginate with first/after. Groove GraphQL: folders.

NameTypeReqDescription
afterstring–Relay pagination cursor — pass the previous page's `endCursor` to get the next page.
firstinteger–How many records to return (Relay pagination `first`).

No output schema declared.

No examples provided.

groove_list_tags ~91

List tags defined in the account (id, name, color) — use tag ids with the tag/untag write tools. Paginate with first/after. Groove GraphQL: tags.

NameTypeReqDescription
afterstring–Relay pagination cursor — pass the previous page's `endCursor` to get the next page.
firstinteger–How many records to return (Relay pagination `first`).

No output schema declared.

No examples provided.

groove_list_teams ~79

List teams (groups of agents that conversations can be assigned to). Paginate with first/after. Groove GraphQL: teams.

NameTypeReqDescription
afterstring–Relay pagination cursor — pass the previous page's `endCursor` to get the next page.
firstinteger–How many records to return (Relay pagination `first`).

No output schema declared.

No examples provided.

groove_open_conversation ~48

RE-OPENS a closed/snoozed conversation in the shared inbox. Groove GraphQL: conversationOpen.

NameTypeReqDescription
idstringyesThe conversation id (opaque GraphQL ID).

No output schema declared.

No examples provided.

groove_snooze_conversation ~100

SNOOZES a conversation until the given time (ISO8601) — it drops out of the inbox until then. Groove GraphQL: conversationSnooze.

NameTypeReqDescription
idstringyesThe conversation id (opaque GraphQL ID).
untilstringyesWhen to un-snooze, as an ISO8601 timestamp (e.g. 2026-08-01T09:00:00Z).

No output schema declared.

No examples provided.

groove_star_conversation ~47

STARS a conversation (flags it for attention) in the shared inbox. Groove GraphQL: conversationStar.

NameTypeReqDescription
idstringyesThe conversation id (opaque GraphQL ID).

No output schema declared.

No examples provided.

groove_tag_conversation ~68

ADDS tags (by tag id) to a conversation. Use groove_list_tags to find tag ids. Groove GraphQL: conversationTag.

NameTypeReqDescription
idstringyesThe conversation id (opaque GraphQL ID).
tag_idsarrayyesTag ids to add to the conversation.

No output schema declared.

No examples provided.

groove_untag_conversation ~72

REMOVES tags (by tag id) from a conversation. Use groove_list_tags to find tag ids. Groove GraphQL: conversationUntag.

NameTypeReqDescription
idstringyesThe conversation id (opaque GraphQL ID).
tag_idsarrayyesTag ids to remove from the conversation.

No output schema declared.

No examples provided.

Install

How do I install the Groove MCP by usefulapi server?

Groove MCP by usefulapi is a hosted endpoint at https://groove-hq.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 · groove-hq.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-groove-hq 'https://groove-hq.usefulapi.io/mcp'
Common questions

What is the Groove MCP by usefulapi server?

Groove MCP by usefulapi is listed in the public MCP registry as io.usefulapi/groove-hq. Read Groove shared-inbox conversations, contacts, agents and tags; close, assign, snooze and tag. This page covers its hosted endpoint (https://groove-hq.usefulapi.io/mcp).

Is the Groove MCP by usefulapi server safe to use?

Groove MCP by usefulapi scores 18 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 Groove MCP by usefulapi server expose?

Groove MCP by usefulapi exposes 16 tools: groove_list_conversations, groove_get_conversation, groove_list_contacts, groove_get_contact, groove_list_agents, and 11 more. Their descriptions and schemas cost roughly 1,333 tokens of context every time the server is loaded.

Does the Groove MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Groove MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Groove MCP by usefulapi server still maintained?

Groove MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.