A sample MCP server exposing a current-time hexagram lookup tool.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"hexagram-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# hexagram-mcp-server A minimal, production-friendly sample MCP server project with PyPI publishing support. ## Features - Minimal MCP server implementation - Tool + Resource examples - Modern Python packaging with `pyproject.toml` - Console entry point (`hexagram-mcp-server`) - Build and publish workflow for PyPI ## Quick Start 1. Create and activate a virtual environment. 2. Install dependencies: ```bash pip install -e .[dev] ``` 3. Run the server: ```bash hexagram-mcp-server ``` ## Example MCP API - Tool: `get_hexagram() -> str` ## Build Package ```bash python -m build ``` After building, artifacts are generated in the `dist/` directory. ## Publish to PyPI 1. Create a PyPI API token from your PyPI account. 2. Configure your token (recommended): ```bash set PYPI_TOKEN=pypi-xxxxxxxxxxxxxxxx ``` 3. Upload: ```bash python -m twine upload -u __token__ -p %PYPI_TOKEN% dist/* ``` For TestPyPI, use: ```bash python -m twine upload --repository-url https://test.pypi.org/legacy/ -u __token__ -p %PYPI_TOKEN% dist/* ``` ## Publish with GitHub Actions This template includes `.github/workflows/publish.yml` and supports PyPI Trusted Publishing. 1. Create your package on PyPI first. 2. In PyPI project settings, configure a Trusted Publisher for your GitHub repository. 3. Create a GitHub Release (`published`), then workflow will build and publish automatically. If you prefer token-based upload in CI, you can replace the publish step with `twine upload` and store token in GitHub Secrets. ## Notes Before Publishing - Update `name`, `authors`, and project URLs in `pyproject.toml`. - Ensure version is bumped before each release. - Verify package contents: ```bash python -m twine check dist/* ``` ## License MIT
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.