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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago