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.

Hyperaware: What's Trending Today

REMOTE · API.HYPERAWARE.LIVE

What's trending today on Google, TikTok, YouTube, Reddit. Public board plus MCP

67 Trust /100

Last scanned (8 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Search and Retrieval

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 Security74
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1803 tokens (~450/item across 4 items; 4 tools + 0 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 Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.

  • 18 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 17 Oct 26 67

    First indexed and scored.

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 18 Oct 2026 · Probed https://api.hyperaware.live/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.trendsmcp.ai CN=Amazon RSA 2048 M04,O=Amazon,C=US 15 Oct 2026 30 Apr 2027 RSA 2048 SHA256-RSA 40191d69ba06c1f9a051fb4ea302789
SANs: api.trendsmcp.ai, api.trendsconnector.com, *.api.trendsmcp.ai, api.trendsapi.ai, api.hyperaware.live, *.api.hyperaware.live, *.api.trendsconnector.com, *.api.trendsapi.ai
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.hyperaware.live. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
live. present 36322 8 Verified
hyperaware.live. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.hyperaware.live/mcp Verified 200
http (plaintext) http://api.hyperaware.live/mcp HTTPS enforced 301 https://api.hyperaware.live/mcp
MCP tools · 4 exposed · ~1,803 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
trends___get_growth ~598

Point-to-point growth for a keyword on one or more sources. Each window is a preset string (12M, 3M, YTD, and the other listed periods). Values are on a 0-100 scale, plus absolute volume when available. Designed for growth questions; for charting or custom math, get_time_series provides the full series. app downloads and app rankings are keyword sources (Android bundle ID). They are not the App Store / Google Play live boards on get_top_trends. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

NameTypeReqDescription
keywordstringyesWhat to look up. The string format is required by source. Standard sources (google search, google images, google news, google shopping, youtube, wikipedia, tiktok, reddit, amazon, news sentiment, new…
percent_growtharray–Growth windows. Default if omitted: ['12M']. Each item must be a preset string: '7D', '1W', '14D', '2W', '30D', '1M', '2M', '3M', '6M', '9M', '12M', '1Y', '18M', '24M', '2Y', '36M', '3Y', '48M', '4Y'…
sourcestringyesOne source, or comma-separated sources (e.g. 'amazon, tiktok, youtube'). Valid: 'google search', 'google images', 'google news', 'google shopping', 'youtube', 'wikipedia', 'tiktok', 'reddit', 'amazon…

No output schema declared.

No examples provided.

trends___get_time_series ~387

Full historical series for one keyword and one source (0-100 values, plus volume when available). Suited for charting or custom math. Live 'what's trending now' boards are on get_top_trends. get_growth answers most growth questions with less data. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

NameTypeReqDescription
keywordstringyesWhat to look up. The string format is required by source. Standard sources (google search, google images, google news, google shopping, youtube, wikipedia, tiktok, reddit, amazon, news sentiment, new…
sourcestringyesExactly one source per request. Valid: 'google search', 'google images', 'google news', 'google shopping', 'youtube', 'wikipedia', 'tiktok', 'reddit', 'amazon', 'news sentiment', 'news volume', 'npm'…

No output schema declared.

No examples provided.

trends___get_top_posts ~150

Live top posts for one hashtag on one social source. Fetched live on every call; nothing is stored. For when the user already has a hashtag and wants the posts winning on it. get_top_trends ranks the hashtags themselves. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

NameTypeReqDescription
keywordstringyesThe hashtag, with or without '#'. Spaces are removed. Example: 'bookstagram' or '#fitness'.
limitinteger–Max posts to return. Default 20, min 1, max 20.
sourcestringyesExactly one source per request. Valid: 'tiktok', 'instagram'.

No output schema declared.

No examples provided.

trends___get_top_trends ~668

Live top-trending board for exactly one feed type. No keyword. For 'Amazon Best Sellers by Category', 'Google Trends by Category', 'Top Websites', 'Substack by Category', and 'TikTok Trending Hashtags by Category', category selects the board. Default sort is current rank. Use sort='rank_change' for climbers vs a prior snapshot (window 1d, 3d, 7d, 14d, or 30d). If the requested board is not in the database yet (for example a country that is not collected on the schedule), the board is fetched live. App Store Top Free, App Store Top Paid, and Google Play are live store boards, not keyword lookups. App history is available via get_growth or get_time_series with source app downloads or app rankings and an Android bundle ID. Live boards are only available here, not via get_time_series. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

NameTypeReqDescription
categorystring–Pass this whenever type is 'Amazon Best Sellers by Category', 'Google Trends by Category', 'Top Websites', 'Substack by Category', or 'TikTok Trending Hashtags by Category'. Use the official name. Wi…
countrystring–Optional ISO 3166-1 alpha-2 code (US, GB, JP). Aliases like 'USA' or 'United States' resolve to US. Omit for the default US board. Only for Google Trends, Google Trends by Category, YouTube Trending,…
limitinteger–Max rows to return. Default 25, min 1, max 200.
offsetinteger–Rows to skip for pagination. Default 0.
sortstring–How to rank the board. 'rank' (default): current leaders. 'rank_change': biggest climbers vs a prior snapshot. Mover rows include rank, keyword, prev_rank, and rank_change.
typestringyesExactly one live feed. Valid: 'Amazon Best Sellers Top Rated', 'Amazon Best Sellers by Category', 'App Store Top Free', 'App Store Top Paid', 'GitHub', 'Google News Top News', 'Google Play', 'Google…
windowstring–Lookback used only when sort is 'rank_change'. One of '1d', '3d', '7d', '14d', '30d'. Default '30d'. Short windows only work on daily feeds; weekly and monthly feeds return a note pointing to a longe…

No output schema declared.

No examples provided.

Install

How do I install the Hyperaware: What's Trending Today MCP server?

Hyperaware: What's Trending Today is a hosted endpoint at https://api.hyperaware.live/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 · api.hyperaware.live

# add to Claude Code
claude mcp add --transport http live-hyperaware-whats-trending 'https://api.hyperaware.live/mcp'
Common questions

What is the Hyperaware: What's Trending Today MCP server?

Hyperaware: What's Trending Today is an MCP server listed in the public MCP registry as live.hyperaware/whats-trending. What's trending today on Google, TikTok, YouTube, Reddit. Public board plus MCP. This page covers its hosted endpoint (https://api.hyperaware.live/mcp).

Is the Hyperaware: What's Trending Today MCP server safe to use?

Hyperaware: What's Trending Today scores 67 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 Hyperaware: What's Trending Today MCP server expose?

Hyperaware: What's Trending Today exposes 4 tools: trends___get_growth, trends___get_time_series, trends___get_top_posts, trends___get_top_trends. Their descriptions and schemas cost roughly 1,803 tokens of context every time the server is loaded.

Does the Hyperaware: What's Trending Today MCP server require authentication?

No. We connected to Hyperaware: What's Trending Today without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Hyperaware: What's Trending Today MCP server still maintained?

Hyperaware: What's Trending Today is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.