MCP servers › io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC › eclipse-feedforge-mcp
MCP server · registry snapshot 2026-10-27
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-feedforge-mcp
Eclipse Feedforge — the publisher's title
by CYAN-ECLIPSE-TECHNOLOGIES-LLC · GitHub account (the registry's namespace rule)source link does not open (missing or private)Website ↗
Messy catalog to agent-grade feed with per-attribute provenance. LOCAL/fixture only. — the publisher's description
Summary
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-feedforge-mcp is an MCP server listed in the official MCP registry at version 0.1.1, under the namespace of the GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLC. Its linked repository, github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-feedforge-mcp, does not open publicly (missing or private).
Record checks
0 of 2 record checks met · 7 do not apply
- not met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: not an npm or PyPI package
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself
Key facts
- Repository
- link does not open publicly
- Last tested
- not tested
Tool list
Not read: The registry entry declares no package and no remote endpoint, so there is nothing to run. So there is no tool-list size and no result from the three APIs.
Worth knowing before you connect it
- The linked repository does not open publicly, so the code cannot be reviewed through it.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 0.1.1, published 2026-10-27 (registry, as of the 2026-10-27 snapshot)
- First listed version
- 2026-10-27 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-10-27
- Package and repository
- checked 2026-10-27
Dead or stale signals
1 found in the records we hold
- The repository link does not open: GitHub answered HTTP 404 (it does not exist, or it is private). — api.github.com · 2026-10-27 · all servers with this fact
Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-10-26, listed on 2026-10-27 with version 0.1.1 (published 2026-10-27).
Source: the official MCP Registry list on 2026-10-26 and on 2026-10-27.
What it is
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Repository github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-feedforge-mcp | Does not open (not found or private) | differs | api.github.com · 2026-10-27 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC · 143 servers
- Repository
- github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-feedforge-mcp — does not open publicly
Source: the registry entry and api.github.com · 2026-10-27.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating0 of 2 record checks met · 7 do not apply
- Not ranked by downloads: not an npm or PyPI package
- Not ranked by stars: no public GitHub repository
- Not metRegistry entry is active and says how to run itThe entry lists no package and no remote address, so a client cannot run it.What changes this check: This check reads the registry entry's status and whether it lists a package or a remote address. Marking an entry deprecated is the publisher's own choice. The registry's documentation says a published version's metadata cannot be changed; a new server.json with a unique version string is how an entry is updated. Versioning published MCP servers
- Not metSource repository link opensThe linked repository returned HTTP 404: it does not exist or is private.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierThe entry lists no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnThe entry lists no package.
- Does not applynpm package carries build provenance (attestation)The entry lists no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesThe entry lists no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-27. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-feedforge-mcp
Answered from the data aboveWho publishes io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-feedforge-mcp?
The registry ties the namespace io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC to the GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLC; only its owner can publish under it. Its linked repository, github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-feedforge-mcp, does not open publicly (missing or private). These are facts from the registry and GitHub, not a rating.
Is io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-feedforge-mcp safe to install?
We do not rate servers as safe or unsafe. 0 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: The repository it links to does not open publicly, so its code cannot be inspected through that link. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-feedforge-mcp been security tested?
Not yet. The registry entry declares no package and no remote endpoint, so there is nothing to run.
Where is the source code of io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-feedforge-mcp?
The registry links to github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-feedforge-mcp, but that link does not open publicly, so the code cannot be inspected through it.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1The registry entry declares no package and no remote endpoint, so there is nothing to run. — the server's own choice
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-feedforge-mcp: MCP server record.” Data checked 2026-10-27. https://protocolprobe.com/mcp/servers/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-feedforge-mcp
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-feedforge-mcp)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology