Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FEEDMYAGENT_REFNoRecords which channel the install came from (e.g. "github"). Passed via `claude mcp add -e FEEDMYAGENT_REF=github -- npx -y feedmyagent-mcp`.
FEEDMYAGENT_API_KEYNoA 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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 event.city_normalized; ask your human which cities and genres they care about and remember them.

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.

request_coverageA

Ask FeedMyAgent to start covering a source (a feed, site, changelog or event calendar your agent relies on) or a topic it does not cover yet. Use this when query_security_feed, get_latest or find_events return nothing useful for a subject you need, or when you know a primary source the feed should ingest; use report_incident or report_event to submit a single item instead. Behaviour: queues the request for the maintainer to review; a repeat request for the same source or topic adds a vote instead of a duplicate, and nothing is ingested until the request is accepted. Requires a free API key: get one via POST /keys with {"owner": ""} and send it as Authorization: Bearer .

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 7 tools

Disambiguation4/5

Most tools have clearly distinct purposes: find_events (events), get_latest and query_security_feed (browse vs. search the ainews feed), list_products (discovery), and the two report_* writes. The only real overlap is get_latest vs. query_security_feed on the same feed, plus find_events vs. get_latest with product=events, but the descriptions proactively disambiguate these cases.

Naming Consistency5/5

All seven tools follow a consistent snake_case verb_noun pattern (find_events, list_products, report_event, report_incident, request_coverage, query_security_feed). get_latest is the one mild deviation (adjective rather than noun target) but it's still a clean verb_thing construction and reads naturally.

Tool Count5/5

Seven tools is well-scoped for a feed/reporting API: four read/discovery operations, two submission operations, and one coverage-request operation. Every tool earns its place with no redundant or filler entries.

Completeness4/5

The surface covers the core lifecycle: discovering products, reading/browsing/searching feeds, submitting incidents and events, and requesting new coverage. Minor gaps exist—no tool to fetch or manage a single reported item and key creation is only done via raw REST (POST /keys) rather than a tool—but these are workable.

Maintenance

ActivityActive
ResponsivenessResponsive