Headline Vibes Analysis MCP Server

Created By
fred-ema year ago
MCP Server - get a heat check headlines
Overview

what is Headline Vibes?

Headline Vibes is a Model Context Protocol server that analyzes sentiment in news headlines from major US publications, providing insights into the overall sentiment of news coverage.

how to use Headline Vibes?

To use Headline Vibes, clone the repository, install the dependencies, build the server, and configure your NewsAPI key. You can then analyze headlines using natural language date input or specific dates.

key features of Headline Vibes?

  • Analyzes up to 100 headlines per request
  • Sentiment scoring on a 0-10 scale (0 = most negative, 10 = most positive)
  • Natural language date parsing for easier input
  • Detailed source distribution information
  • Sample headlines included in results

use cases of Headline Vibes?

  1. Analyzing sentiment trends in news over time
  2. Comparing sentiment across different news sources
  3. Understanding public sentiment on specific events or topics

FAQ from Headline Vibes?

  • What is the maximum number of headlines that can be analyzed at once?

Up to 100 headlines can be analyzed per request.

  • Do I need an API key to use Headline Vibes?

Yes, you need a NewsAPI key to access the news headlines.

  • How does the sentiment scoring work?

The sentiment is scored on a scale from 0 to 10, where 0 indicates the most negative sentiment and 10 indicates the most positive.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fred-em
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago