io.github.makash/feedmyagent
REMOTE · API.FEEDMYAGENT.COM · 2 COMPONENTS
Agent-readable feed: AI/agent tech news, security advisories, compliance deadlines, and live events.
Available components
Last scanned (22 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 4 Nov 2026.
Category News and Social
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1666 tokens (~238/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 Management67
- Stability observed for 20 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 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Tool “find_events” rewrote its description, which is the text the model reads security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 0
- “query_security_feed” added an optional parameter “section” cosmetic
- “get_latest” added an optional parameter “section” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
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 4 Nov 2026 · Probed https://api.feedmyagent.com/mcp/mcp-registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=feedmyagent.com | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | fe97f301d9f1a350139493f0a2f5a294 |
| SANs: feedmyagent.com, api.feedmyagent.com, *.api.feedmyagent.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.feedmyagent.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| feedmyagent.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.feedmyagent.com/mcp/mcp-registry | Verified | 200 | |
| http (plaintext) | http://api.feedmyagent.com/mcp/mcp-registry | Inconclusive | 405 |
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 ~221
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`.
| 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 ~250
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.
| 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 is a hosted endpoint at https://api.feedmyagent.com/mcp/mcp-registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.feedmyagent.com
claude mcp add --transport http makash-feedmyagent 'https://api.feedmyagent.com/mcp/mcp-registry'
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 hosted endpoint (https://api.feedmyagent.com/mcp/mcp-registry).
Is the io.github.makash/feedmyagent MCP server safe to use?
io.github.makash/feedmyagent scores 74 out of 100 on VerifyMCP. 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,559 tokens of context every time the server is loaded.
Does the io.github.makash/feedmyagent MCP server require authentication?
No. We connected to io.github.makash/feedmyagent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.