# Eclipse Namesake

> Eclipse Namesake is an open-source MCP server for agent identity. Identity-collision similarity screen over a fixture registry snapshot for agent names. It is available on self-hosted.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** self-hosted
- **Website:** https://eclipsebazaar.com
- **Repository:** https://github.com/cyan-eclipse-technologies-llc/eclipse-namesake-mcp
- **MCP Registry name:** io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-namesake-mcp
- **Categories:** [agent identity](https://ai-powered.com/categories/agent-identity), [naming and domains](https://ai-powered.com/categories/naming-and-domains)
- **Listing updated:** 2026-11-18

## About

Eclipse Namesake is a small MCP server that screens a name for similarity against a snapshot of registry entries. The registry entry describes it as an identity-collision check run over a fixture registry snapshot, and it states plainly that the output is not a trademark opinion.

The server comes from Cyan Eclipse Technologies, the company behind the Cyan Eclipse Bazaar marketplace. That marketplace lists MCP tools with scoped verdicts, and its catalog describes sibling servers such as Umbra, which watches for lookalike and typosquat agent identities. The catalog excerpt available here does not list Namesake's own tools, transports or package details, so what it exposes is not confirmed.

It suits developers who want an early signal of naming collisions before choosing an agent or product name. Because it works on fixture data, it is a screening aid rather than a legal or registry-of-record check.

## Features

- **Name similarity screening:** Compares a candidate name against entries in a registry snapshot to flag possible identity collisions.
- **Fixture registry snapshot:** Runs over a fixed snapshot of fixture data rather than a live registry.
- **Explicit legal disclaimer:** The listing states the result is not a trademark opinion.
- **MCP server interface:** Delivered as a Model Context Protocol server for use from AI clients.

## Good for

- Check an agent name for lookalikes before launch
- Flag potential naming collisions early in product naming
- Test identity-collision screening workflows against fixture data

## FAQ

### Is this a trademark check?

No. The registry description says it is a similarity screen and not a trademark opinion.

### What data does it screen against?

A fixture registry snapshot, not a live registry.

### Who publishes it?

Cyan Eclipse Technologies LLC, per the repository organisation and the Cyan Eclipse Bazaar site.

### Is Eclipse Namesake free?

Yes. Eclipse Namesake is open source, so you can use and self-host it for free.

### What are the best alternatives to Eclipse Namesake?

The closest alternatives to Eclipse Namesake are Eclipse Umbra MCP, Eclipse Continuity, Eclipse Attest MCP and Eclipse Genesis.

## Where this comes from

- Description: written from the project's website and its MCP Registry entry.

## Alternatives

- [Eclipse Umbra MCP](https://ai-powered.com/mcp/eclipse-umbra-mcp): Eclipse Umbra MCP is an MCP server for agent identity.
- [Eclipse Continuity](https://ai-powered.com/mcp/eclipse-continuity): Eclipse Continuity is an MCP server for agent identity.
- [Eclipse Attest MCP](https://ai-powered.com/mcp/eclipse-attest-mcp): Eclipse Attest MCP is an MCP server for agent identity.
- [Eclipse Genesis](https://ai-powered.com/mcp/eclipse-genesis): Eclipse Genesis is an open-source MCP server for agent identity.

---
Source: https://ai-powered.com/mcp/eclipse-namesake
