An MCP service for building queries against SDSS catalogs.
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":"cas-sdss-mcp","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.
# SSEC-JHU <package_name> [](https://github.com/ssec-jhu/base-template/actions/workflows/ci.yml) [](https://ssec-jhu-base-template.readthedocs.io/en/latest/?badge=latest) [](https://codecov.io/gh/ssec-jhu/base-template) [](https://github.com/ssec-jhu/base-template/actions/workflows/security.yml) [](https://doi.org/10.5281/zenodo.14052740)  Based on https://github.com/nicknochnack/BuildMCPServer Base repo template to be used by all others. Things to do when using this template: * Run ```python project_setup.py``` * Uncomment above DOI in README.md and correct ``<insert_ID_number>``. * Correct "description" field in .zenodo.json to reflect description of child repo. * Correct the ``CI Status`` badge with the correct token in the URL. * Import package into https://readthedocs.org/. * Update [zenodo.json](zenodo.json). For more details see [zenodo.json docs](https://developers.zenodo.org/#representation) and [zenodo docs on contributors vs creators](https://help.zenodo.org/docs/deposit/describe-records/contributors/). * Update quickstart guide below. What's included in this template: * Licence file * Code of Conduct * Build & Setup, inc. ``pip`` dependency requirements. * Dependabot GitHub action * CI for GitHub actions: lint, pytest, build & publish docker image to GitHub Packages. * Dockerfile. * Pytest example(s). * Githooks. # Quickstart Guide Add here, streamlined instructions on how to get the code running as swiftly as possible, and provi…
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.