# Mentio (remote · mcp.mentio.dev) Social listening for agents: brand mentions across 16 platforms, scored for relevance and intent - Trust score: 87/100 (high trust) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `mcp.mentio.dev`: 87/100 (this document), [markdown](https://verifymcp.io/servers/dev-mentio-mcp/mcp.md), [page](https://verifymcp.io/servers/dev-mentio-mcp/mcp) ## Channel facts - Endpoint: `https://mcp.mentio.dev/mcp` - Transports: `streamable-http` - Auth: `required` - Version: `1.0.0` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Endpoint Security**: 81/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - 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. - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC is configured correctly; the domain's records validate against the full chain to the root. - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 77/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 15416 tokens (~237/item across 65 items; 61 tools + 4 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 100/100 - No destabilizing schema changes in the last 30 days. - **Tool Coverage**: 98/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 93% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - All 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. - An AI judge read all 63 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 60/100 - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. ## Install ### How do I install the Mentio MCP server? Mentio is a hosted endpoint at https://mcp.mentio.dev/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. ### Claude ```bash claude mcp add --transport http dev-mentio-mcp 'https://mcp.mentio.dev/mcp' ``` ### Cursor ```json { "mcpServers": { "dev-mentio-mcp": { "url": "https://mcp.mentio.dev/mcp" } } } ``` ### VS Code ```json { "servers": { "dev-mentio-mcp": { "type": "http", "url": "https://mcp.mentio.dev/mcp" } } } ``` ### Codex ```toml [mcp_servers.dev-mentio-mcp] url = "https://mcp.mentio.dev/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "dev-mentio-mcp": { "type": "remote", "url": "https://mcp.mentio.dev/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add dev-mentio-mcp --url 'https://mcp.mentio.dev/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: dev-mentio-mcp: url: "https://mcp.mentio.dev/mcp" ``` ### Netclaw ```json { "McpServers": { "dev-mentio-mcp": { "Transport": "http", "Url": "https://mcp.mentio.dev/mcp" } } } ``` ### Vellum ```bash assistant mcp add dev-mentio-mcp -t streamable-http -u 'https://mcp.mentio.dev/mcp' ``` ### Other ```json { "mcpServers": { "dev-mentio-mcp": { "type": "http", "url": "https://mcp.mentio.dev/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-05 (score 87, +1) - [security] Stability: 0.97 → pass ### 2026-11-04 (score 86, −1) - [functional] Stability: pass → 0.97 ### 2026-11-03 (score 87, +1) - [security] Stability: 0.97 → pass ### 2026-11-01 (score 86, +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. ### 2026-10-30 (score 85, +1) No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-28 (score 84, +1) No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-26 (score 83, +1) No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-24 (score 82, +1) No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes. ## MCP tools (61) ### `list_segments` (~124 tokens) List segments Your saved audience segments (named filters such as "Influencers" or "Switch prospects"), each with the number of people in it right now, plus presets you can save with create_segment. Pass a segment id to list_people to see its members. With groupId, the segments saved in that keyword group, counted over its own people. Input parameters: - `groupId` (string): Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, mute, merges, activities and segments. Omit for the whole workspace. ### `create_segment` (~152 tokens) Create segment Save an audience segment: a name plus a filter (platforms, tags, follower range, minimum mentions or negatives, intents seen, keyword kinds mentioned or never mentioned, first seen within N days, linkHosts they have shared a link to). Evaluated on every read, never materialized. With groupId the segment belongs to that keyword group and is only listed there. Input parameters: - `description` (string) - `filter` (object) - `groupId` (string): Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, mute, merges, activities and segments. Omit for the whole workspace. - `name` (string, required) ### `update_segment` (~126 tokens) Update segment Rename, describe or refilter a saved segment. `filter` replaces the whole filter. A segment saved in a keyword group is found with that groupId. Input parameters: - `description` (string) - `filter` (object): Replaces the whole filter. - `groupId` (string): Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, mute, merges, activities and segments. Omit for the whole workspace. - `id` (string, required): Segment id (seg_...) - `name` (string) ### `delete_segment` (~97 tokens) Delete segment Delete a saved segment. Nobody in it is affected. A segment saved in a keyword group is found with that groupId. Input parameters: - `groupId` (string): Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, mute, merges, activities and segments. Omit for the whole workspace. - `id` (string, required): Segment id (seg_...), from list_segments ### `list_views` (~46 tokens) List views Your saved views (named filters over mentions such as "Negative about us" or "Needs a reply"). Pass a view id as viewId to search_mentions to read exactly what it selects. ### `create_view` (~157 tokens) Create view Save a view: a name plus a filter in the vocabulary of search_mentions (keywords or keyword kinds, platforms, status, relevant, sentiments, intents, languages, author countries, author tags, follower range, replies, link hosts, automated, organization, free text), lists any-of, `not` lists none-of, every condition ANDed, plus anyOf for OR: groups of those conditions, at least one of which must hold. Nothing is materialized: the view selects whatever matches when it is read. Input parameters: - `description` (string): What the view is for, shown under its name. - `filter` (object): The filter; empty selects every mention. - `name` (string, required): Unique per workspace, case-insensitive. ### `update_view` (~64 tokens) Update view Rename, describe or refilter a saved view. `filter` replaces the whole filter. Input parameters: - `description` (string) - `filter` (object): Replaces the whole filter. - `id` (string, required): View id (vw_...) - `name` (string) ### `delete_view` (~30 tokens) Delete view Delete a saved view. No mention is affected. Input parameters: - `id` (string, required): View id (vw_...) ### `list_groups` (~86 tokens) List groups The keyword groups of the workspace, the default first: how keywords are grouped (a customer, a campaign, a product). A term may be tracked once per group; every keyword belongs to one; get_usage_breakdown by=group says what each cost. externalId finds the group carrying your own id. Input parameters: - `externalId` (string): Only the group carrying exactly this externalId. ### `get_group` (~33 tokens) Get group One keyword group by id, with how many keywords it holds. Input parameters: - `id` (string, required): Group id (grp_...) ### `create_group` (~279 tokens) Create group Create a keyword group: a name (unique per workspace), optionally your own id for it (externalId, unique too, a customer id say), and optionally its own company description (context: who the business is, what it sells, for whom), which the classifier reads in place of the whole workspace profile (guidelines and competitors included) for this group's keywords, so a rule for the group goes in that text. One group per customer with its description is how a reseller gets each customer judged as itself. Then pass its id as groupId to add_keyword. Input parameters: - `context`: What the classifier reads as "the company" for this group's keywords, in place of the WHOLE workspace profile, its relevance guidelines and competitor list included (at most 4000 characters): who the… - `externalId`: Your own id for the group (a customer id, say). Unique per workspace; find the group by it with GET /v1/groups?externalId=. - `name` (string, required): The group's name: a customer, a campaign, a product. Unique per workspace. ### `update_group` (~186 tokens) Update group Rename a keyword group, change your id for it (externalId, null clears) or its company description (context, null clears: the workspace profile applies again; new mentions are judged with it at once). The default group can be renamed but takes no description: it is the workspace itself and reads the company profile (update_company). Input parameters: - `context`: Replaces the group's company description; null clears it (the workspace profile applies again). New mentions are judged with it at once; old ones are not rescored. Not on the default group (400 defau… - `externalId`: Replaces your id for the group; null clears it. - `id` (string, required): Group id (grp_...) - `name` (string): The group's name: a customer, a campaign, a product. Unique per workspace. ### `delete_group` (~55 tokens) Delete group Delete a keyword group and EVERY keyword in it (each as delete_keyword does: its mentions go with it). The default group cannot be deleted. Says how many keywords went. Input parameters: - `id` (string, required): Group id (grp_...) ### `search_mentions` (~2437 tokens) Search mentions Search tracked mentions for your organization. Filter by keyword, platform, status (open, ignored, done), relevant, minimum relevance, minimum confidence (0 to 1), sentiment, intent, free text (q, the post text or the author name), time range (ISO 8601), one person (personId from list_people), assignee (assigneeId), author reach (minFollowers, maxFollowers), engagement the platform reported (minLikes, minReposts, minReplies, minQuotes, minViews, minBookmarks; a post without the count never passes), review stars (ratings, or notRatings to leave some out), author tags (tags, any-of), the hosts a post links to (linkHosts, any-of, a host or any subdomain of it), Reddit subreddits (subreddits or notSubreddits, names without the r/), replies against top-level posts (isReply), posts against comments (kind: post or comment), whether the post reads as machine-made (automated=true for the bots, false for the rest), where the author is (countries, or notCountries to leave some out, lowercase ISO 3166-1 alpha-2 codes like in, us, de, as the classifier read the profile and the post; an unknown country passes notCountries), whether the author is a company or organization (organization=true for companies, brands and organizations, false for people), the language of the post (languages or notLanguages, ISO 639-1), an alert rule's whole filter (alertId, the same mentions the rule would send), a saved view's filter (viewId, from list_views, ANDed with the rest), the kind of keyword that matched (keywordKinds: brand, competitor, topic), or the keyword's group (groupIds, or notGroupIds to leave groups out; ids from list_groups). Every filter is ANDed; for OR, anyOf takes up to 10 groups of the same conditions (an object each, all its conditions ANDed) and keeps a mention when at least one group holds, on top of the rest: anyOf=[{platforms:["reddit"],sentiments:["negative"]},{intents:["buy_intent"]}]. Snoozed mentions are hidden unless snoozed=true. sort="newest" (default) or "priority… Input parameters: - `alertId` (string): Apply an alert rule's filter (an id from GET /v1/alerts) on top of the other filters: the same mentions the rule would send, for a feed-shaped export or a preview. Unknown ids are a 404. - `anyOf` (array): OR across groups: a mention passes when it meets every condition of at least one group (1 to 10 groups). The other conditions still apply to every mention: the whole filter is (other conditions) AND… - `assigneeId` (string): Only mentions assigned to this workspace member (user id). - `automated` (boolean): true: only mentions that read as machine-made (a bot account, a scheduled or templated post, AI-written text); false: only the rest, mentions judged before this existed included. Omitted: everything. - `countries` (array): Only posts whose author is in any of these countries (ISO 3166-1 alpha-2: us, in, de), as the classifier read the author's profile and the post. A post whose country is unknown never passes. - `excludeAuthors` (array): Hide these authors: display names, handles or profile URLs. Repeatable, or one comma-separated value. - `groupIds` (array): Only matches of keywords in any of these groups (grp_...). Repeatable, or comma-separated. - `includeDuplicates` (boolean): true: list cross-posts (a mention whose duplicateOf is set) as mentions of their own. By default each is listed only in its original's duplicates. - `includeHidden` (boolean): true: include mentions their keyword's display lists hide (a language or country it does not show), hidden by default. - `includeMuted` (boolean): true: include mentions by people you muted, hidden by default: muted for the workspace, or for the mention's own keyword group. - `intent` (string): Only mentions carrying this intent or topic tag (buy_intent, question, complaint, praise, comparison, churn_intent, bug_report, pricing, hiring, event, promotional, testimonial, industry_insight, lau… - `intents` (array): Only mentions carrying any of these intent or topic tags. - `isReply` (boolean): true: only replies and comments (posts answering another post); false: only top-level posts. Omitted: both. - `keywordId` (string): Only matches of this keyword. - `keywordIds` (array): Only matches of any of these keywords. - `keywordKinds` (array): Only matches of keywords of any of these kinds: brand, competitor, topic. Repeatable, or comma-separated. - `kind` (string): Only posts (post), only comments (comment) or only GitHub repository events (repository). Omitted: all. - `languages` (array): Only posts in any of these languages (ISO 639-1: en, es, de). A post whose language is unknown never passes. - `limit` (integer): How many mentions to return, 1 to 100. Default 10: narrow the filters before asking for more. - `linkHosts` (array): Only posts linking to any of these hosts, the host itself or a subdomain of it (octolens.com also matches blog.octolens.com). Repeatable, or comma-separated. - `maxFollowers` (integer): Only authors with at most this many followers. Unknown reach never passes. - `minBookmarks` (integer): Only posts with at least this many bookmarks (saves), as the platform reported them when the post was found. A post without that count never passes. - `minConfidence` (number): Only mentions whose classifier confidence is at least this, 0 to 1. Mentions without a confidence are excluded. - `minFollowers` (integer): Only authors with at least this many followers. Unknown reach never passes. - `minLikes` (integer): Only posts with at least this many likes (upvotes, reactions), as the platform reported them when the post was found. A post without that count never passes. - `minQuotes` (integer): Only posts with at least this many quotes, as the platform reported them when the post was found. A post without that count never passes. - `minRelevance` (integer): Only mentions scored at least this; unclassified ones are excluded. - `minReplies` (integer): Only posts with at least this many replies (comments), as the platform reported them when the post was found. A post without that count never passes. - `minReposts` (integer): Only posts with at least this many reposts (shares, retweets), as the platform reported them when the post was found. A post without that count never passes. - `minViews` (integer): Only posts with at least this many views (plays), as the platform reported them when the post was found. A post without that count never passes. - `notCountries` (array): Never posts whose author is in these countries: notCountries=in. A post whose country is unknown still passes. - `notGroupIds` (array): Never matches of keywords in these groups. - `notIntents` (array): Never mentions carrying these intent or topic tags. - `notKeywordIds` (array): Never matches of these keywords. - `notLanguages` (array): Never posts in these languages. A post whose language is unknown still passes. - `notLinkHosts` (array): Never posts linking to these hosts, the host itself or a subdomain of it. - `notPlatforms` (array): Never posts from these platforms. - `notRatings` (array): Never reviews with these star ratings (1 to 5): notRatings=5 hides the five star reviews. Posts that are not reviews still pass. - `notSentiments` (array): Never these sentiments. A mention the classifier has not scored yet still passes. - `notSubreddits` (array): Never Reddit posts from these subreddits; posts from other platforms still pass. - `notTags` (array): Never authors tagged with any of these, in the workspace's tags or those of the mention's own keyword group. - `organization` (boolean): true: only posts by companies, brands and organizations (a LinkedIn company page, a GitHub organization, a business account); false: only posts by people, mentions judged before this existed included… - `personId` (string): Only this person (an id from /v1/people), merged accounts included. Implies includeMuted. - `platform` (string): Only posts from this platform. - `platforms` (array): Only posts from any of these platforms. - `q` (string): Substring search in the post text or the author's name. - `ratings` (array): Only app store reviews with any of these star ratings (1 to 5): ratings=1,2 is the unhappy ones. Every other post fails it. - `relevant` (boolean): true: only mentions the classifier scored relevant; false: only the rest (unclassified included). - `sentiment` (string): Only this sentiment. - `sentiments` (array): Only these sentiments. - `since` (integer): Only posts published at or after this instant (ISO 8601, or epoch ms). - `snoozed` (boolean): true: only mentions currently snoozed. Otherwise snoozed mentions stay out until they wake. - `sort` (string): newest: by match time, newest first. priority: by attention score, highest first; priority ranks the last 30 days of matches only, older ones stay reachable under newest. Cursors are specific to a so… - `status` (string): Only mentions in this status. Omit for every status. - `subreddits` (array): Only Reddit posts from any of these subreddits: subreddits=SaaS,startups (names without the r/, any case). Every other post fails it. Repeatable, or comma-separated. - `tags` (array): Only authors tagged with any of these (exact, case-sensitive), in the workspace's tags or those of the mention's own keyword group. Repeatable, or comma-separated. - `until` (integer): Only posts published at or before this instant (ISO 8601, or epoch ms). - `viewId` (string): Apply a saved view's filter (an id from GET /v1/views) on top of the other filters, every condition ANDed: exactly what the view selects. Unknown ids are a 404. ### `get_mention` (~49 tokens) Get mention Fetch a single mention by id, including its classification (relevance, sentiment, intents, confidence, uncertain, note). Input parameters: - `id` (string, required): Mention id (mention match id, mm_...) ### `list_mention_comments` (~176 tokens) List mention comments The comments under a mention's post, newest first: the whole thread, whether or not each comment names the keyword, each with its author, text, time, engagement, a light sentiment and intent read, and mentionId when the comment is itself one of your mentions. Filled from 30 minutes after the post and read again while its platform's conversations last (a day on Reddit, Hacker News and Bluesky, a week on GitHub, Stack Overflow and DEV, a month on YouTube) for relevant mentions whose keyword has comments enabled (add_keyword / update_keyword `comments`); empty otherwise. Page with cursor. Input parameters: - `cursor` (string): nextCursor from the previous page. - `id` (string, required): Mention id (mm_...) - `limit` (integer): Page size, 1 to 100. ### `update_mention` (~363 tokens) Update mention The one write on a mention: status "ignored" (not interesting) or "done" (handled), "open" to put it back; assign it to a workspace member (assigneeId, null to unassign); snooze it out of the feed until an ISO 8601 instant (snoozedUntil, null to wake it); leave an internal note (note, null to clear); or correct the classifier with `relevant` (true or false: your verdict, which sets relevance to 100 or 0 and moves the mention in or out of the relevant feed; null withdraws it) and `sentiment` (a corrected label; null restores the classifier's). Use the verdicts when the user says a mention is noise or was missed. Omitted fields are untouched. Delivery and billing never change. Input parameters: - `assigneeId`: A workspace member (user id), or null to unassign. - `id` (string, required): Mention id (mm_...) - `note`: Internal note; null or empty clears it. - `relevant` (boolean|null): Your verdict on relevance, correcting the classifier: true sets relevance to 100 and puts a filtered mention back in the relevant feed, false sets it to 0 and takes it out; null withdraws the verdict… - `sentiment`: Your corrected sentiment; null withdraws the correction and restores the classifier's. - `snoozedUntil`: ISO 8601 (or epoch ms) until which the mention leaves the feed; null wakes it. - `status` (string): ignored or done to handle it; open to put it back. ### `add_keyword` (~1602 tokens) Add keyword Start tracking a keyword. kind is "brand" (default), "competitor" or "topic". platforms optionally restricts it to some platforms (default: every platform). New mentions containing the term will be matched, classified and delivered. A multi-word term also matches a post holding its words close together (any order, plurals and spellings like non-profit/nonprofit); such a post is kept and billed only when the classifier scores it relevant. Wrap the term in double quotes, or set matching.exactPhrase, for the exact phrase only. Prefer short terms people actually write ("fundraising agency") over sentences ("looking for a fundraising agency"). For a common word, narrow it with `matching` (requiredTerms with requiredMode any|all, requiredGroups: combinations where the post must hold every term of at least one, as [["weather","alert*"],["tsunami"]], so one keyword replaces a search per line, excludedTerms, a `*` wildcard at an end of any rule term, excludedAuthors, caseSensitive, exactPhrase, subreddits: { only, excluded } to keep its Reddit posts to some subreddits or out of some): a post the rules reject is never stored or billed. `context` is one sentence the classifier reads for this keyword only ("Arc is our browser; ignore the geometry word"). `cap` ({ mentions: N, per: "day" | "week" | "month" }, per defaults to month) is a ceiling on its matched mentions per UTC day, week (from Monday) or month: at the cap it stops matching until the next period starts or until the cap is raised, while its daily keyword charge continues. A daily cap keeps mentions coming every day with a fixed ceiling on spend (N × $0.008 a day at most, plus the keyword). `groupId` puts it in a keyword group (list_groups; default: the workspace's default group); a term may be tracked once per group, so two groups may track the same term as two keywords. `reviewSources` collects reviews: pass each page's link (url: an App Store or Google Play app, a Trustpilot page, a Google Maps place or its maps.… Input parameters: - `cap`: A mention cap per day, week or month (per, default month); omit or null for none. - `comments` (object): Comments under this keyword's mentions; omitted fields are untouched (on create: off, 20 per post). - `context`: A sentence the classifier reads for this keyword only, on top of the company profile or the group's own description (at most 300 characters): what the term means here, what to ignore. "Arc is our bro… - `display` (object): Which of this keyword's mentions you see, by language and country; each list is replaced when sent, kept when omitted. Hidden mentions are still billed. - `feeds` (array): RSS or Atom feeds this keyword reads, at most 20, each { url }: a feed's URL, or a page's (a forum, a community, a blog), in which case the feed the page advertises is used, else a usual address such… - `groupId` (string): The group to track it in (grp_...); omit for the workspace's default group. A term may be tracked once per group. - `kind` (string): brand: your own names. competitor: theirs. topic: the space. Drives share of voice and segments. - `matching` (object): Omitted fields are untouched; an empty list clears one. - `platforms`: Platforms to search the term on; omit or null for every platform. [] searches it nowhere: a keyword that only collects reviews or reads feeds, which then needs reviewSources or feeds. - `readsWorkspaceFeeds` (boolean): Whether the keyword also reads the workspace's feeds (GET /v1/feeds); default true. A new keyword reading them gets the look-back of the 8 most recently connected. - `reviewSources` (array): Review pages this keyword collects, at most 10: App Store and Google Play apps, Trustpilot pages, Google Maps places. Every new review of one is a mention of the keyword, whatever its text says. Poll… - `term` (string, required): The word or phrase to track, case-insensitive. A multi-word term matches as the phrase or as its words close together (see matching.exactPhrase); wrap it in double quotes for the exact phrase only. ### `update_keyword` (~1062 tokens) Update keyword Change a keyword: rename it (term: the new term is tracked from now on, with no look-back; the keyword keeps its id, its settings and what the old term found), the platforms it is tracked on (platforms: a list, or null for every platform), mute or unmute it, reclassify it (kind), set its classifier context (null clears), or its matching rules (matching: each field optional, an empty list clears one; requiredTerms with requiredMode any|all, requiredGroups (every term of at least one combination), excludedTerms, a `*` wildcard at an end of any rule term, excludedAuthors, caseSensitive, exactPhrase: true for the exact phrase only, false to also match its words close together, subreddits: { only, excluded } for its Reddit posts alone, each list replaced when sent), or its monthly mention cap (cap: { mentions: N, per: "day" | "week" | "month" }, null removes it; a cap above the current period's count resumes a capped keyword at once), or move it to another group (groupId; a 409 when that group already tracks the term), or replace where it collects reviews, App Store, Google Play, Trustpilot or Google Maps (reviewSources: the whole list, [] disconnects them; a newly added app or country brings its last 30 days free), or replace the RSS or Atom feeds it reads (feeds: the whole list of URLs, [] disconnects them; a newly added feed brings its newest 10 matching items of the last 30 days). It also switches comments on or off (comments: { enabled, maxPerPost }; $0.008 per comment delivered), and sets which mentions it shows by language and country (display: { languages: { only, excluded }, countries: { only, excluded } }, each list replaced when sent; hidden mentions are still billed, and the change applies to older mentions too). Rules apply to new mentions only. Returns the updated keyword with its stats. On GitHub a keyword also gets events about repositories naming it; matching.repositories chooses them: events (traction: a repository under 30 days old reached 10 stars; s… Input parameters: - `cap`: Replaces the mention cap and its period (per, default month); null removes it. A cap above the current period's count resumes a capped keyword at once, one at or under it pauses it. - `comments` (object): Comments under this keyword's mentions; omitted fields are untouched (on create: off, 20 per post). - `context`: A sentence the classifier reads for this keyword only, on top of the company profile or the group's own description (at most 300 characters): what the term means here, what to ignore. "Arc is our bro… - `display` (object): Which of this keyword's mentions you see, by language and country; each list is replaced when sent, kept when omitted. Hidden mentions are still billed. - `feeds` (array): Replaces the feeds this keyword reads; [] disconnects them all (their mentions stay). A feed added here is checked now and brings its newest 10 matching items of the last 30 days; one already listed… - `groupId` (string): Moves the keyword to this group (grp_...). A 409 when that group already tracks the term. - `id` (string, required): Keyword id - `kind` (string): Reclassify it as brand, competitor or topic. - `matching` (object): Omitted fields are untouched; an empty list clears one. - `muted` (boolean): A muted keyword stops polling and matching; its mentions stay. - `platforms`: Replaces the platform list; null means every platform, [] none (reviews only, when the keyword has reviewSources). - `readsWorkspaceFeeds` (boolean): true: the keyword also reads the workspace's feeds (GET /v1/feeds), live from now on. false: its own feeds alone. - `reviewSources` (array): Replaces the list of apps whose reviews this keyword collects; [] disconnects them all (their reviews stay). An app or country added here gets the free 30-day look-back; one already listed keeps its… - `term` (string): Renames the keyword: the new term is tracked from now on, with no look-back, and the keyword keeps its id, its settings and the mentions the old term found. Wrap it in double quotes for the exact phr… ### `duplicate_keyword` (~245 tokens) Duplicate keyword Create a new keyword with an existing one's settings: give the new term (or the same term with another groupId, since a term is tracked once per group). It copies the kind, platforms, context, every matching rule, the monthly mention cap and the comments setting; review apps and feeds only when listed in include (reviewSources, feeds), since two keywords on one app collect and bill every review twice. It is a new keyword: $5 per month, and its last 30 days come in at once. Input parameters: - `groupId` (string): The group of the copy (grp_...); omit for the original's group. - `id` (string, required): The keyword to copy (kw_...) - `include` (array): Also copy these: reviewSources (its review apps) and feeds (its RSS or Atom feeds). Off by default, since two keywords on one app or feed collect, and bill, every review or item twice. - `term` (string, required): The term of the copy. The same term as the original only in another group (groupId): a term is tracked once per group. Wrap it in double quotes for the exact phrase only. ### `list_feeds` (~148 tokens) List feeds The RSS and Atom feeds the WORKSPACE reads (forums, communities, blogs): every keyword with readsWorkspaceFeeds (the default) gets an item of one of these feeds as a mention when the item holds its term, with its matching rules, billed like any mention. Each feed with when it was connected and how its hourly poll goes. q filters on address or title; limit and offset page, total counts. Input parameters: - `limit` (integer): Feeds per page, at most 500; default 100. - `offset` (integer): Feeds to skip, for the next page. - `q` (string): Only feeds whose address or title contains this text, case-insensitive. ### `add_feeds` (~255 tokens) Add feeds Connect RSS or Atom feeds to the workspace, up to 100 at a time (the workspace reads at most 500): each url is a feed's address, or a page's (a forum, a community, a blog) whose advertised feed is used. Every keyword reading workspace feeds then gets the feed's items holding its term, polled every hour; reading a feed is free, its matches bill like any mention. Each { url } is checked on its own and reported added, already (the workspace reads it) or failed with an error code: feed_unreadable (no feed found, or the site blocks automated readers), feed_login_required (a members-only forum: send it again as { url, auth: { type: "cookie", value } } with the person's own sign-in, stored encrypted and read for this workspace alone), feed_login_expired, feed_limit_reached. The first 8 added bring each keyword the newest 10 matching items of the last 30 days. Input parameters: - `feeds` (array, required): Up to 100 feeds, each { url } or { url, auth } for a members-only one. Each is checked on its own: one that fails never stops the others. ### `update_feed` (~170 tokens) Update feed Rename a workspace feed (title; null clears it) or set its sign-in for a members-only forum (auth: { type: 'cookie', value } with the Cookie header the person's signed-in browser sends, or { type: 'header', name, value }). A sign-in is checked by reading the feed with it (feed_login_expired when it does not work), stored encrypted, never shown again, and the feed is then read for this workspace alone; auth: null removes it. Input parameters: - `auth`: Replaces the sign-in (checked by reading the feed with it first); null removes it and the feed is read signed out again. - `id` (string, required): Feed id (fd_...), from list_feeds - `title`: Your name for the feed; null clears it. ### `delete_feed` (~58 tokens) Delete feed Stop the workspace reading a feed (fd_..., from list_feeds). Its mentions stay; keywords that name the same feed in their own feeds keep reading it. Input parameters: - `id` (string, required): Feed id (fd_...), from list_feeds ### `get_analytics_summary` (~315 tokens) Get analytics summary Headline counts for a window: matched and relevant mentions, distinct posts and people, sentiment split, buying intent and questions, estimated reach (followers of the people whose count is known), and triage (open, ignored, done, waiting over 24h, handled rate, median time to done). Window: range 7d|30d|90d|365d ending today, or from/to as YYYY-MM-DD; keywordIds and platforms are lists; timezone (IANA) cuts the days, UTC by default; compare=true adds the same counts for the period right before as `previous`. Time axis is the publish date. Input parameters: - `compare` (boolean): true adds the period of the same length right before the window as `previous`. - `from` (string): First day, YYYY-MM-DD, inclusive, in `timezone`. - `keywordIds` (array): Only these keyword ids. Repeatable, or comma-separated; omit for every keyword. - `platforms` (array): Only these platforms. Repeatable, or comma-separated; omit for every platform. - `range` (string): Preset window ending today. Ignored when from or to is given. Default 30d. - `timezone` (string): IANA zone the days are cut in (Europe/Madrid). Default UTC. One offset, the zone's at the end of the window, applies to the whole window. - `to` (string): Last day, YYYY-MM-DD, inclusive, in `timezone`. Default today. ### `get_analytics_series` (~363 tokens) Get analytics series Mentions over time: one point per day or week (bucket; default day up to 90 days) with matched, relevant and sentiment counts, as a single "total" series or split with by="platform" or by="keyword" (top 20, the rest as "other"). Same window parameters as get_analytics_summary; compare=true adds `previous`, the period right before, points aligned by index. Input parameters: - `bucket` (string): Point granularity: hour (windows of at most 14 days), day, week (Monday start) or month. Default: day up to 90 days, week beyond. - `by` (string): Split into one series per platform, per keyword (the top 20 by matched, the rest folded into "other") or per sentiment (positive, neutral, negative, unclassified). Omit for one total series. - `compare` (boolean): true adds the period of the same length right before the window as `previous`. - `from` (string): First day, YYYY-MM-DD, inclusive, in `timezone`. - `keywordIds` (array): Only these keyword ids. Repeatable, or comma-separated; omit for every keyword. - `platforms` (array): Only these platforms. Repeatable, or comma-separated; omit for every platform. - `range` (string): Preset window ending today. Ignored when from or to is given. Default 30d. - `timezone` (string): IANA zone the days are cut in (Europe/Madrid). Default UTC. One offset, the zone's at the end of the window, applies to the whole window. - `to` (string): Last day, YYYY-MM-DD, inclusive, in `timezone`. Default today. ### `get_analytics_breakdown` (~494 tokens) Get analytics breakdown One table grouped by a dimension `by`: platform, keyword, sentiment, intent, status (open, ignored, done), hour (weekday and hour of day in timezone, for "when do people talk"), person (who posted most, with followers), language (ISO 639-1), country (where the authors are, ISO 3166-1 alpha-2; "unknown" for posts nobody could place), or subreddit (Reddit posts only: which subreddits your mentions come from). Each row has matched, relevant, share of the window in percent, a sentiment split and, with compare=true, the same group in the period right before. Same window parameters as get_analytics_summary. At most 50 groups, most matched first. Input parameters: - `by` (string, required): The dimension to group by: platform, keyword, sentiment (unclassified included), intent (a mention can carry several), status (open, ignored, done), hour (weekday and hour of day in `timezone`), pers… - `compare` (boolean): true adds the period of the same length right before the window as `previous`. - `from` (string): First day, YYYY-MM-DD, inclusive, in `timezone`. - `keywordIds` (array): Only these keyword ids. Repeatable, or comma-separated; omit for every keyword. - `platforms` (array): Only these platforms. Repeatable, or comma-separated; omit for every platform. - `range` (string): Preset window ending today. Ignored when from or to is given. Default 30d. - `timezone` (string): IANA zone the days are cut in (Europe/Madrid). Default UTC. One offset, the zone's at the end of the window, applies to the whole window. - `to` (string): Last day, YYYY-MM-DD, inclusive, in `timezone`. Default today. ### `get_share_of_voice` (~248 tokens) Get share of voice Brand against competitors: every keyword matched in the window with matched, relevant, negative and buy-intent counts and its share of brand plus competitor matches in percent (topics are counted but stay out of the split). Same window parameters as get_analytics_summary; compare=true adds the previous period's matched per keyword. Input parameters: - `compare` (boolean): true adds the period of the same length right before the window as `previous`. - `from` (string): First day, YYYY-MM-DD, inclusive, in `timezone`. - `keywordIds` (array): Only these keyword ids. Repeatable, or comma-separated; omit for every keyword. - `platforms` (array): Only these platforms. Repeatable, or comma-separated; omit for every platform. - `range` (string): Preset window ending today. Ignored when from or to is given. Default 30d. - `timezone` (string): IANA zone the days are cut in (Europe/Madrid). Default UTC. One offset, the zone's at the end of the window, applies to the whole window. - `to` (string): Last day, YYYY-MM-DD, inclusive, in `timezone`. Default today. ### `get_reviews_report` (~302 tokens) Get reviews report The reviews report: App Store, Google Play, Trustpilot and Google reviews the keywords collect, over a window. Totals (reviews, average stars, 1-5 distribution, replies, open 1-2 star reviews), the tags on the unhappy reviews, and one row per review page with its average stars per day or week (bucket). A review matched by two keywords counts once. Same window parameters as get_analytics_summary; compare=true adds the previous period. Input parameters: - `bucket` (string): Series bucket: day (default up to 90 days) or week. - `compare` (boolean): true adds the period of the same length right before the window as `previous`. - `from` (string): First day, YYYY-MM-DD, inclusive, in `timezone`. - `keywordIds` (array): Only these keyword ids. Repeatable, or comma-separated; omit for every keyword. - `platforms` (array): Only these platforms. Repeatable, or comma-separated; omit for every platform. - `range` (string): Preset window ending today. Ignored when from or to is given. Default 30d. - `timezone` (string): IANA zone the days are cut in (Europe/Madrid). Default UTC. One offset, the zone's at the end of the window, applies to the whole window. - `to` (string): Last day, YYYY-MM-DD, inclusive, in `timezone`. Default today. ### `list_alerts` (~44 tokens) List alerts List alert rules: what each watches (filter), whether it fires instantly or as an hourly, daily or weekly digest (mode, schedule), and which channels it sends to. ### `get_alert` (~38 tokens) Get alert One alert rule by id: its filter, mode and schedule, channels and delivery stats. Input parameters: - `id` (string, required): Alert id (feed_...) ### `delete_alert` (~50 tokens) Delete alert Delete an alert rule. Its channels stay and can serve other rules. Irreversible; disabling it (update_alert enabled=false) keeps the rule. Input parameters: - `id` (string, required): Alert id (feed_...) ### `list_channels` (~47 tokens) List channels List the channels alerts can be sent to: Slack channels, Telegram chats, email address lists, webhooks. Telegram chats connect from the dashboard (Settings, Integrations), not through the API. ### `list_attention` (~178 tokens) List attention What needs a person right now, newest first: a keyword whose mentions spiked in the last hour (mention.spike), whose negative share of the last 24 hours jumped (sentiment.negative_spike), that turned noisy (keyword.noisy), or a channel whose last sends all failed (channel.failing). Detected once an hour; items resolve on their own when the condition is gone. Open items by default; status "all" reads the history. Each item has a one-line title, the facts in data, and data.url pointing at the dashboard. Input parameters: - `cursor` (string): nextCursor from the previous call. - `kinds` (array): Only these kinds. - `limit` (integer): Items to return, 50 by default. - `status` (string): open (default), resolved, dismissed, or all. ### `dismiss_attention` (~49 tokens) Dismiss attention Dismiss an attention item (att_... from list_attention): it leaves the open list and does not come back while its condition lasts. Input parameters: - `id` (string, required): Attention item id (att_...) ### `create_alert` (~293 tokens) Create alert Create an alert rule. mode "instant" sends each matching mention as it happens; "hourly" sends one digest every UTC hour (five minutes past) for the previous hour, nothing when it had no mention over the floor, takes no schedule and no email channel (Slack, Telegram, webhook); "daily" sends one digest at schedule.hour in schedule.timezone; "weekly" sends one a week on schedule.weekday (0 Sunday to 6 Saturday). filter narrows by keywordIds, platforms, minRelevance (the relevance floor: absent sends relevant mentions only, 40 and up; 0 sends every scored match, noise included), minConfidence, sentiments, intents, excludeAuthors, minFollowers, tags, linkHosts (the hosts a post links to, a host or any subdomain of it). channelIds come from list_channels. Input parameters: - `channelIds` (array): Channel ids from GET /v1/channels. - `enabled` (boolean) - `event`: Custom event name for webhook payloads; null for the mode default. - `filter` (object) - `mode` (string) - `name` (string, required) - `schedule` (object): Required for daily and weekly alerts (weekly ones also need schedule.weekday). Hourly alerts take none: they send every UTC hour, so a time of day and a zone are ignored and a weekday is refused. ### `update_alert` (~122 tokens) Update alert Change an alert: name, enabled, mode, schedule, filter (replaces the whole filter) or channelIds (replaces the whole list). Input parameters: - `channelIds` (array): Replaces the whole list. - `enabled` (boolean) - `event` - `filter` (object): Replaces the whole filter. - `id` (string, required): Rule id - `mode` (string) - `name` (string) - `schedule`: Daily and weekly alerts. Ignored on an hourly one, except a weekday, which is refused. ### `mute_authors` (~143 tokens) Mute authors Mute authors on an alert without touching the rest of its filter. Accepts profile or post links, @handles, u/names, Bluesky DIDs or display names; a link is stored as the author's profile. Already muted authors are skipped; an entry that names no person is rejected. Input parameters: - `authors` (array, required): Profile or post links (x.com/name, linkedin.com/in/name, reddit.com/user/name, a post URL), handles (@name, u/name), Bluesky DIDs or display names. A link is stored as the author's profile; a plain n… - `id` (string, required): Rule id ### `unmute_authors` (~122 tokens) Unmute authors Unmute authors on an alert without touching the rest of its filter. Name each by the stored entry or any link to that profile or its posts; authors that are not muted are ignored. Input parameters: - `authors` (array, required): Profile or post links (x.com/name, linkedin.com/in/name, reddit.com/user/name, a post URL), handles (@name, u/name), Bluesky DIDs or display names. A link is stored as the author's profile; a plain n… - `id` (string, required): Rule id ### `list_keywords` (~346 tokens) List keywords The tracked keywords of your organization with their stats, poll health, matching rules and context, plus `total`. Without arguments: every keyword, newest first. Search the term and context (q), narrow by kind, status (active, muted by a person, paused by the wallet, noisy: paused by the noise brake, capped at its monthly mention cap), platform or group (groupId), order (sort) and page (limit, offset). Input parameters: - `groupId` (array): Only keywords in any of these groups (grp_...). Repeatable, or comma-separated. - `kind` (array): Only these kinds: brand, competitor, topic. Repeatable, or comma-separated. - `limit` (integer): Page size, 1 to 500. Omit for every keyword after `offset`. - `offset` (integer): Skip this many keywords. - `platform` (array): Only keywords tracked on any of these platforms: its term searched there (every platform when its platforms are null), or for appstore and googleplay, an app of that store among its reviewSources. Re… - `q` (string): Text to find in the term or in the keyword's context, case-insensitive. - `sort` (string): newest: created most recently first. oldest: the reverse. term: A to Z. mentions: most matches first. relevant: most relevant matches first. recent: most matches in the last 7 days first. lastMention… - `status` (array): Only keywords in these states: active, muted, paused, capped. Repeatable, or comma-separated. ### `get_keyword` (~74 tokens) Get keyword One keyword by id: term, kind, platforms, matching rules, context, its monthly mention cap and whether it is at it (pausedForCap), stats (mentions, relevant, last 7 days, this month, your feedback) and poll health per platform. Input parameters: - `id` (string, required): Keyword id (kw_...) ### `get_keyword_health` (~277 tokens) Get keyword health Is a keyword worth what it costs, and what would fix it. Over a trailing window (range 7d, 30d or 90d; default 30d): a status (healthy; noisy = 20 or more scored matches and under 30% relevant; quiet = 7 days or older with nothing relevant; capped; paused; new = under 7 days old) with reasons in plain words, matches, relevant, noise share by platform and week, what it cost, the words and authors over-represented in its noise, and suggestions. Each suggestion has a `patch`: pass it to update_keyword with the keyword id to apply it (lists hold the whole new list), and an `effect` measured by running the matcher's rules over the window's posts (noise and relevant matches it would have removed, cents saved). ai=true adds a context rewritten by a language model (cached a day; 20 model calls an hour per workspace). Read only, never billed, cached 5 minutes. Input parameters: - `ai` (boolean): true: also ask a language model for a rewritten context. Default false. - `id` (string, required): Keyword id (kw_...) - `range` (string): Trailing window ending today: 7d, 30d (default) or 90d. ### `delete_keyword` (~79 tokens) Delete keyword Stop tracking a keyword and delete its mentions (a post also matched by another keyword stays). Alert rules that named it stop naming it; a rule that named only this keyword is disabled rather than widened to every keyword. Irreversible; muting (update_keyword muted=true) keeps the mentions. Input parameters: - `id` (string, required): Keyword id (kw_...) ### `whoami` (~64 tokens) Whoami The workspace this credential acts on, how it authenticated (an API key or an OAuth sign-in), whether it may write, and the person behind it when there is one. Call it once at the start of a session to name the workspace and know whether write tools are available. ### `list_members` (~47 tokens) List members The people in the workspace with their role (owner, admin, member), email and user id. The user id is the value update_mention assigneeId and update_person ownerId take. ### `get_usage` (~81 tokens) Get usage The prepaid balance (ledger, pending mention charges, effective), the daily burn and the days it buys, how many keywords run and how many the wallet paused, the matches recorded today and over 30 days, and whether tracking is stopped or the balance is low. Every matched mention bills $0.008 and every active keyword $5 a month, charged daily. ### `get_usage_breakdown` (~636 tokens) Get usage breakdown What the workspace consumed and was charged over a window, in USD cents at list price, grouped by ONE dimension per call: `by` = keyword (the default: days charged, mentions billed, totalCents per keyword, a deleted keyword kept with keyword.removed=true), platform, or day. `range` (7d, 30d, 90d; default 30d) reads a trailing window ending today; `month` (YYYY-MM) reads one calendar month, the shape a bill or a per-customer margin is reconciled against; `from`/`to` (YYYY-MM-DD) any window up to 366 days. `keywordIds`, `groupIds` and `platforms` narrow every number (a keyword-day has no platform, so a platform filter counts mentions and comments only). Every call also returns the window's totals (keyword-days, matched and billed mentions, list-price total, what the ledger actually debited). Rows are paged (limit, offset, total). Answer "what did keyword X cost" and "where does the money go" from it; get_usage answers "how much is left". Each keyword's running-month cost is also on get_keyword as stats.cost. Input parameters: - `by` (string): The dimension to group by: day (one row per UTC day of the window), platform, keyword (default: the row a margin is computed from), or group (what a customer or a campaign cost). - `from` (string): First UTC day of a custom window, YYYY-MM-DD, inclusive; with `to` (default today). At most 366 days. Wins over `range` and `month`. - `groupIds` (array): Only these groups (grp_...): a keyword-day by the group it was metered under, a mention or a comment by its keyword's group as it is now. Repeatable, or comma-separated. - `keywordIds` (array): Only these keywords (kw_...), deleted ones included. Repeatable, or comma-separated. - `limit` (integer): Rows per page, 1 to 500 (default 100). Only by=keyword can outgrow a page; a window has at most 90 days and a dozen platforms. - `month` (string): A calendar month (YYYY-MM, UTC) instead of a trailing window: from its first day to its last, or to today for the running month. A future month is a 400. - `offset` (integer): Skip this many rows. - `platforms` (array): Only these platforms. A keyword-day belongs to no platform, so with this filter the keyword line reads 0 and only mentions and comments count. Repeatable, or comma-separated. - `range` (string): Trailing window of UTC days ending today: 7d, 30d, 90d (default 30d). Ignored when `month` is given. - `to` (string): Last UTC day of a custom window, YYYY-MM-DD, inclusive; never after today. Needs `from`. ### `list_ledger` (~117 tokens) List ledger Every movement of the prepaid balance, newest first: the welcome credit, top-ups, refunds, the daily keyword-day and mention debits, adjustments. A debit row carries the UTC day it settled and the cumulative units behind it. Cursor paged (limit up to 100). Adding funds is a checkout on the dashboard's billing page or POST /v1/billing/top-ups on the REST API. Input parameters: - `cursor` (string): Opaque cursor from a previous page. - `limit` (integer): Page size (default 25). ### `get_filters` (~71 tokens) Get filters The workspace filters: noise rules applied to every keyword before a mention is stored (excluded terms and authors, excluded GitHub repositories, the subreddits Reddit posts may or may not come from). A post they reject is never classified, delivered or billed. Per-keyword rules live on each keyword (`matching`). ### `update_filters` (~160 tokens) Update filters Change the workspace filters: excludedTerms (a `*` at an end is a wildcard), excludedAuthors (links, handles, names), excludedRepos (owner/name or a github.com link), subreddits.only (an allowlist; when set, excluded is ignored) and subreddits.excluded. Each list optional; an omitted list is untouched, an empty one clears it. Takes effect on new mentions within a minute. Input parameters: - `excludedAuthors` (array): Replaces the list; [] clears it. - `excludedRepos` (array): Replaces the list; [] clears it. - `excludedTerms` (array): Replaces the list; [] clears it. - `subreddits` (object): Reddit only; an omitted list is untouched. ### `get_company` (~58 tokens) Get company Read what the classifier knows about the company: name, description, use cases, own accounts, and the composed context it reads to judge relevance (for keywords in a group that carries its own description, the group's text replaces it; see list_groups). ### `update_company` (~181 tokens) Update company Update the company profile (name, description, useCases, accounts) or override the classifier context directly. Profile edits recompose the context; an explicit context wins until the next profile edit. The context is the single biggest lever on relevance scoring, so keep it accurate and specific; it does not reach keywords in a group with its own description (update_group for those). Omitted fields are untouched. Input parameters: - `accounts` (object) - `competitors` (array): Replaces the whole list; [] clears it. - `context` (string): Overrides the composed context until the next profile edit. - `description` (string) - `guidelines`: Free-text rules for the classifier; null clears them. - `name` (string) - `useCases` (array): Replaces the whole list. - `website`: The company website; null clears it. ### `list_people` (~740 tokens) List people The people who wrote mentions matching your keywords: name, profile, platform, how many of their posts matched (and how many scored relevant), their sentiment split, when they were first and last seen, and where your outreach stands (owner, stage, last contacted). Filter by platform or name, find one person by handle or profile link (handle), outreach stage (stages), owner (ownerIds, "none" for unowned) or automated (bot accounts, whose posts mostly read machine-made); sort by mentions or recency. With groupId, only the people who mentioned that keyword group's keywords, with that group's own counts, tags, notes, merges and outreach. Use search_mentions with authorId to read what one person said. Email addresses are not returned over MCP: profile.email is always null (the dashboard and the REST API show it where the person published it). Input parameters: - `automated` (boolean): true: only people whose matched posts are mostly machine-made (bot accounts); false: only the rest - `groupId` (string): Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, mute, merges, activities and segments. Omit for the whole workspace. - `handle` (string): Find one person by an account: a handle (@jane, u/jane) or a profile or post link (https://x.com/jane). Exact, case-insensitive; add platform to pick one platform - `intents` (array): At least one mention carrying any of these intents - `keywordKinds` (array): Mentioned a keyword of any of these kinds (brand, competitor, topic) - `limit` (integer) - `linkHosts` (array): At least one mention linking to any of these hosts, the host itself or a subdomain of it (octolens.com also matches blog.octolens.com) - `maxFollowers` (integer) - `minFollowers` (integer): At least this many followers (unknown reach never matches) - `minMentions` (integer): At least this many matched mentions - `minNegative` (integer): At least this many negative mentions - `muted` (boolean): true: only muted people; false: only unmuted; omit: everyone - `neverKeywordKinds` (array): Never mentioned a keyword of these kinds - `newSinceDays` (integer): First seen within this many days - `offset` (integer): Skip this many people (paging) - `ownerIds` (array): People owned by any of these members (user ids); "none" for people nobody owns - `platform` (string): Only people with an account on this platform - `platforms` (array): People with an account on any of these platforms - `q` (string): Match the display name or the profile handle/url - `segmentId` (string): A saved segment (from list_segments) applied on top of the other filters - `since` (integer): Only people whose first matched mention is at or after this instant (ISO 8601, or epoch ms): new voices - `sort` (string): "mentions": most matches first; "recent": last seen first; "reach": most followers first; "new": first seen most recently first - `stages` (array): People at any of these outreach stages (not_contacted, contacted, replied, in_talks, customer, not_a_fit) - `tag` (string): Only people carrying this tag - `tags` (array): People carrying any of these tags ### `get_person` (~185 tokens) Get person One person from the audience, with their counts, tags, notes and mute for your organization, their outreach (owner, stage, last contacted), plus their public profile (bio, company, location, website and linked accounts) where the platform lists it. GitHub authors are looked up today; profile is null until then. With groupId, the person as that keyword group sees them. Email addresses are not returned over MCP: profile.email is always null (the dashboard and the REST API show it where the person published it). Input parameters: - `groupId` (string): Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, mute, merges, activities and segments. Omit for the whole workspace. - `id` (string, required): Audience author id (aut_...), from list_people or a mention's authorId ### `update_person` (~314 tokens) Update person Annotate a person for your organization: replace their tags, set notes, mute/unmute them, or set the outreach owner (ownerId, a member user id; null clears) and stage. Muting hides their posts from the feed and from every channel; ingest and billing are unchanged. With groupId the annotations are that keyword group's own: muted hides the person from the mentions of that group's keywords only (feed, alerts and digests), and the group's tags show on those mentions next to the workspace's. A mute set without groupId hides them for every group. Input parameters: - `groupId` (string): Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, mute, merges, activities and segments. Omit for the whole workspace. - `id` (string, required): Audience author id (aut_...) - `muted` (boolean): true hides their posts from the feed, the alerts and the digests; false shows them again. Without groupId, for every keyword of the workspace; with groupId, for the mentions of that group's keywords… - `notes` (string) - `ownerId`: The member who owns the contact (user id); null clears. - `stage` (string): Where your workspace stands with the person: not_contacted, contacted, replied, in_talks, customer or not_a_fit. - `tags` (array): Replaces the whole list. ### `merge_people` (~140 tokens) Merge people Declare that two accounts are the same person, for your organization only: fold account `id` into person `into`. Their mentions, tags and notes combine; the folded account shows under the person's platforms. With groupId the merge holds in that keyword group only. Input parameters: - `groupId` (string): Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, mute, merges, activities and segments. Omit for the whole workspace. - `id` (string, required): The account to fold in (aut_...) - `into` (string, required): The person to fold it into (aut_...) ### `split_person` (~108 tokens) Split person Undo a merge: the account becomes its own person again for your organization. A merge made in a keyword group is undone with that groupId. Input parameters: - `groupId` (string): Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, mute, merges, activities and segments. Omit for the whole workspace. - `id` (string, required): Audience author id (aut_...), from list_people or a mention's authorId ### `list_activities` (~163 tokens) List activities The outreach log on one person, newest first: every logged contact with who reached out, the channel (email, x, linkedin, bluesky, reddit, github, call, meeting, other), when, and a short note. Check it, and the person's outreach owner, before reaching out so two teammates never contact the same person without knowing. With groupId, the log that keyword group keeps on them. Input parameters: - `groupId` (string): Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, mute, merges, activities and segments. Omit for the whole workspace. - `id` (string, required): Audience author id (aut_...), from list_people or a mention's authorId ### `log_activity` (~294 tokens) Log activity Record that someone reached out to a person: an email, a DM, a call. The first contact claims an unowned person for whoever reached out and moves not_contacted to contacted; an existing owner and a later stage are kept (set them with update_person). memberId defaults to the signed-in user; with an API key and no memberId the activity is unattributed and claims nobody. Returns the activity and the person as they now read. With groupId the activity, and the owner and stage it moves, are that keyword group's own. Input parameters: - `channel` (string, required): How they were reached: email, x, linkedin, bluesky, reddit, github, call, meeting or other. - `groupId` (string): Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, mute, merges, activities and segments. Omit for the whole workspace. - `id` (string, required): Person id (aut_...), from list_people or a mention's authorId - `memberId` (string): The member who reached out (user id). Defaults to the signed-in member; an API key that omits it logs an unattributed activity. - `note` (string): What was sent or said, briefly. - `occurredAt` (integer): When the contact happened (ISO 8601, or epoch ms). Defaults to now. ### `delete_activity` (~118 tokens) Delete activity Delete an outreach activity logged by mistake. The person's owner and stage stay as they are. An activity logged in a keyword group is found with that groupId. Input parameters: - `activityId` (string, required): Activity id (act_...), from list_activities - `groupId` (string): Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, mute, merges, activities and segments. Omit for the whole workspace. - `id` (string, required): Person id (aut_...) ### `get_mention_stats` (~88 tokens) Get mention stats Mention counts for the last N days (default 7), grouped by platform and by sentiment, optionally filtered to one platform or keyword. Unclassified mentions appear under sentiment "unclassified". Input parameters: - `keywordId` (string): Only count mentions matching this keyword id - `platform` (string): Only count mentions from this platform - `sinceDays` (integer): Look-back window in days ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-mentio-mcp/mcp#diagnostics ## Score history - 2026-11-05: 87 - 2026-11-04: 86 - 2026-11-03: 87 - 2026-11-02: 86 - 2026-11-01: 86 - 2026-10-31: 85 - 2026-10-30: 85 - 2026-10-29: 84 - 2026-10-28: 84 - 2026-10-27: 83 - 2026-10-26: 83 - 2026-10-25: 82 - 2026-10-24: 82 - 2026-10-23: 81 - 2026-10-22: 81 - 2026-10-21: 80 - 2026-10-20: 80 - 2026-10-19: 79 - 2026-10-18: 79 - 2026-10-17: 79 - 2026-10-16: 78 - 2026-10-15: 78 - 2026-10-14: 77 - 2026-10-13: 77 - 2026-10-12: 77 - 2026-10-10: 76 - 2026-10-09: 75 - 2026-10-04: 71 ## Common questions ### What is the Mentio MCP server? Mentio is an MCP server listed in the public MCP registry as dev.mentio/mcp. Social listening for agents: brand mentions across 16 platforms, scored for relevance and intent. This page covers its hosted endpoint (https://mcp.mentio.dev/mcp). ### Is the Mentio MCP server safe to use? Mentio scores 87 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 Mentio MCP server expose? Mentio exposes 61 tools: list_segments, create_segment, update_segment, delete_segment, list_views, and 56 more. Their descriptions and schemas cost roughly 15,149 tokens of context every time the server is loaded. ### Does the Mentio MCP server require authentication? Yes. Mentio 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 Mentio MCP server still maintained? Mentio 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. ### What did VerifyMCP test on the Mentio MCP server? VerifyMCP ran 12 checks on Mentio, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Mentio: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out. ## Links - Remote endpoint: https://mcp.mentio.dev/mcp - Website: https://mentio.dev/ - Changelog RSS feed: https://verifymcp.io/servers/dev-mentio-mcp/mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/dev-mentio-mcp/mcp/changelog.json - Trust report (JSON): https://verifymcp.io/servers/dev-mentio-mcp/mcp.json - HTML version of this page: https://verifymcp.io/servers/dev-mentio-mcp/mcp