
Eclipse Benchkit
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.1Updated Nov 5, 2026
Free vendor self-bench SDK — Assay scorecard format + verifier spot-check sampling.
Overview
A local stdio MCP server from Eclipse Benchkit offering a free vendor self-bench SDK with an Assay scorecard format and verifier spot-check sampling.
- What you can do
- The listing names no tools, so capabilities are known only from the short description.
- It presents a free vendor self-bench SDK for benchmarking one's own offering.
- It covers an Assay scorecard format for structuring benchmark results.
- It covers verifier spot-check sampling, apparently for checking a subset of results.
- When to use it
- Consider it if you want an assistant to help structure self-benchmark scorecards or plan spot-check sampling for verification. Beyond that narrow scope the listing gives no detail, so evaluate it only if that specific workflow matters to you.
- 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 how it is installed and launched is not stated in the listing.
Installation
In SourceWeft
- Open Eclipse Benchkit 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
35% 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