MCP server for controlling SeestarS50 telescope
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":"seestar-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.
# SeestarS50 MCP Server [](https://github.com/taco-ops/seestar-mcp/actions/workflows/ci-cd.yml) [](https://www.python.org/downloads/) [](https://pypi.org/project/fastmcp/) [](https://github.com/taco-ops/seestar-mcp/pkgs/container/seestar-mcp) [](https://opensource.org/licenses/MIT) [](https://github.com/psf/black) [](https://codecov.io/gh/taco-ops/seestar-mcp) [](https://github.com/taco-ops/seestar-mcp/releases) [](https://github.com/taco-ops/seestar-mcp/releases) [](CHANGELOG.md) > 🚧 **PUBLIC BETA**: This project is in active development and public beta testing. While all tests pass and core functionality works, we're still gathering user feedback and making improvements. Use with caution in production environments. Please report any issues on GitHub! A Model Context Protocol (MCP) server for controlling SeestarS50 telescopes using Python FastMCP and complete UDP+TCP protocol implementation. Designed for both developers and astrophotographers who want to control their telescope through natural language interfaces like Claude Desktop, Warp Terminal, or other MCP-compatible clients. **⚠️ Beta Notice**: This software is currently in public beta. While extensively tested and functionally complete, we'r…
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.