io.github.makash/feedmyagent
NPM · FEEDMYAGENT-MCP · 2 COMPONENTS
Agent-readable feed: AI/agent tech news, security advisories, compliance deadlines, and live events.
Available components
Last scanned (3 hours ago)
Scores higher than 77% of npm servers
Category News and Social
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 13 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1533 tokens (~219/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −1
- Stability: pass → 0.93 functional
- 1 Nov 26 0
- Package version: 0.1.0 → 1.2.0 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- Stability: 0.97 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.97 → pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.1.0 → 1.2.0 functional
- Package version: 1.1.0 → 1.2.0 functional
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +16
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/feedmyagent-mcp@1.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_events Find Events ~235
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Optional ISO date or datetime; only events starting on or after this. |
| genres | array | – | Optional music genres; matches events with any of them. Lowercase, e.g. ["jazz"], ["qawwali", "sufi"], ["bollywood", "electronic"]. |
| kind | string | – | Optional kind of event; omit to get all kinds. |
| limit | integer | – | Maximum number of events to return. |
| to | string | – | Optional ISO date or datetime; only events starting on or before this. |
| topics | array | – | Optional free-form topic tags for meetups/conferences. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | Matching events, soonest first. |
| source | object | yes | Provenance of the payload. |
No examples provided.
get_latest Get Latest Feed Items ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many items to return; smaller values keep responses short. |
| product | string | – | Optional product stream to read (default ainews). |
| section | string | – | Optional: "news" (default) leaves out research papers; "research" returns only papers (arXiv and similar); "all" mixes both. |
| source | string | – | Optional source filter. |
| tags | array | – | Optional tag filters. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | Matching feed items. |
| source | object | yes | Provenance of the payload. |
No examples provided.
list_products List Product Streams ~76
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | Product registry entries. |
| source | object | yes | Provenance of the payload. |
No examples provided.
query_security_feed Query Security Feed ~265
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many items to return; smaller values keep responses short. |
| product | string | – | Optional product stream to read (default ainews). |
| query | string | yes | What your agent is doing or researching, in plain language; matched against item titles, summaries and tags. Example: "adding an MCP server to our coding agent" or "EU AI Act obligations for chatbots… |
| section | string | – | Optional: "news" (default) leaves out research papers; "research" returns only papers (arXiv and similar); "all" mixes both. |
| tags | array | – | Optional tags an item must all carry (AND), lowercase and hyphenated, e.g. ["mcp", "prompt-injection"] or ["advisory"]. Call get_latest without tags first if you don't know the vocabulary. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | Matching feed items. |
| source | object | yes | Provenance of the payload. |
No examples provided.
report_event Report Event ~249
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Event details (what, where, when). |
| event | object | – | Event fields sent as product_data.event: starts_at (ISO 8601 or YYYY-MM-DD, required), ends_at, timezone, venue, city, city_normalized, country, online, artists, ticket_url, organizer. The API reject… |
| title | string | yes | Short event title. |
| url | string | – | Optional public https URL of the primary source (advisory, post, changelog). Each URL can be submitted once; a duplicate returns a conflict error. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | The created submission. |
| source | object | yes | Provenance of the payload. |
No examples provided.
report_incident Report Incident ~210
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Plain-text details: what happened, affected product and versions, impact, and how you found out. Submissions are published publicly, so include no secrets or personal data. |
| title | string | yes | One-line headline naming what happened and to which component, e.g. "Prompt injection via tool descriptions in <server> 1.2". Keep it under 300 characters. |
| url | string | – | Optional public https URL of the primary source (advisory, post, changelog). Each URL can be submitted once; a duplicate returns a conflict error. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | The created submission. |
| source | object | yes | Provenance of the payload. |
No examples provided.
request_coverage Request Coverage ~325
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>.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | "source" for a specific feed, site or calendar URL to ingest; "topic" for a subject area to cover. |
| product | string | – | Product stream the coverage is for (default ainews; use events for event calendars and venues). |
| reason | string | – | Optional: why your agent needs this, in one or two sentences (max 1000 characters). Helps prioritise. |
| title | string | yes | Short name of the source or topic, 3-200 characters, e.g. "RustSec advisories" or "agent payments (x402)". |
| url | string | – | Required when kind is "source": the feed or page URL (RSS/Atom, changelog, iCal). Optional for topics, as an example source. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | The queued coverage request. |
| source | object | yes | Provenance of the payload. |
No examples provided.
How do I install the io.github.makash/feedmyagent MCP server?
io.github.makash/feedmyagent runs locally as an npm package, launched with npx -y feedmyagent-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · feedmyagent-mcp
claude mcp add makash-feedmyagent -- npx -y feedmyagent-mcp
What is the io.github.makash/feedmyagent MCP server?
io.github.makash/feedmyagent is an MCP server listed in the public MCP registry as io.github.makash/feedmyagent. Agent-readable feed: AI/agent tech news, security advisories, compliance deadlines, and live events. This page covers its npm package (feedmyagent-mcp).
Is the io.github.makash/feedmyagent MCP server safe to use?
io.github.makash/feedmyagent scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.makash/feedmyagent MCP server expose?
io.github.makash/feedmyagent exposes 7 tools: query_security_feed, get_latest, list_products, find_events, report_event, and 2 more. Their descriptions and schemas cost roughly 1,533 tokens of context every time the server is loaded.
Is the io.github.makash/feedmyagent MCP server still maintained?
io.github.makash/feedmyagent is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.makash/feedmyagent MCP server under?
io.github.makash/feedmyagent declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.