io.usefulapi/groove-hq

REMOTE · GROOVE-HQ.USEFULAPI.IO · SCANNED AUG 3

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

Available components

+4 this week 74 74 Trust /100

Trust breakdown (6 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 →

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 not yet verified: we couldn't determine whether a plaintext access path exists. 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

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability81

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 Management23

Stability observed for 7 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

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · groove-hq.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http io-usefulapi-groove-hq 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"

// 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.

3 Aug 26 +1

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

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +2
- 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 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
27 Jul 26 +58
- 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 12

First indexed and scored.

Show 7 earlier entries Hide earlier entries

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 3 Aug 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	19 Jul 2026	17 Oct 2026	ECDSA 256	ECDSA-SHA256	8c3c87f11c25f8c13f4b3037d4a5fe8
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

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

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.

Tool Tokens

groove_assign_conversation 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.

Input Output Examples

Name	Type	Req	Description
agent_id	string	—	Agent id to assign the conversation to.
id	string	yes	The conversation id (opaque GraphQL ID).
team_id	string	—	Team id to assign the conversation to.

No output schema declared.

No examples provided.

groove_close_conversation Close conversation ~46

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	The conversation id (opaque GraphQL ID).

No output schema declared.

No examples provided.

groove_get_contact Get contact ~60

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	The Groove object id (opaque GraphQL ID, passed as a string).

No output schema declared.

No examples provided.

groove_get_conversation Get conversation ~63

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	The Groove object id (opaque GraphQL ID, passed as a string).

No output schema declared.

No examples provided.

groove_list_agents List agents ~82

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

Input Output Examples

Name	Type	Req	Description
after	string	—	Relay pagination cursor — pass the previous page's `endCursor` to get the next page.
first	integer	—	How many records to return (Relay pagination `first`).

No output schema declared.

No examples provided.

groove_list_channels List channels ~85

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

Input Output Examples

Name	Type	Req	Description
after	string	—	Relay pagination cursor — pass the previous page's `endCursor` to get the next page.
first	integer	—	How many records to return (Relay pagination `first`).

No output schema declared.

No examples provided.

groove_list_contacts 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).

Input Output Examples

Name	Type	Req	Description
after	string	—	Relay pagination cursor — pass the previous page's `endCursor` to get the next page.
first	integer	—	How many records to return (Relay pagination `first`).
keywords	string	—	Keyword search across contacts (name/email).

No output schema declared.

No examples provided.

groove_list_conversations 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).

Input Output Examples

Name	Type	Req	Description
after	string	—	Relay pagination cursor — pass the previous page's `endCursor` to get the next page.
assigned	boolean	—	If set, filter to assigned (true) or unassigned (false) conversations.
channel_id	string	—	Filter to a single channel (mailbox) id.
first	integer	—	How many records to return (Relay pagination `first`).
folder_id	string	—	Filter to a single folder id.
keywords	string	—	Full-text keyword search across conversations.
starred	boolean	—	If set, filter to starred (true) or unstarred (false) conversations.
state	string	—	Filter by conversation state.
tag_name	string	—	Filter to conversations carrying this tag name.

No output schema declared.

No examples provided.

groove_list_folders List folders ~82

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

Input Output Examples

Name	Type	Req	Description
after	string	—	Relay pagination cursor — pass the previous page's `endCursor` to get the next page.
first	integer	—	How many records to return (Relay pagination `first`).

No output schema declared.

No examples provided.

groove_list_tags 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.

Input Output Examples

Name	Type	Req	Description
after	string	—	Relay pagination cursor — pass the previous page's `endCursor` to get the next page.
first	integer	—	How many records to return (Relay pagination `first`).

No output schema declared.

No examples provided.

groove_list_teams List teams ~79

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

Input Output Examples

Name	Type	Req	Description
after	string	—	Relay pagination cursor — pass the previous page's `endCursor` to get the next page.
first	integer	—	How many records to return (Relay pagination `first`).

No output schema declared.

No examples provided.

groove_open_conversation Open conversation ~48

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	The conversation id (opaque GraphQL ID).

No output schema declared.

No examples provided.

groove_snooze_conversation Snooze conversation ~100

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	The conversation id (opaque GraphQL ID).
until	string	yes	When to un-snooze, as an ISO8601 timestamp (e.g. 2026-08-01T09:00:00Z).

No output schema declared.

No examples provided.

groove_star_conversation Star conversation ~47

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	The conversation id (opaque GraphQL ID).

No output schema declared.

No examples provided.

groove_tag_conversation Tag conversation ~68

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	The conversation id (opaque GraphQL ID).
tag_ids	array	yes	Tag ids to add to the conversation.

No output schema declared.

No examples provided.

groove_untag_conversation Untag conversation ~72

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	The conversation id (opaque GraphQL ID).
tag_ids	array	yes	Tag ids to remove from the conversation.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	12
27 Jul	70
28 Jul	71
29 Jul	72
30 Jul	70
31 Jul	72
1 Aug	73
2 Aug	73
3 Aug	74