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

Mentio

REMOTE · MCP.MENTIO.DEV

Social listening for agents: brand mentions across 16 platforms, scored for relevance and intent

Available components

+3 this week 87 Trust /100

Last scanned (6 hours ago)

Scores higher than 94% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security81
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 63 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 +1

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

  • 30 Oct 26 +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.

  • 28 Oct 26 +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.

  • 26 Oct 26 +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.

  • 24 Oct 26 +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.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://mcp.mentio.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mentio.dev CN=WE1,O=Google Trust Services,C=US 28 Oct 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA256 7f3a09f2aa59afb41350c2812266e0fc
SANs: mentio.dev, mcp.mentio.dev, *.mcp.mentio.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.mentio.dev. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
mentio.dev. DS published 2371 13 Verified
mcp.mentio.dev. Verified address RRset verified with the apex keys
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="mentio-mcp", resource_metadata="https://mcp.mentio.dev/.well-known/oauth-protected-resource"

Bearer realm="mentio-mcp", resource_metadata="https://mcp.mentio.dev/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://mcp.mentio.dev/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.mentio.dev/mcp
Authorisation server https://app.mentio.dev

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.mentio.dev/mcp Verified 200
http (plaintext) http://mcp.mentio.dev/mcp Inconclusive 405
MCP tools · 61 exposed · ~15,149 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
update_alert ~122

Change an alert: name, enabled, mode, schedule, filter (replaces the whole filter) or channelIds (replaces the whole list).

NameTypeReqDescription
channelIdsarray–Replaces the whole list.
enabledboolean––
event–––
filterobject–Replaces the whole filter.
idstringyesRule id
modestring––
namestring––
schedule––Daily and weekly alerts. Ignored on an hourly one, except a weekday, which is refused.

No output schema declared.

No examples provided.

update_company ~181

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.

NameTypeReqDescription
accountsobject––
competitorsarray–Replaces the whole list; [] clears it.
contextstring–Overrides the composed context until the next profile edit.
descriptionstring––
guidelines––Free-text rules for the classifier; null clears them.
namestring––
useCasesarray–Replaces the whole list.
website––The company website; null clears it.

No output schema declared.

No examples provided.

update_feed ~170

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.

NameTypeReqDescription
auth––Replaces the sign-in (checked by reading the feed with it first); null removes it and the feed is read signed out again.
idstringyesFeed id (fd_...), from list_feeds
title––Your name for the feed; null clears it.

No output schema declared.

No examples provided.

update_filters ~160

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.

NameTypeReqDescription
excludedAuthorsarray–Replaces the list; [] clears it.
excludedReposarray–Replaces the list; [] clears it.
excludedTermsarray–Replaces the list; [] clears it.
subredditsobject–Reddit only; an omitted list is untouched.

No output schema declared.

No examples provided.

update_group ~186

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

NameTypeReqDescription
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.
idstringyesGroup id (grp_...)
namestring–The group's name: a customer, a campaign, a product. Unique per workspace.

No output schema declared.

No examples provided.

update_keyword ~1,062

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…

NameTypeReqDescription
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.
commentsobject–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…
displayobject–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.
feedsarray–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…
groupIdstring–Moves the keyword to this group (grp_...). A 409 when that group already tracks the term.
idstringyesKeyword id
kindstring–Reclassify it as brand, competitor or topic.
matchingobject–Omitted fields are untouched; an empty list clears one.
mutedboolean–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).
readsWorkspaceFeedsboolean–true: the keyword also reads the workspace's feeds (GET /v1/feeds), live from now on. false: its own feeds alone.
reviewSourcesarray–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…
termstring–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…

No output schema declared.

No examples provided.

update_mention ~363

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.

NameTypeReqDescription
assigneeId––A workspace member (user id), or null to unassign.
idstringyesMention id (mm_...)
note––Internal note; null or empty clears it.
relevantboolean|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.
statusstring–ignored or done to handle it; open to put it back.

No output schema declared.

No examples provided.

update_person ~314

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.

NameTypeReqDescription
groupIdstring–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.
idstringyesAudience author id (aut_...)
mutedboolean–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…
notesstring––
ownerId––The member who owns the contact (user id); null clears.
stagestring–Where your workspace stands with the person: not_contacted, contacted, replied, in_talks, customer or not_a_fit.
tagsarray–Replaces the whole list.

No output schema declared.

No examples provided.

update_segment ~126

Rename, describe or refilter a saved segment. `filter` replaces the whole filter. A segment saved in a keyword group is found with that groupId.

NameTypeReqDescription
descriptionstring––
filterobject–Replaces the whole filter.
groupIdstring–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.
idstringyesSegment id (seg_...)
namestring––

No output schema declared.

No examples provided.

update_view ~64

Rename, describe or refilter a saved view. `filter` replaces the whole filter.

NameTypeReqDescription
descriptionstring––
filterobject–Replaces the whole filter.
idstringyesView id (vw_...)
namestring––

No output schema declared.

No examples provided.

whoami ~64

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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.

remote · mcp.mentio.dev

# add to Claude Code
claude mcp add --transport http dev-mentio-mcp 'https://mcp.mentio.dev/mcp'
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.