com.mentiondrop/mentiondrop
REMOTE · WWW.MENTIONDROP.COM · SCANNED AUG 14
AI-triaged brand, competitor and demand mentions from Reddit, Google News and search.
Available components
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 →
Endpoint Security97
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 852 tokens (~77/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · www.mentiondrop.com
claude mcp add --transport http com-mentiondrop-mentiondrop https://www.mentiondrop.com/api/mcp
[mcp_servers.com-mentiondrop-mentiondrop] url = "https://www.mentiondrop.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mentiondrop-mentiondrop": {
"type": "remote",
"url": "https://www.mentiondrop.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-mentiondrop-mentiondrop --url https://www.mentiondrop.com/api/mcp --transport streamable-http
mcp_servers:
com-mentiondrop-mentiondrop:
url: "https://www.mentiondrop.com/api/mcp" {
"mcpServers": {
"com-mentiondrop-mentiondrop": {
"type": "http",
"url": "https://www.mentiondrop.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 13 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 9 Aug 26 74
First indexed and scored.
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 14 Aug 2026 · Probed https://www.mentiondrop.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.mentiondrop.com | CN=YR1,O=Let's Encrypt,C=US | 15 Jul 2026 | 13 Oct 2026 | RSA 2048 | SHA256-RSA | 5647cd1d77e1d2890f0c5f26aeb8f6c9c82 |
| SANs: www.mentiondrop.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of www.mentiondrop.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| mentiondrop.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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="MentionDrop", error="invalid_token", resource_metadata="https://www.mentiondrop.com/.well-known/oauth-protected-resource"
Bearer realm="MentionDrop", error="invalid_token", resource_metadata="https://www.mentiondrop.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://www.mentiondrop.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://www.mentiondrop.com/api/v1 |
| Authorisation server | https://clerk.mentiondrop.com |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.mentiondrop.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.mentiondrop.com/api/mcp | HTTPS enforced | 308 | https://www.mentiondrop.com/api/mcp |
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.
create_keyword ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | – |
| keyword | string | yes | – |
| role | string | – | – |
No output schema declared.
No examples provided.
generate_reply_draft ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| draft_intent | string | – | – |
| mention_id | string | yes | – |
No output schema declared.
No examples provided.
get_competitor_signals ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| competitor | string | – | – |
| from | string | – | – |
| limit | number | – | – |
| to | string | – | – |
No output schema declared.
No examples provided.
get_digest ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| limit | number | – | – |
| to | string | – | – |
No output schema declared.
No examples provided.
get_mention ~53
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_pain_signals ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| keyword | string | – | – |
| limit | number | – | – |
| to | string | – | – |
No output schema declared.
No examples provided.
get_recent_mentions ~112
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".
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| keyword | string | – | – |
| limit | number | – | – |
| role | string | – | – |
| sentiment | string | – | – |
| source | string | – | – |
| to | string | – | – |
No output schema declared.
No examples provided.
list_keywords ~51
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mark_mention_reviewed ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| verdict | string | yes | – |
No output schema declared.
No examples provided.
search_mentions ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| keyword | string | – | – |
| limit | number | – | – |
| query | string | yes | – |
| role | string | – | – |
| sentiment | string | – | – |
| source | string | – | – |
| to | string | – | – |
No output schema declared.
No examples provided.
update_keyword ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string|null | – | – |
| excluded_content_types | array | – | – |
| exclusion_terms | array | – | – |
| id | string | yes | – |
| is_active | boolean | – | – |
| min_relevance | number | – | – |
| role | string | – | – |
No output schema declared.
No examples provided.