MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Knowledge & memory

Attention Trends

Topic popularity, interest over time and trending topics from Wikipedia pageviews (x402 paid).

Checks passed
13 / 22

1 failed · 8 not measured

Median response
238 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
3

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Outdated check

Last connection measurement is over 24 hours old. Current availability is unknown.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
312

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 238 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name attention-trends.

  • Pass
    Lists tools

    tools/list returned 3 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 238 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 238 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    9 of 9 parameters have a description (100%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-10-22T15:23:27.02644Z, within 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Start using Attention Trends

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http attention-trends https://attention-trends.shopttyass-85f.workers.dev/mcp

Capabilities

Tools 3

compare_topic_popularity

Compare the popularity of 2-5 topics (brands, competitors, products, people, keywords) by Wikipedia pageviews. Returns one jointly normalized 0-100 interest-over-time series per topic, share of attention, the most popular and the fastest-rising topic, and per-topic trend direction and spikes. A Google-Trends-style popularity comparison based on Wikipedia reading rather than searches. Suited to competitor analysis, brand tracking and content planning. Paid: $0.01 USDC per call via x402.

Discovered
trending_topics

What is trending right now: the most-read Wikipedia articles for a language and day (default yesterday UTC), with views and rank, cleaned of the Main Page, special and other non-article pages. A daily signal of trending topics, breaking news and current events in 300+ Wikipedia language editions. Suited to trend discovery, news monitoring and content ideas. Paid: $0.005 USDC per call via x402.

Discovered
wikipedia_pageviews_trend

Wikipedia pageviews trend for any topic: interest over time as a measure of topic popularity and public attention. Free text (brand, person, product, event) is resolved to the matching Wikipedia article. Returns daily views normalized 0-100, 7-day and window % change, direction (rising, falling, stable, spiking), peak day and spike detection. Similar in purpose to Google Trends search interest, but it measures Wikipedia reading, not searches. Paid: $0.005 USDC per call via x402.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected238 ms3