
Eclipse Crawlway
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.1Updated Oct 29, 2026
Pay-per-crawl licensing receipts: sealed identity+terms+fingerprint binding. LOCAL/fixture only.
Overview
Eclipse Crawlway is a local, desktop-only MCP server for pay-per-crawl licensing receipts that seal identity, terms and fingerprint binding.
- What you can do
- Issues and handles pay-per-crawl licensing receipts, binding a crawler's identity, agreed terms and a fingerprint into a sealed record.
- Works only in a local or fixture mode, so it is meant for testing and development rather than live licensing.
- No tools are listed in the manifest, so the exact operations an assistant can call are not documented.
- When to use it
- Consider it if you are building or testing pay-per-crawl licensing flows and want an assistant to work with sealed receipt records locally. It is not suited to production licensing or real crawler traffic, since it is described as local/fixture only.
- Requirements
- Runs as a local process over stdio on a desktop machine; no web executable. No packages, environment variables, headers or authentication are declared, so setup details are undocumented.
Installation
In SourceWeft
- Open Eclipse Crawlway 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.