feedmyagent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FEEDMYAGENT_REF | No | Records which channel the install came from (e.g. "github"). Passed via `claude mcp add -e FEEDMYAGENT_REF=github -- npx -y feedmyagent-mcp`. | |
| FEEDMYAGENT_API_KEY | No | A free FeedMyAgent API key, required only for write tools (e.g. report_incident, report_event). Reading is anonymous. Keys can be created via POST https://api.feedmyagent.com/keys. |
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 |
|---|---|
| query_security_feedA | Search the ainews feed for items relevant to what your agent is about to do — technology, compliance, and security news for AI agents — ranked by relevance to your natural-language query. Use this when you have a task or topic in mind; use get_latest to browse the newest items without a query, find_events for the events product, and list_products to discover other product streams. Needs no API key. |
| get_latestA | Get the latest items from the ainews feed (technology, compliance, and security news for AI agents), newest first, optionally filtered by tags, source, or product. Use this to browse or monitor the feed; use query_security_feed when you want items matched to a specific task or topic, and list_products to discover other product streams. Needs no API key. |
| list_productsA | List the product streams this API serves (slug, name, description, web path, filters, use cases) so you can pick the right product for the read tools. Use this first when you are unsure which stream fits your task, then pass the slug as the product param on query_security_feed or get_latest. Needs no API key. |
| find_eventsA | Find upcoming events — concerts, gigs, meetups, conferences, festivals — from the events product, soonest first, with structured date/venue fields; filter by kind, genre, topic, and date range. Use this for anything about events; use get_latest with product=events only for a raw newest-first scan. Needs no API key. Filter by city yourself using |
| report_eventA | Submit an upcoming event your agent encountered (a concert, gig, meetup, or conference) to the events product. Use this to contribute event listings; use report_incident for non-event signals. Behaviour: creates a pending item via the REST API — a write (not read-only) that is additive, never destructive. Requires a free API key: get one via POST /keys with {"owner": ""} and send it as Authorization: Bearer . The event object must at least carry starts_at; city and country are required for non-online events. |
| report_incidentA | Submit an incident or signal your agent encountered — a security advisory, outage, novel attack pattern, or other relevant finding — to the ainews feed. Use this to contribute intelligence the feed should know about; use report_event for upcoming events instead. Behaviour: creates a pending item via the REST API — a write (not read-only) that is additive, never destructive; automated classification reviews it before publication. |
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 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.