Groove MCP by usefulapi
io.usefulapi/groove-hqusefulapi.iostreamable-httpv1.40.4Scanned
Read Groove shared-inbox conversations, contacts, agents and tags; close, assign, snooze and tag.
16 tools: 7 can delete or cancel things and 9 only read.
- Reads private data · 7
- Reads text others write · 6
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
7 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Groove MCP by usefulapi can do
The Groove MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 16 tools. It can delete or cancel things (7 tools: groove_close_conversation, groove_open_conversation, groove_snooze_conversation, groove_star_conversation and 3 more). 9 tools only read.
7 tools read private data (groove_list_conversations, groove_get_conversation, groove_list_contacts and 4 more); 6 tools bring in text other people can write (groove_list_conversations, groove_get_conversation, groove_get_contact and 3 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
16 tools
Deletes or cancels 7Claude Code: deny
groove_assign_conversationASSIGNS a conversation to an agent and/or team.No findings
Why it is in this group
- The name "groove_assign_conversation" says "assign": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it ASSIGNS a conversation to an agent and/or team. Pass agent_id, team_id, or both (at least one is required). Groove GraphQL: conversationAssign.
Annotations the server declares
- title: Assign conversation
- destructiveHint: true
groove_close_conversationCLOSES a conversation (marks it resolved) in the shared inbox.No findings
Why it is in this group
- The name "groove_close_conversation" says "close": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it CLOSES a conversation (marks it resolved) in the shared inbox. Groove GraphQL: conversationClose.
Annotations the server declares
- title: Close conversation
- destructiveHint: true
groove_open_conversationRE-OPENS a closed/snoozed conversation in the shared inbox.No findings
Why it is in this group
- The name "groove_open_conversation" says "open": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it RE-OPENS a closed/snoozed conversation in the shared inbox. Groove GraphQL: conversationOpen.
Annotations the server declares
- title: Open conversation
- destructiveHint: true
groove_snooze_conversationSNOOZES a conversation until the given time (ISO8601) — it drops out of the inbox until then.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it SNOOZES a conversation until the given time (ISO8601) — it drops out of the inbox until then. Groove GraphQL: conversationSnooze.
Annotations the server declares
- title: Snooze conversation
- destructiveHint: true
groove_star_conversationSTARS a conversation (flags it for attention) in the shared inbox.No findings
Why it is in this group
- The name "groove_star_conversation" says "star": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it STARS a conversation (flags it for attention) in the shared inbox. Groove GraphQL: conversationStar.
Annotations the server declares
- title: Star conversation
- destructiveHint: true
groove_tag_conversationADDS tags (by tag id) to a conversation.No findings
Why it is in this group
- The description's first verb is "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it ADDS tags (by tag id) to a conversation. Use groove_list_tags to find tag ids. Groove GraphQL: conversationTag.
Annotations the server declares
- title: Tag conversation
- destructiveHint: true
groove_untag_conversationREMOVES tags (by tag id) from a conversation.No findings
Why it is in this group
- The description's first verb is "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it REMOVES tags (by tag id) from a conversation. Use groove_list_tags to find tag ids. Groove GraphQL: conversationUntag.
Annotations the server declares
- title: Untag conversation
- destructiveHint: true
Only reads 9Show 9 read-only tools
groove_get_contactGet a single contact by id — name, email, role, type, and conversation count.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "groove_get_contact" says "get": a word for reading.
What it can reach
- private-dataThe name "groove_get_contact" says "get" and "contact": it reads contacts.
- private-dataThe description's first sentence says "get" and "contact": it reads contacts.
- untrusted-inputThe description's first sentence says "get" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it Get a single contact by id — name, email, role, type, and conversation count. Groove GraphQL: contact(contactId: ID!).
Annotations the server declares
- title: Get contact
- readOnlyHint: true
groove_get_conversationGet a single conversation by id — subject, state, assignment, contact, channel, counts, and tags.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "groove_get_conversation" says "get": a word for reading.
What it can reach
- private-dataThe name "groove_get_conversation" says "get" and "conversation": it reads messages.
- private-dataThe description's first sentence says "get" and "conversation": it reads messages.
- untrusted-inputThe name "groove_get_conversation" says "get" and "conversation": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "get" and "conversation": it reads messages, which other people can write.
Description, as the server wrote it Get a single conversation by id — subject, state, assignment, contact, channel, counts, and tags. Groove GraphQL: conversation(id: ID!).
Annotations the server declares
- title: Get conversation
- readOnlyHint: true
groove_list_agentsList agents (support staff / users) in the account, with role and state.No findings
Why it is in this group
- The name "groove_list_agents" says "list": a word for reading.
Description, as the server wrote it List agents (support staff / users) in the account, with role and state. Paginate with first/after. Groove GraphQL: agents.
Annotations the server declares
- title: List agents
- readOnlyHint: true
groove_list_channelsList channels (mailboxes / inboxes — email, chat, etc.) configured in the account.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "groove_list_channels" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "mailbox": it reads mail.
- untrusted-inputThe description's first sentence says "list" and "mailbox": it reads inbound email, which other people can write.
Description, as the server wrote it List channels (mailboxes / inboxes — email, chat, etc.) configured in the account. Paginate with first/after. Groove GraphQL: channels.
Annotations the server declares
- title: List channels
- readOnlyHint: true
groove_list_contactsList customer contacts (people who wrote in).Reads private dataNo findings
Why it is in this group
- The name "groove_list_contacts" says "list": a word for reading.
What it can reach
- private-dataThe name "groove_list_contacts" says "list" and "contact": it reads contacts.
- private-dataThe description's first sentence says "list" and "contact": it reads contacts.
Description, as the server wrote it List customer contacts (people who wrote in). Optional keyword search over name/email; paginate with first/after. Groove GraphQL: contacts(keywords: String).
Annotations the server declares
- title: List contacts
- readOnlyHint: true
groove_list_conversationsList support conversations (tickets) in the shared inbox, with rich filters.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "groove_list_conversations" says "list": a word for reading.
What it can reach
- private-dataThe name "groove_list_conversations" says "list" and "conversation": it reads messages.
- private-dataThe description's first sentence says "list" and "conversation": it reads messages.
- private-dataThe input names a folder (input.folder_id), and the tool reads: it reads files.
- untrusted-inputThe name "groove_list_conversations" says "list" and "conversation": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "conversation": it reads messages, which other people can write.
Description, as the server wrote it 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).
Annotations the server declares
- title: List conversations
- readOnlyHint: true
groove_list_foldersList folders (saved views / smart folders that group conversations), with conversation counts.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "groove_list_folders" says "list": a word for reading.
What it can reach
- private-dataThe name "groove_list_folders" says "list" and "folder": it reads files.
- private-dataThe description's first sentence says "list" and "folder": it reads files.
- untrusted-inputThe description's first sentence says "list" and "conversation": it reads messages, which other people can write.
Description, as the server wrote it List folders (saved views / smart folders that group conversations), with conversation counts. Paginate with first/after. Groove GraphQL: folders.
Annotations the server declares
- title: List folders
- readOnlyHint: true
groove_list_tagsList tags defined in the account (id, name, color) — use tag ids with the tag/untag write tools.No findings
Why it is in this group
- The name "groove_list_tags" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List tags
- readOnlyHint: true
groove_list_teamsList teams (groups of agents that conversations can be assigned to).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "groove_list_teams" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "conversation": it reads messages.
- untrusted-inputThe description's first sentence says "list" and "conversation": it reads messages, which other people can write.
Description, as the server wrote it List teams (groups of agents that conversations can be assigned to). Paginate with first/after. Groove GraphQL: teams.
Annotations the server declares
- title: List teams
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data7
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 7 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://groove-hq.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://groove-hq.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 7 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://groove-hq.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://groove-hq.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http groove-hq https://groove-hq.usefulapi.io/mcpclaude mcp add --transport http groove-hq https://groove-hq.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__groove-hq__groove_list_conversations",
"mcp__groove-hq__groove_get_conversation",
"mcp__groove-hq__groove_list_contacts",
"mcp__groove-hq__groove_get_contact",
"mcp__groove-hq__groove_list_agents",
"mcp__groove-hq__groove_list_channels",
"mcp__groove-hq__groove_list_tags",
"mcp__groove-hq__groove_list_folders",
"mcp__groove-hq__groove_list_teams"
],
"ask": [],
"deny": [
"mcp__groove-hq__groove_close_conversation",
"mcp__groove-hq__groove_open_conversation",
"mcp__groove-hq__groove_snooze_conversation",
"mcp__groove-hq__groove_star_conversation",
"mcp__groove-hq__groove_assign_conversation",
"mcp__groove-hq__groove_tag_conversation",
"mcp__groove-hq__groove_untag_conversation"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as groove-hq. Review it before you use it.
Capability tags behind 7 rules
- mcp__groove-hq__groove_list_conversations private-data, untrusted-input
- mcp__groove-hq__groove_get_conversation private-data, untrusted-input
- mcp__groove-hq__groove_list_contacts private-data
- mcp__groove-hq__groove_get_contact private-data, untrusted-input
- mcp__groove-hq__groove_list_channels private-data, untrusted-input
- mcp__groove-hq__groove_list_folders private-data, untrusted-input
- mcp__groove-hq__groove_list_teams private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/groove-hq/verify?hash=eea994d79689ef6fdbac111df89d37763ff58faf143e0a3a419e697a91d904c1" | jq -e '.changed == false'Pinned hash eea994d79689, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/groove-hq/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/groove-hq)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Groove MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Groove MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 16 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Groove MCP by usefulapi delete data?
- Yes. 7 tools can delete, cancel or revoke something: groove_close_conversation, groove_open_conversation, groove_snooze_conversation, groove_star_conversation, groove_assign_conversation, groove_tag_conversation and 1 more.
Can the Groove MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Groove MCP by usefulapi have?
- 16 tools: 7 destructive, 9 read. groove_close_conversation, groove_open_conversation, groove_snooze_conversation, groove_star_conversation, groove_assign_conversation, groove_tag_conversation, groove_untag_conversation, groove_list_conversations and 8 more.
Does the Groove MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Groove MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Groove MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.