News API MCP Server

Created By
kcjonnyca year ago
MCP server for NewsAPI integration - enables AI assistants to search articles, get headlines, and browse news sources
Overview

what is News API MCP Server?

News API MCP Server is a Model Context Protocol (MCP) server that provides access to news content through the NewsAPI.org service, enabling AI assistants to search articles, get top headlines, and browse news sources.

how to use News API MCP Server?

To use the News API MCP Server, install the necessary dependencies, obtain a NewsAPI key, configure your environment, and build the project. You can then set up the MCP configuration to integrate it with your AI assistant.

key features of News API MCP Server?

  • Search through millions of articles from various news sources.
  • Retrieve breaking news headlines and top stories.
  • Discover and filter available news sources.

use cases of News API MCP Server?

  1. Integrating news search functionality into AI assistants.
  2. Providing users with real-time news updates and headlines.
  3. Enabling content aggregation from multiple news sources.

FAQ from News API MCP Server?

  • How do I get a NewsAPI key?

You can sign up at NewsAPI.org to get your free API key, which allows up to 100 requests per day.

  • Is there a limit on the number of requests?

Yes, the free tier allows up to 100 requests per day.

  • What programming language is used for this project?

The project is developed using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kcjonnyc
Star
0
Language
TypeScript
License
-
Tags

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.

8 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago