Mention

A working server exists but somebody other than the vendor built it. It can be abandoned without the vendor noticing. The status was established by hand on 2026-09-02. On 2026-09-04 the recorded URL was a reachable repository or package: a server you install and run on your own machine over stdio. Callable after an install, not a remote endpoint.

mcp_status, verbatim from the file:

community

mcp_url, verbatim from the file:

https://github.com/MaelitoP/mention-mcp-server (third-party; not published by Mention)

• https://github.com/MaelitoP/mention-mcp-server

A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.

This list came from a repo the vendor does not own. Those are that author's tools for the vendor's API, not the vendor's own published surface, and the two must not be read as the same thing.

• build-boolean-query
  Generate a valid Boolean query string using Boolean operators, quoted terms, proximity, and field selectors
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• create_advanced_alert
  Create a new advanced monitoring alert with boolean query syntax. Advanced alerts use complex query strings with boolean operators like AND, OR, NOT.
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• create_basic_alert
  Create a new basic monitoring alert. Basic alerts use simple keyword matching with included_keywords, required_keywords, and excluded_keywords arrays.
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• fetch_alert_stats
  Retrieve comprehensive statistics for one or more alerts including mentions per interval, tones, influencers, geographical data, and reach metrics. Supports flexible date ranges, filtering, and aggregation options.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• fetch_mentions
  Retrieve mentions associated with a specific alert. Supports various filters like source, folder, tone, countries, languages, and advanced search queries.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_account_info
  Get current account information including subscription plan, account ID, and capabilities. This tool should be called first to understand account limitations and determine which alert creation tools are available.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_alert
  Get detailed information about a specific alert by its ID.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_app_data
  Get application configuration data including available languages, countries, sources, colors, and other metadata needed for creating alerts.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• instructions
  What the Boolean query should match, e.g.,
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• list_alerts
  List all monitoring alerts for the current account with pagination support.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• pause_alert
  Temporarily pause monitoring for a specific alert.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• unpause_alert
  Resume monitoring for a previously paused alert.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• update_alert
  Update an existing alert with new criteria or settings.
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.

No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.

api_gate, verbatim from the file:

paid - "API access for custom integrations" is listed as part of the top-tier Company plan; exact dollar pricing was not visible on the fetched pricing page (rendered as placeholders, likely region/currency-gated), so treat pricing as unconfirmed beyond "top-tier plan only."

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:

• https://github.com/MaelitoP/mention-mcp-server

github.com/mentionapp tied to the vendor by rule 3, account website https://mention.com has the vendor's domain, confidence strong

The five most recently pushed, on 2026-09-08:

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

• Monitor social and community mentions

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

• https://mention.com/en/
• https://mention.com/en/pricing/
• https://github.com/MaelitoP/mention-mcp-server

3 source URLs. Raw sources field, verbatim:

https://mention.com/en/, https://mention.com/en/pricing/, https://github.com/MaelitoP/mention-mcp-server

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.