eval-hub-mcp
This package distributes the compiled Go eval-hub-mcp server binary for multiple
platforms. It installs the binary directly into your bin/ directory (Scripts/ on Windows) with no
Python wrapper — no argument rewriting, no subprocess overhead, no Python
runtime required at execution time.
Installation
pip install eval-hub-mcp
Capabilities
With EVALHUB_BASE_URL, EVALHUB_TOKEN, and EVALHUB_TENANT configured, the server exposes MCP tools (discover_providers, submit_evaluation, get_job_status, cancel_job), resources (evalhub://providers, evalhub://benchmarks, evalhub://collections, evalhub://jobs, and more), and prompts (edd_workflow, evaluate_model, compare_runs). See MCP.md in the eval-hub repository for the full reference.
Usage
# Run in stdio mode (default, for IDE integration)
evalhub-mcp
# Run in HTTP mode
evalhub-mcp --transport http --port 3001
# Show version
evalhub-mcp --version
Supported Platforms
- Linux: x86_64, arm64
- macOS: x86_64 (Intel), arm64 (Apple Silicon)
- Windows: x86_64
For eval-hub-sdk Users
Note:
eval-hub-sdk[mcp]currently installs a Python FastMCP-based server. This will be replaced witheval-hub-mcp(the Go binary distributed by this package) in a future release.
If you're using eval-hub-sdk, you can install the MCP server as an extra:
pip install eval-hub-sdk[mcp]
For more information, see the eval-hub-sdk repository.
License
Apache-2.0
Release files for eval-hub-mcp 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| eval_hub_mcp-1.0.2-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details for eval_hub_mcp-1.0.2-py3-none-win_amd64.whl |
| eval_hub_mcp-1.0.2-py3-none-manylinux_2_17_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details for eval_hub_mcp-1.0.2-py3-none-manylinux_2_17_x86_64.whl |
| eval_hub_mcp-1.0.2-py3-none-manylinux_2_17_aarch64.whl | Python 3 | none | Linux glibc 2.17+ ARM64 | Details for eval_hub_mcp-1.0.2-py3-none-manylinux_2_17_aarch64.whl |
| eval_hub_mcp-1.0.2-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details for eval_hub_mcp-1.0.2-py3-none-macosx_11_0_arm64.whl |
| eval_hub_mcp-1.0.2-py3-none-macosx_10_9_x86_64.whl | Python 3 | none | macOS 10.9+ x86-64 | Details for eval_hub_mcp-1.0.2-py3-none-macosx_10_9_x86_64.whl |
Total release size: 26.7 MB
Release files / eval_hub_mcp-1.0.2-py3-none-win_amd64.whl
| Download URL | eval_hub_mcp-1.0.2-py3-none-win_amd64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7d2980d8ce8407a8a607de4e0d8a2c5ab60d7e42871146ea8ca0e2354e385bc2
|
|
BLAKE2b-256 checksum How to use checksums |
5b3afd8e2f8c3c9ee76a809e913533160a4eb64ac41eda55125477c4e723f67b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / eval_hub_mcp-1.0.2-py3-none-manylinux_2_17_x86_64.whl
| Download URL | eval_hub_mcp-1.0.2-py3-none-manylinux_2_17_x86_64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
0a257e65608a3c704ae3e03c65ee5abbc69deebb91ad4e026168d509f4e2cde0
|
|
BLAKE2b-256 checksum How to use checksums |
f0827a4e62e5aa5c13c65955de8fca48781d23a61813003cfba0efdde9b56bf5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / eval_hub_mcp-1.0.2-py3-none-manylinux_2_17_aarch64.whl
| Download URL | eval_hub_mcp-1.0.2-py3-none-manylinux_2_17_aarch64.whl |
|---|---|
| Size | 4.9 MB |
| Tags | Linux glibc 2.17+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
f8daf1089ff129ab87b7230dc40e89d212d86501cf48803161924edd58442ff0
|
|
BLAKE2b-256 checksum How to use checksums |
3419e9ced0b95577ea37bd1c8585d6d1d739db1028cfb3b72943167d04b16c9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / eval_hub_mcp-1.0.2-py3-none-macosx_11_0_arm64.whl
| Download URL | eval_hub_mcp-1.0.2-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 5.1 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
77e41c8d7d4a60144363511d58c8630b25460cfdca11c3c96db572616c67b4e7
|
|
BLAKE2b-256 checksum How to use checksums |
b9ff9f460243f9b15f4ad0e898d096d5091a00c774733255a68b7d87305d5d01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / eval_hub_mcp-1.0.2-py3-none-macosx_10_9_x86_64.whl
| Download URL | eval_hub_mcp-1.0.2-py3-none-macosx_10_9_x86_64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | Python 3 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
734431636c201fe78ca9d5c6ab540a085fb605f76b3ce97876e2c0a2a6d3177f
|
|
BLAKE2b-256 checksum How to use checksums |
d902d583bb3fbfc0828082bfb3c1bee604f12d3eb810e8dff9f81b9b4cee7ef4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logSecurity for eval-hub-mcp 1.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 5 files in this release have been uploaded with provenance metadata.
Attestation for eval_hub_mcp-1.0.2-py3-none-win_amd64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
