mcp-registry/ai.trendsmcp/market-research · v1.0.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-10 22:08 UTC, the Trendsmcp Market Research MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 13 minutes.
See if a market is heating or cooling. Trend volume and growth signals. Free key at trendsmcp.ai
Point your MCP client at this streamable-http endpoint: https://market-research.api.trendsmcp.ai/mcp
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
In the last 30 days: 1 tool(s) removed and 18 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
1 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fai.trendsmcp%2Fmarket-research/fixes
{
"name": "trends___get_reviews",
"description": "What customers say about a brand, app, product or place. Returns, per source, the matched listing with its all-time rating and review count, the newest reviews (stars, text, the company's reply) and a summary (average stars, star counts, share negative, share replied). Use it for brand sentiment and complaints; get_context covers social posts. Costs 1 request per data type (source or board) in the call; boards cost 1 request per 10 rows. Only data types that answer are charged; the answer says r",
"inputSchema": {
"type": "object",
"required": [
"keyword",
"source"
],
"properties": {
"days": {
"type": "integer",
"description": "Only reviews from the last N days, 1 to 365. Default 90."
},
"limit": {
"type": "integer",
"description": "Reviews per source, newest first, 1 to 20. Default 10."
},
"source": {
"type": "string",
"description": "One source, several comma-separated, or 'all': 'all' = 3 ('App Store', 'Google Play', and 'Amazon'), costing 3. Valid: 'App Store', 'Google Play', 'Amazon'."
},
"country": {
"type": "string",
"description": "Store country, ISO code (US, GB, DE). Default US. Only for 'App Store', 'Google Play', and 'Amazon'."
},
"keyword": {
"type": "string",
"description": "A brand, app, product or place name, e.g. 'notion'. Each source matches it to one listing and returns that listing as subject; check it is the one you meant."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.trendsmcp/market-research"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.trendsmcp/market-research"}) over MCP.
trends___get_growth ~893 tokenstrends___get_top_trends ~805 tokenstrends___get_time_series ~742 tokenstrends___get_context ~475 tokenstrends___get_reviews ~381 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fai.trendsmcp%2Fmarket-research?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.trendsmcp%2Fmarket-research?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fai.trendsmcp%2Fmarket-research.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:36fbc76c146f36cf…, first seen 2026-11-06, included at leaf 178496 of 217,498. Version history · verify what your client received.
Compare: most reliable data servers · most reliable search servers · most reliable trends servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
As of 2026-11-10 22:08 UTC, the Trendsmcp Market Research MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 13 minutes.
Trendsmcp Market Research MCP server advertises 9 tools, including get_growth, get_top_trends, get_trends, trends___get_context, trends___get_growth.
Point your MCP client at this streamable-http endpoint: https://market-research.api.trendsmcp.ai/mcp
Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.