
Eclipse Archivist
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.2Updated Oct 29, 2026
Capture witness: content, headers + TLS cert sealed as one signed bundle; fixture captures only.
Overview
Eclipse Archivist is a local MCP server that captures web content, headers and TLS certificate as one signed bundle, for fixture captures only.
- What you can do
- Capture a witness of a web page: content, response headers and TLS certificate sealed together as a single signed bundle.
- Produce fixture captures intended for later reference or testing.
- No tool list, README or server instructions are published, so the exact operations and output format are not documented here.
- When to use it
- Consider it when you need a tamper-evident, signed record of what a page served, including its TLS certificate, for fixtures or evidence-style reference. It is not a general browsing or scraping tool.
- Requirements
- Runs as a local process over stdio on a desktop machine; no packages, environment variables, headers or authentication are declared. Network access to the target sites is implied by capturing content, headers and certificates.
Installation
In SourceWeft
- Open Eclipse Archivist 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.2LatestOct 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.