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.

io.usefulapi/groove-hq

REMOTE · GROOVE-HQ.USEFULAPI.IO · SCANNED SEP 21

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

Available components

remote · groove-hq.usefulapi.io 86
0 this week 86 Trust /100
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 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 answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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 & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1333 tokens (~83/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 16 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
Install

How do I install the io.usefulapi/groove-hq MCP server?

io.usefulapi/groove-hq 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'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-usefulapi-groove-hq": {
      "url": "https://groove-hq.usefulapi.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-usefulapi-groove-hq": {
      "type": "http",
      "url": "https://groove-hq.usefulapi.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-usefulapi-groove-hq]
url = "https://groove-hq.usefulapi.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-groove-hq": {
      "type": "remote",
      "url": "https://groove-hq.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-usefulapi-groove-hq --url 'https://groove-hq.usefulapi.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-usefulapi-groove-hq:
    url: "https://groove-hq.usefulapi.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-usefulapi-groove-hq": {
      "Transport": "http",
      "Url": "https://groove-hq.usefulapi.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-usefulapi-groove-hq -t streamable-http -u 'https://groove-hq.usefulapi.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-usefulapi-groove-hq": {
      "type": "http",
      "url": "https://groove-hq.usefulapi.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

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 21 Sept 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 16 Sept 2026 15 Dec 2026 ECDSA 256 ECDSA-SHA256 63e3fc34b3fdea620ebd484b4e7a59ab
SANs: usefulapi.io, groove-hq.usefulapi.io, *.groove-hq.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 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 200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://groove-hq.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" 

Bearer realm="OAuth", resource_metadata="https://groove-hq.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Protected resource metadata

Document https://groove-hq.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://groove-hq.usefulapi.io/mcp
Authorisation server https://groove-hq.usefulapi.io

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 Verified 200
http (plaintext) http://groove-hq.usefulapi.io/mcp Inconclusive 401
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.

Common questions

What is the io.usefulapi/groove-hq MCP server?

io.usefulapi/groove-hq is an MCP server 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 io.usefulapi/groove-hq MCP server safe to use?

io.usefulapi/groove-hq scores 86 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 io.usefulapi/groove-hq MCP server expose?

io.usefulapi/groove-hq 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 io.usefulapi/groove-hq MCP server require authentication?

Yes. io.usefulapi/groove-hq 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 io.usefulapi/groove-hq MCP server still maintained?

io.usefulapi/groove-hq is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.