Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.

Is mentiondrop free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does mentiondrop have?

11 tools: create_keyword, update_keyword, get_competitor_signals, get_pain_signals, get_recent_mentions, mark_mention_reviewed, get_mention, search_mentions, ….

Is mentiondrop safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp streamable-http · checked 2h ago

mentiondrop

https://www.mentiondrop.com

Registry code: 33979e5193e28c1d

api record

AI-triaged brand, competitor and demand mentions from Reddit, Google News and search.

from a public catalogue that lists it, not from the operator

endpoint: https://www.mentiondrop.com/api/mcp
protocol: streamable-http ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is mentiondrop live?: Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is mentiondrop free to use?: Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does mentiondrop have?: 11 tools: create_keyword, update_keyword, get_competitor_signals, get_pain_signals, get_recent_mentions, mark_mention_reviewed, get_mention, search_mentions, ….
Is mentiondrop safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

99.4%

90 days 99.4%· all time 99.4%

latency

225ms

last good check

priced tools

of 11 tools

_ answered our checks, 90 days 338 checks · signed record

2026-11-03 02:15 degraded → live
2026-11-03 00:13 live → degraded· timeout after 20000ms
2026-10-12 10:24 degraded → live
2026-09-28 20:12 degraded → live
2026-09-28 18:13 live → degraded· timeout after 20000ms

_ what it is for

topic: productivity & business marketing & seo
used for: monitor brand mentions
get competitor mention signals
get demand and pain signals
draft reply to a mention
takes → gives: text → data, text
tools: 8 reads3 changes data

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 11 tools

11 auth-required 11 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

create_keyword changes data auth-required never probed

Start monitoring a new keyword for this account. Takes an optional role (own_brand, competitor, or industry) and a short context string that sharpens relevance scoring. Enforces the account plan keyword limit and rejects keywords too generic to produce signal.

mcp-tool

{
  "type": "object",
  "required": [
    "keyword"
  ],
  "properties": {
    "role": {
      "enum": [
        "own_brand",
        "competitor",
        "industry"
      ],
      "type": "string"
    },
    "context": {
      "type": "string",
      "maxLength": 300
    },
    "keyword": {
      "type": "string",
      "maxLength": 100,
      "minLength": 2
    }
  },
  "additionalProperties": false
}

arguments 26 lines

update_keyword changes data auth-required never probed

Update one existing monitored keyword by id: change its role, context, active state, minimum relevance threshold, excluded content types, or exclusion terms. Use list_keywords to find the id. Pausing a keyword sets is_active to false rather than deleting it.

mcp-tool

{
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "role": {
      "enum": [
        "own_brand",
        "competitor",
        "industry"
      ],
      "type": "string"
    },
    "context": {
      "type": [
        "string",
        "null"
      ]
    },
    "is_active": {
      "type": "boolean"
    },
    "min_relevance": {
      "type": "number",
      "maximum": 100,
      "minimum": 0
    },
    "exclusion_terms": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "excluded_content_types": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  },
  "additionalProperties": false
}

arguments 46 lines

get_competitor_signals reads auth-required never probed

Return recent mentions matched by competitor-role keywords, optionally narrowed to a single competitor name. Use this to see what people are publicly saying about rival products.

mcp-tool

{
  "type": "object",
  "properties": {
    "to": {
      "type": "string"
    },
    "from": {
      "type": "string"
    },
    "limit": {
      "type": "number",
      "maximum": 50,
      "minimum": 1
    },
    "competitor": {
      "type": "string"
    }
  },
  "additionalProperties": false
}

arguments 20 lines

get_pain_signals reads auth-required never probed
Return recent industry-role mentions that read as demand or pain signals, meaning they carry a suggested action or score at least 80 for relevance. Use this to find people publicly describing a problem the product solves.

mcp-tool
{ "type": "object", "properties": { "to": { "type": "string" }, "from": { "type": "string" }, "limit": { "type": "number", "maximum": 50, "minimum": 1 }, "keyword": { "type": "string" } }, "additionalProperties": false }
arguments 20 lines

get_recent_mentions reads auth-required 2h ago

Return the most recent mentions matched for this account, newest first, each with its AI summary, sentiment, relevance score, and suggested action. Filter by keyword role, specific keyword, source, sentiment, and date range. Use this to answer "what came in lately".

mcp-tool

{
  "type": "object",
  "properties": {
    "to": {
      "type": "string"
    },
    "from": {
      "type": "string"
    },
    "role": {
      "enum": [
        "own_brand",
        "competitor",
        "industry"
      ],
      "type": "string"
    },
    "limit": {
      "type": "number",
      "maximum": 50,
      "minimum": 1
    },
    "source": {
      "enum": [
        "firehose",
        "reddit",
        "brave",
        "google_news",
        "serper",
        "hackernews",
        "adzuna"
      ],
      "type": "string"
    },
    "keyword": {
      "type": "string"
    },
    "sentiment": {
      "enum": [
        "positive",
        "neutral",
        "negative"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}

arguments 48 lines

mark_mention_reviewed changes data auth-required never probed
Record a review verdict on one mention as relevant or not_relevant. This feedback tunes how future mentions are scored for the account. Re-sending the same verdict is safe.

mcp-tool
{ "type": "object", "required": [ "id", "verdict" ], "properties": { "id": { "type": "string" }, "verdict": { "enum": [ "relevant", "not_relevant" ], "type": "string" } }, "additionalProperties": false }
arguments 20 lines
get_mention reads auth-required 15h ago
Fetch one mention by id with its full record: title, AI summary, sentiment, relevance score, suggested action, source, and matched keyword. Only returns mentions owned by this account.

mcp-tool
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string" } }, "additionalProperties": false }
arguments 12 lines

search_mentions reads auth-required 15h ago

Find mentions whose title, summary, URL, suggested action, or matched keyword contain every word in the query. Use this to look for a specific topic, product, or phrase rather than a plain time window.

mcp-tool

{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "to": {
      "type": "string"
    },
    "from": {
      "type": "string"
    },
    "role": {
      "enum": [
        "own_brand",
        "competitor",
        "industry"
      ],
      "type": "string"
    },
    "limit": {
      "type": "number",
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string"
    },
    "source": {
      "enum": [
        "firehose",
        "reddit",
        "brave",
        "google_news",
        "serper",
        "hackernews",
        "adzuna"
      ],
      "type": "string"
    },
    "keyword": {
      "type": "string"
    },
    "sentiment": {
      "enum": [
        "positive",
        "neutral",
        "negative"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}

arguments 54 lines

generate_reply_draft reads auth-required never probed

Generate a draft reply or outreach email for one processed mention. Returns draft text for a human to review and never posts, sends, or publishes anything.

mcp-tool

{
  "type": "object",
  "required": [
    "mention_id"
  ],
  "properties": {
    "mention_id": {
      "type": "string"
    },
    "draft_intent": {
      "enum": [
        "reply",
        "outreach_email"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}

arguments 19 lines

get_digest reads auth-required 2h ago
Return one grouped catch-up brief of recent mentions, split into owned brand mentions, competitor signals, demand signals, and conversations worth replying to. Use this when a single summary is wanted instead of separate queries.

mcp-tool
{ "type": "object", "properties": { "to": { "type": "string" }, "from": { "type": "string" }, "limit": { "type": "number", "maximum": 50, "minimum": 1 } }, "additionalProperties": false }
arguments 17 lines
list_keywords reads auth-required 2h ago
List every keyword this MentionDrop account monitors, with its id, role (own_brand, competitor, or industry), and active state. Call this first to discover the keyword ids and role names the other tools accept.

mcp-tool
{ "type": "object", "properties": {}, "additionalProperties": false }
arguments 5 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 33979e5193e28c1d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/33979e5193e28c1d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/33979e5193e28c1d/badge.svg)](https://brick.blue/agent/33979e5193e28c1d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.