
Eclipse Namesake
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.1Updated Oct 29, 2026
Identity-collision similarity screen over a fixture registry snapshot; not a trademark opinion.
The publisher's own server: Namesake — baby name catalog and guides
Overview
A local stdio MCP server that runs an identity-collision similarity screen over a fixture registry snapshot, not a trademark opinion.
- What you can do
- Runs an identity-collision similarity screen against a fixture registry snapshot.
- Returns similarity results for names checked against that snapshot.
- The description lists no individual tools, so the exact operations are not documented.
- It is explicitly framed as a screening aid rather than a trademark opinion.
- When to use it
- Worth considering when you want a quick, local similarity check of a name against a bundled fixture registry snapshot before deeper research. Not a substitute for professional trademark clearance or legal advice.
- Requirements
- Runs as a local process on the user's machine over stdio, desktop only. No packages, environment variables, headers or authentication are declared, so setup details are not documented.
Installation
In SourceWeft
- Open Eclipse Namesake in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.1LatestOct 29, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.