Skip to main content
Glama
santapau10

cantkeepupwithai-mcp

by santapau10

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_AUTH_TOKENNoToken required for remote deployment (Streamable HTTP). Not used in stdio mode.
CKUWAI_API_BASE_URLNoBase URL of the backend against which requests are made.http://localhost:4000

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_trending_topicsA

Lists the AI trends currently tracked by cantkeepupwithai.com, ranked by mentions over the last 30 days. Each trend includes its mention count, week-over-week percent change, direction (up/down), and a 7-day sparkline.

get_trend_detailA

Fetches full detail for a single AI trend by its id: summary, why it matters, full mention history, and the source references (posts/articles) behind it.

get_daily_digestA

Fetches the daily AI news digest: a set of stories with headline, summary, why-it-matters, and sources. Omit date to get the latest published digest, or pass a date (YYYY-MM-DD) to get that day's digest.

list_digest_archiveA

Lists past daily digests (id, issue date, issue number, story count), paginated, newest first.

search_toolboxA

Full-site search across trends, digest stories, and the AI toolbox. Returns up to 5 matches per category. Query must be at least 2 characters.

get_pipeline_statsA

Fetches stats from the most recent ingestion pipeline run: sources checked, posts read, stories produced, and estimated reading minutes saved.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: trend lists vs. trend details, digest content vs. digest archive listing, full-site search, and pipeline stats. There is no functional overlap; even the two digest-related tools are easy to differentiate (content vs. metadata).

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: get_ for single resources, list_ for collections, and search_ for search. Naming conventions are uniform and predictable.

Tool Count5/5

With 6 tools, the set is well-scoped for the server's purpose of exposing AI trends and daily digests. Each tool covers a necessary operation without bloat.

Completeness5/5

The tool surface covers the core content lifecycle: browse trends, inspect trend details, fetch digests, list digest history, and search across content. The addition of pipeline stats is a bonus. No obvious gaps for public read-only access.

Maintenance

ActivitySlowing
ResponsivenessNo issues