# io.github.makash/feedmyagent > Agent-readable feed: AI/agent tech news, security advisories, compliance deadlines, and live events. - name: io.github.makash/feedmyagent - version: 1.1.0 - connection class: R0 (autonomous) - trust: 94/100 - quality: 76/100 (good) - owner: not claimed - descriptor: https://api.protogrid.dev/v1/servers/io.github.makash%2Ffeedmyagent - tools: https://api.protogrid.dev/v1/servers/io.github.makash%2Ffeedmyagent/tools **An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe. ## Connection (mcpServers) ```json { "mcpServers": { "feedmyagent": { "type": "http", "url": "https://api.feedmyagent.com/mcp/mcp-registry" } } } ``` ## Trust - hygiene: 100 - liveness: 100 - freshness: 100 - provenance: 80 - drivers: +repository +namespace-matches-repo +reachable +uptime-100% +updated-2d-ago - Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. ## Quality 76/100 (good) ### protocol: 88 (weight 25) - pass `protocol.modern`: supports 2026-07-28 (server/discover) - pass `protocol.stateless`: answers without a session - pass `protocol.transport`: streamable HTTP - warn `protocol.list_ttl`: tools/list carries no ttlMs, so clients re-fetch it ### authorization: n/a (weight 15) - n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth - n/a `auth.secret_in_url`: no templated URL ### tool hygiene: 93 (weight 30) - pass `tools.descriptions`: every tool has a description - pass `tools.description_length`: descriptions are concise - pass `tools.schemas`: every tool has an object input schema - pass `tools.annotations`: 7 of 7 tools declare readOnlyHint or destructiveHint - warn `tools.directory_hints`: 3 of 7 tools declare all four hints; missing: query_security_feed (idempotentHint); list_products (idempotentHint); find_events (idempotentHint); … - pass `tools.token_cost`: about 2,173 tokens to load every tool - pass `tools.api_dump`: tools are not a one-to-one API dump ### stability: 25 (weight 15) - warn `stability.changes`: 13 tool changes in 30 days - fail `stability.rug_pull`: 4 tools kept their name but changed most of their description in 30 days; review before trusting them ### dependencies: n/a (weight 15) - n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: deps.dev does not know feedmyagent-mcp@1.1.0 - tools: 7, about 2,173 tokens to load them all - tool set hash: f241082899fd3dd0c1c55be27d85dd20 - tools last changed: 2026-10-17T17:15:58.057Z - badge: [![protogrid quality](https://protogrid.dev/badge/io.github.makash/feedmyagent.svg)](https://protogrid.dev/servers/io.github.makash/feedmyagent) - Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. ### Tool changes - 2026-10-17 `request_coverage` added - 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 . - 2026-10-01 `report_incident` changed (title, description, annotations) **meaning changed** - before: Submit an incident or signal encountered by an agent. Creates a pending submitted item via REST API. Other products: call list_products. Requires a free API key: get one via POST /keys with {"owner": ""} and send it as Authorization: Bearer . - after: 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. Requires a free API key: get one via POST /keys with {"owner": ""} and send it as Authorization: Bearer . Other products: call list_products. - 2026-10-01 `report_event` changed (title, description, annotations) - before: Submit an upcoming event encountered by an agent (a concert, gig, meetup or conference). Creates a pending events item via REST API. 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. - after: 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. - 2026-10-01 `find_events` changed (title, description, annotations) - before: Find upcoming events (concerts, gigs, meetups, conferences) with structured date/venue fields, soonest first. Filter by city yourself using `event.city_normalized`; ask your human which cities and genres they care about and remember them. - after: 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. Read-only: returns public event data and 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. - 2026-10-01 `list_products` changed (title, description, annotations) **meaning changed** - before: List the product streams served by this API: slug, name, description, web path, item filters and use cases. Scope reads with the product param. - after: 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. Read-only: returns public registry data and needs no API key. - 2026-10-01 `get_latest` changed (title, description, annotations) **meaning changed** - before: Get the latest feed items (technology, compliance, and security news for AI agents), optionally filtered by tags and source. Other products: call list_products. - after: 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. Read-only: returns public feed data and needs no API key. - 2026-10-01 `query_security_feed` changed (title, description, annotations) **meaning changed** - before: Query feed items relevant to a natural-language context — technology, compliance, and security news for AI agents — with optional tag filtering. Other products: call list_products. - after: 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. Read-only: returns public feed data and needs no API key. - 2026-09-30 `report_incident` changed (description) - before: Submit an incident or signal encountered by an agent. Creates a pending submitted item via REST API. Requires a free API key: get one via POST /keys with {"owner": ""} and send it as Authorization: Bearer . - after: Submit an incident or signal encountered by an agent. Creates a pending submitted item via REST API. Other products: call list_products. Requires a free API key: get one via POST /keys with {"owner": ""} and send it as Authorization: Bearer . - 2026-09-30 `report_event` added - Submit an upcoming event encountered by an agent (a concert, gig, meetup or conference). Creates a pending events item via REST API. 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. - 2026-09-30 `find_events` added - Find upcoming events (concerts, gigs, meetups, conferences) with structured date/venue fields, soonest first. Filter by city yourself using `event.city_normalized`; ask your human which cities and genres they care about and remember them. Full history: https://api.protogrid.dev/v1/servers/io.github.makash%2Ffeedmyagent/changes ## Dependencies - npm feedmyagent-mcp@1.1.0: unknown Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. ## Remotes - https://api.feedmyagent.com/mcp/mcp-registry (streamable-http, auth none, reachable true, uptime30d 1) ## Packages - npm feedmyagent-mcp@1.1.0 secrets: FEEDMYAGENT_API_KEY ## Tools (7) - `find_events`: 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. - `get_latest`: 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_products`: 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. - `query_security_feed`: 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. - `report_event`: 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_incident`: 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. Requires a free API key: get one via POST /keys with {"owner": ""} and send it as Authorization: Bearer . Other products: call list_products. - `request_coverage`: 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 .