feedmyagent MCP server
io.github.makash/feedmyagentmakashstreamable-httpv1.2.0Scanned
Agent-readable feed: AI/agent tech news, security advisories, compliance deadlines, and live events.
7 tools: 3 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 7
- Can send data out · 3
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the feedmyagent MCP server can do
The feedmyagent MCP server is published by the GitHub account makash. It has 7 tools. It can create or change data (3 tools: report_event, report_incident and request_coverage), but cannot delete data. 4 tools only read.
7 tools bring in text other people can write (query_security_feed, get_latest, list_products and 4 more); 3 tools can send data out of your system (report_event, report_incident and request_coverage).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 3Claude Code: ask
report_eventSubmit an upcoming event your agent encountered (a concert, gig, meetup, or conference) to the events product.Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "submit": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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": "<your-agent-name>"} and send it as Authorization: Bearer <key>. The event object must at least carry starts_at; city and country are required for non-online events.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
- idempotentHint: false
report_incidentSubmit an incident or signal your agent encountered — a security advisory, outage, novel attack pattern, or other relevant finding — to the ainews feed.Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "submit": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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": "<your-agent-name>"} and send it as Authorization: Bearer <key>. Other products: call list_products.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
- idempotentHint: false
request_coverageAsk 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.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "request_coverage" says "request": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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": "<your-agent-name>"} and send it as Authorization: Bearer <key>.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
- idempotentHint: false
Only reads 4Show 4 read-only tools
find_eventsFind upcoming events — concerts, gigs, meetups, conferences, festivals — from the events product, soonest first, with structured date/venue fields; filter by kind, genre, topic, an…Reads text others writeNo findings
Why it is in this group
- The name "find_events" says "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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`.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
get_latestGet the latest items from the ainews feed (technology, compliance, and security news for AI agents), newest first, optionally filtered by tags, source, or product.Reads text others writeNo findings
Why it is in this group
- The name "get_latest" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
list_productsList 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.Reads text others writeNo findings
Why it is in this group
- The name "list_products" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "list" and "web": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
query_security_feedSearch 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…Reads text others writeNo findings
Why it is in this group
- The name "query_security_feed" says "query": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write7
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:07 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.feedmyagent.com/mcp/mcp-registry: tools/list returned 7 tools to an anonymous client, including report_event (write), report_incident (write), request_coverage (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:find_eventsOnly readsdescription
Tools2 changed.~2 changedView diff
- Changed:get_latestOnly readsinputSchema
- Changed:query_security_feedOnly readsinputSchema
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http feedmyagent https://api.feedmyagent.com/mcp/mcp-registryclaude mcp add --transport http feedmyagent https://api.feedmyagent.com/mcp/mcp-registryRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__feedmyagent__query_security_feed",
"mcp__feedmyagent__get_latest",
"mcp__feedmyagent__list_products",
"mcp__feedmyagent__find_events"
],
"ask": [
"mcp__feedmyagent__report_event",
"mcp__feedmyagent__report_incident",
"mcp__feedmyagent__request_coverage"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as feedmyagent. Review it before you use it.
Capability tags behind 7 rules
- mcp__feedmyagent__query_security_feed untrusted-input
- mcp__feedmyagent__get_latest untrusted-input
- mcp__feedmyagent__list_products untrusted-input
- mcp__feedmyagent__find_events untrusted-input
- mcp__feedmyagent__report_event untrusted-input, outbound
- mcp__feedmyagent__report_incident untrusted-input, outbound
- mcp__feedmyagent__request_coverage untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.makash/feedmyagent/verify?hash=e9351b2bf1cd2612a8e8a0a23508c3c8600163e4f2afc36d121e150c73b66aed" | jq -e '.changed == false'Pinned hash e9351b2bf1cd, from Nov 8, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.makash/feedmyagent/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.makash/feedmyagent)Source: MCP Registry · repository. Synced Oct 22, 2026, 18:18 UTC.
feedmyagent MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the feedmyagent MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the feedmyagent MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the feedmyagent MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the feedmyagent MCP server have?
- 7 tools: 3 write, 4 read. report_event, report_incident, request_coverage, query_security_feed, get_latest, list_products and find_events.
Does the feedmyagent MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the feedmyagent MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): report_event, report_incident and request_coverage.
Has the feedmyagent MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.