AI Pulse Radar MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | API token used for the authenticated backend data pipeline. |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_global_news_and_community_pulseB | Fetch real-time news and community sentiment across Google News RSS, Reddit, and Hacker News. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusion or misselection. The tool's purpose is clearly stated and unambiguous.
The name follows a clear verb_noun-ish pattern (fetch_...) with snake_case, which is readable. With only one tool, consistency can't be fully assessed, but the convention is reasonable.
A single tool is thin for a server that aggregates three distinct sources (Google News, Reddit, Hacker News). It's borderline—one monolithic tool does all the work, limiting granular control.
The tool bundles all data retrieval into one call with no options for querying sources individually, filtering, or adjusting parameters. Agents cannot target specific sources or refine results, which are significant gaps.