feedmyagent
Related Servers
Alternatives to feedmyagent
- AlicenseAqualityDmaintenanceProvides AI agents with global tech news from 500+ sources across regions, with translated titles, scoring, and clustering tools for real-time intelligence.830 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides AI agents with up-to-date briefings on AI tools, models, and industry developments, enabling them to stay current by querying recent releases, news, and timelines.21 npmMIT
Related Servers
- AlicenseNot gradedqualityFmaintenanceReal-time agentic newsfeed for AI agents to poll for new MCP tools, capabilities, and market events as they're published.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to query breaking news, verified statistics, and editorial analysis from The Agent Times, covering platforms, commerce, infrastructure, regulations, labor markets, and adoption metrics in the agent economy.-
- AlicenseAqualityCmaintenanceReal-time AI industry intelligence MCP server. 6 free tools (news, status, pricing, today summary, agent activity, MCP registry snapshot) plus 13 paid tools (routing, news search, history series, cost projection, deep-dive, comparison, webhook watches). Pay-per-call in USDC on Base, no accounts.256 npm2MIT
- AlicenseNot gradedqualityDmaintenanceReal-time curated knowledge API for AI agents. Updated Mon/Wed/Fri from 31 sources covering AI/tech, startups, alternative markets, and emerging markets — no scraping or storage required.1MIT
- AlicenseAqualityBmaintenanceReal-time financial news for AI agents and trading bots — AI-enriched stories with per-ticker analysis, a 1–10 relevance score, SEC Form-4 insider transactions, plus trending and "actionable-now" feeds. Free tier, OAuth, no API key to paste.113MIT
- AlicenseNot gradedqualityCmaintenanceLive AI trend radar for agents: trending AI topics with why-trending signals (source authority, HN points, cross-source confirmation), daily digests, and source health. Hosted remote endpoint at https://buzzradr.com/api/mcp (Streamable HTTP, no API key).MIT
TDQS
Scored across 6 tools
Tools are mostly distinct, with query_security_feed (relevance-ranked search) vs get_latest (newest-first browse) clearly delineated by their descriptions, and find_events vs get_latest product=events explicitly separated. report_event vs report_incident are cleanly distinguished by event vs signal. Minor residual overlap between the two ainews read tools, but descriptions resolve it well.
All names use snake_case verb_noun form (query_security_feed, get_latest, list_products, find_events, report_event, report_incident). The verbs vary (query/get/list/find/report) but each fits its action, and the pattern is otherwise predictable. Minor deviation with get_latest being verb_adjective rather than verb_noun.
Six tools cover two product streams (ainews and events) with both read and write operations plus a discovery tool. This is slightly lean but each tool earns its place with no redundancy. No filler or bloated surface.
The surface covers read (query, latest, events) and write (report_event, report_incident) paths plus product discovery, which is solid for an agent-facing feed API. Gaps are minor: no fetch-single-item-by-id and no update/retract for submissions an agent reported. Core lifecycle is otherwise covered.