
Eclipse Recall Witness
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.0Updated Oct 29, 2026
Recall campaigns, witnessed: NHTSA's as-served record sealed night by night.
Overview
A local stdio MCP server that seals NHTSA vehicle recall campaign records night by night, giving an assistant witnessed recall data.
- What you can do
- The listing gives no tool list, so capabilities are inferred from the description only.
- It is presented as a way to work with NHTSA recall campaigns as served by the agency.
- It records that data in nightly sealed snapshots, described as witnessed.
- No further functions, queries or outputs are documented.
- When to use it
- Consider it if you want an assistant to work with NHTSA vehicle recall campaign data and to keep a nightly, tamper-evident record of what the source served. There is too little documentation to recommend it for anything beyond that narrow purpose.
- 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. Network access to NHTSA data is implied by the description but not stated.
Installation
In SourceWeft
- Open Eclipse Recall Witness 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.0LatestOct 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.