@cosmosos/mcp-ephemeris 0.2.1 → 0.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/LICENSE +216 -91
  2. package/README.md +115 -115
  3. package/package.json +3 -2
package/LICENSE CHANGED
@@ -1,91 +1,216 @@
1
- # License @cosmosos/mcp-ephemeris
2
-
3
- Required Notice: Copyright 2026 KAIROSAST LTD (https://llmastro.com)
4
-
5
- ------------------------------------------------------------------------
6
- This software is **free for noncommercial use** (personal, research,
7
- education, non-profit organizations) under the PolyForm Noncommercial
8
- License 1.0.0, reproduced below.
9
-
10
- **Commercial / professional use requires a separate, paid license.**
11
- To obtain one, contact KAIROSAST LTD via https://llmastro.com/contact.
12
-
13
- Note: the optional `swisseph` dependency (Swiss Ephemeris, by Astrodienst)
14
- is licensed separately (AGPL or a commercial Swiss Ephemeris license) and
15
- is NOT covered by this license. Commercial users must comply with
16
- Astrodienst's terms independently.
17
- ------------------------------------------------------------------------
18
-
19
- # PolyForm Noncommercial License 1.0.0
20
-
21
- <https://polyformproject.org/licenses/noncommercial/1.0.0>
22
-
23
- ## Acceptance
24
-
25
- In order to get any license under these terms, you must agree to them as both strict obligations and conditions to all your licenses.
26
-
27
- ## Copyright License
28
-
29
- The licensor grants you a copyright license for the software to do everything you might do with the software that would otherwise infringe the licensor's copyright in it for any permitted purpose. However, you may only distribute the software according to [Distribution License](#distribution-license) and make changes or new works based on the software according to [Changes and New Works License](#changes-and-new-works-license).
30
-
31
- ## Distribution License
32
-
33
- The licensor grants you an additional copyright license to distribute copies of the software. Your license to distribute covers distributing the software with changes and new works permitted by [Changes and New Works License](#changes-and-new-works-license).
34
-
35
- ## Notices
36
-
37
- You must ensure that anyone who gets a copy of any part of the software from you also gets a copy of these terms or the URL for them above, as well as copies of any plain-text lines beginning with `Required Notice:` that the licensor provided with the software. For example:
38
-
39
- > Required Notice: Copyright Yoyodyne, Inc. (http://example.com)
40
-
41
- ## Changes and New Works License
42
-
43
- The licensor grants you an additional copyright license to make changes and new works based on the software for any permitted purpose.
44
-
45
- ## Patent License
46
-
47
- The licensor grants you a patent license for the software that covers patent claims the licensor can license, or becomes able to license, that you would infringe by using the software.
48
-
49
- ## Noncommercial Purposes
50
-
51
- Any noncommercial purpose is a permitted purpose.
52
-
53
- ## Personal Uses
54
-
55
- Personal use for research, experiment, and testing for the benefit of public knowledge, personal study, private entertainment, hobby projects, amateur pursuits, or religious observance, without any anticipated commercial application, is use for a permitted purpose.
56
-
57
- ## Noncommercial Organizations
58
-
59
- Use by any charitable organization, educational institution, public research organization, public safety or health organization, environmental protection organization, or government institution is use for a permitted purpose regardless of the source of funding or obligations resulting from the funding.
60
-
61
- ## Fair Use
62
-
63
- You may have "fair use" rights for the software under the law. These terms do not limit them.
64
-
65
- ## No Other Rights
66
-
67
- These terms do not allow you to sublicense or transfer any of your licenses to anyone else, or prevent the licensor from granting licenses to anyone else. These terms do not imply any other licenses.
68
-
69
- ## Patent Defense
70
-
71
- If you make any written claim that the software infringes or contributes to infringement of any patent, your patent license for the software granted under these terms ends immediately. If your company makes such a claim, your patent license ends immediately for work on behalf of your company.
72
-
73
- ## Violations
74
-
75
- The first time you are notified in writing that you have violated any of these terms, or done anything with the software not covered by your licenses, your licenses can nonetheless continue if you come into full compliance with these terms, and take practical steps to correct past violations, within 32 days of receiving notice. Otherwise, all your licenses end immediately.
76
-
77
- ## No Liability
78
-
79
- ***As far as the law allows, the software comes as is, without any warranty or condition, and the licensor will not be liable to you for any damages arising out of these terms or the use or nature of the software, under any kind of legal claim.***
80
-
81
- ## Definitions
82
-
83
- The **licensor** is the individual or entity offering these terms, and the **software** is the software the licensor makes available under these terms.
84
-
85
- **You** refers to the individual or entity agreeing to these terms.
86
-
87
- **Your company** is any legal entity, sole proprietorship, or other kind of organization that you work for, plus all organizations that have control over, are under the control of, or are under common control with that organization. **Control** means ownership of substantially all the assets of an entity, or the power to direct its management and policies by vote, contract, or otherwise. Control can be direct or indirect.
88
-
89
- **Your licenses** are all the licenses granted to you for the software under these terms.
90
-
91
- **Use** means anything you do with the software requiring one of your licenses.
1
+ The MCP project is undergoing a licensing transition from the MIT License to the Apache License, Version 2.0 ("Apache-2.0"). All new code and specification contributions to the project are licensed under Apache-2.0. Documentation contributions (excluding specifications) are licensed under CC-BY-4.0.
2
+
3
+ Contributions for which relicensing consent has been obtained are licensed under Apache-2.0. Contributions made by authors who originally licensed their work under the MIT License and who have not yet granted explicit permission to relicense remain licensed under the MIT License.
4
+
5
+ No rights beyond those granted by the applicable original license are conveyed for such contributions.
6
+
7
+ ---
8
+
9
+ Apache License
10
+ Version 2.0, January 2004
11
+ http://www.apache.org/licenses/
12
+
13
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
14
+
15
+ 1. Definitions.
16
+
17
+ "License" shall mean the terms and conditions for use, reproduction,
18
+ and distribution as defined by Sections 1 through 9 of this document.
19
+
20
+ "Licensor" shall mean the copyright owner or entity authorized by
21
+ the copyright owner that is granting the License.
22
+
23
+ "Legal Entity" shall mean the union of the acting entity and all
24
+ other entities that control, are controlled by, or are under common
25
+ control with that entity. For the purposes of this definition,
26
+ "control" means (i) the power, direct or indirect, to cause the
27
+ direction or management of such entity, whether by contract or
28
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
29
+ outstanding shares, or (iii) beneficial ownership of such entity.
30
+
31
+ "You" (or "Your") shall mean an individual or Legal Entity
32
+ exercising permissions granted by this License.
33
+
34
+ "Source" form shall mean the preferred form for making modifications,
35
+ including but not limited to software source code, documentation
36
+ source, and configuration files.
37
+
38
+ "Object" form shall mean any form resulting from mechanical
39
+ transformation or translation of a Source form, including but
40
+ not limited to compiled object code, generated documentation,
41
+ and conversions to other media types.
42
+
43
+ "Work" shall mean the work of authorship, whether in Source or
44
+ Object form, made available under the License, as indicated by a
45
+ copyright notice that is included in or attached to the work
46
+ (an example is provided in the Appendix below).
47
+
48
+ "Derivative Works" shall mean any work, whether in Source or Object
49
+ form, that is based on (or derived from) the Work and for which the
50
+ editorial revisions, annotations, elaborations, or other modifications
51
+ represent, as a whole, an original work of authorship. For the purposes
52
+ of this License, Derivative Works shall not include works that remain
53
+ separable from, or merely link (or bind by name) to the interfaces of,
54
+ the Work and Derivative Works thereof.
55
+
56
+ "Contribution" shall mean any work of authorship, including
57
+ the original version of the Work and any modifications or additions
58
+ to that Work or Derivative Works thereof, that is intentionally
59
+ submitted to the Licensor for inclusion in the Work by the copyright
60
+ owner or by an individual or Legal Entity authorized to submit on behalf
61
+ of the copyright owner. For the purposes of this definition, "submitted"
62
+ means any form of electronic, verbal, or written communication sent
63
+ to the Licensor or its representatives, including but not limited to
64
+ communication on electronic mailing lists, source code control systems,
65
+ and issue tracking systems that are managed by, or on behalf of, the
66
+ Licensor for the purpose of discussing and improving the Work, but
67
+ excluding communication that is conspicuously marked or otherwise
68
+ designated in writing by the copyright owner as "Not a Contribution."
69
+
70
+ "Contributor" shall mean Licensor and any individual or Legal Entity
71
+ on behalf of whom a Contribution has been received by Licensor and
72
+ subsequently incorporated within the Work.
73
+
74
+ 2. Grant of Copyright License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ copyright license to reproduce, prepare Derivative Works of,
78
+ publicly display, publicly perform, sublicense, and distribute the
79
+ Work and such Derivative Works in Source or Object form.
80
+
81
+ 3. Grant of Patent License. Subject to the terms and conditions of
82
+ this License, each Contributor hereby grants to You a perpetual,
83
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
84
+ (except as stated in this section) patent license to make, have made,
85
+ use, offer to sell, sell, import, and otherwise transfer the Work,
86
+ where such license applies only to those patent claims licensable
87
+ by such Contributor that are necessarily infringed by their
88
+ Contribution(s) alone or by combination of their Contribution(s)
89
+ with the Work to which such Contribution(s) was submitted. If You
90
+ institute patent litigation against any entity (including a
91
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
92
+ or a Contribution incorporated within the Work constitutes direct
93
+ or contributory patent infringement, then any patent licenses
94
+ granted to You under this License for that Work shall terminate
95
+ as of the date such litigation is filed.
96
+
97
+ 4. Redistribution. You may reproduce and distribute copies of the
98
+ Work or Derivative Works thereof in any medium, with or without
99
+ modifications, and in Source or Object form, provided that You
100
+ meet the following conditions:
101
+
102
+ (a) You must give any other recipients of the Work or
103
+ Derivative Works a copy of this License; and
104
+
105
+ (b) You must cause any modified files to carry prominent notices
106
+ stating that You changed the files; and
107
+
108
+ (c) You must retain, in the Source form of any Derivative Works
109
+ that You distribute, all copyright, patent, trademark, and
110
+ attribution notices from the Source form of the Work,
111
+ excluding those notices that do not pertain to any part of
112
+ the Derivative Works; and
113
+
114
+ (d) If the Work includes a "NOTICE" text file as part of its
115
+ distribution, then any Derivative Works that You distribute must
116
+ include a readable copy of the attribution notices contained
117
+ within such NOTICE file, excluding those notices that do not
118
+ pertain to any part of the Derivative Works, in at least one
119
+ of the following places: within a NOTICE text file distributed
120
+ as part of the Derivative Works; within the Source form or
121
+ documentation, if provided along with the Derivative Works; or,
122
+ within a display generated by the Derivative Works, if and
123
+ wherever such third-party notices normally appear. The contents
124
+ of the NOTICE file are for informational purposes only and
125
+ do not modify the License. You may add Your own attribution
126
+ notices within Derivative Works that You distribute, alongside
127
+ or as an addendum to the NOTICE text from the Work, provided
128
+ that such additional attribution notices cannot be construed
129
+ as modifying the License.
130
+
131
+ You may add Your own copyright statement to Your modifications and
132
+ may provide additional or different license terms and conditions
133
+ for use, reproduction, or distribution of Your modifications, or
134
+ for any such Derivative Works as a whole, provided Your use,
135
+ reproduction, and distribution of the Work otherwise complies with
136
+ the conditions stated in this License.
137
+
138
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
139
+ any Contribution intentionally submitted for inclusion in the Work
140
+ by You to the Licensor shall be under the terms and conditions of
141
+ this License, without any additional terms or conditions.
142
+ Notwithstanding the above, nothing herein shall supersede or modify
143
+ the terms of any separate license agreement you may have executed
144
+ with Licensor regarding such Contributions.
145
+
146
+ 6. Trademarks. This License does not grant permission to use the trade
147
+ names, trademarks, service marks, or product names of the Licensor,
148
+ except as required for reasonable and customary use in describing the
149
+ origin of the Work and reproducing the content of the NOTICE file.
150
+
151
+ 7. Disclaimer of Warranty. Unless required by applicable law or
152
+ agreed to in writing, Licensor provides the Work (and each
153
+ Contributor provides its Contributions) on an "AS IS" BASIS,
154
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
155
+ implied, including, without limitation, any warranties or conditions
156
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
157
+ PARTICULAR PURPOSE. You are solely responsible for determining the
158
+ appropriateness of using or redistributing the Work and assume any
159
+ risks associated with Your exercise of permissions under this License.
160
+
161
+ 8. Limitation of Liability. In no event and under no legal theory,
162
+ whether in tort (including negligence), contract, or otherwise,
163
+ unless required by applicable law (such as deliberate and grossly
164
+ negligent acts) or agreed to in writing, shall any Contributor be
165
+ liable to You for damages, including any direct, indirect, special,
166
+ incidental, or consequential damages of any character arising as a
167
+ result of this License or out of the use or inability to use the
168
+ Work (including but not limited to damages for loss of goodwill,
169
+ work stoppage, computer failure or malfunction, or any and all
170
+ other commercial damages or losses), even if such Contributor
171
+ has been advised of the possibility of such damages.
172
+
173
+ 9. Accepting Warranty or Additional Liability. While redistributing
174
+ the Work or Derivative Works thereof, You may choose to offer,
175
+ and charge a fee for, acceptance of support, warranty, indemnity,
176
+ or other liability obligations and/or rights consistent with this
177
+ License. However, in accepting such obligations, You may act only
178
+ on Your own behalf and on Your sole responsibility, not on behalf
179
+ of any other Contributor, and only if You agree to indemnify,
180
+ defend, and hold each Contributor harmless for any liability
181
+ incurred by, or claims asserted against, such Contributor by reason
182
+ of your accepting any such warranty or additional liability.
183
+
184
+ END OF TERMS AND CONDITIONS
185
+
186
+ ---
187
+
188
+ MIT License
189
+
190
+ Copyright (c) 2024-2025 Model Context Protocol a Series of LF Projects, LLC.
191
+
192
+ Permission is hereby granted, free of charge, to any person obtaining a copy
193
+ of this software and associated documentation files (the "Software"), to deal
194
+ in the Software without restriction, including without limitation the rights
195
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
196
+ copies of the Software, and to permit persons to whom the Software is
197
+ furnished to do so, subject to the following conditions:
198
+
199
+ The above copyright notice and this permission notice shall be included in all
200
+ copies or substantial portions of the Software.
201
+
202
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
203
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
204
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
205
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
206
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
207
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
208
+ SOFTWARE.
209
+
210
+ ---
211
+
212
+ Creative Commons Attribution 4.0 International (CC-BY-4.0)
213
+
214
+ Documentation in this project (excluding specifications) is licensed under
215
+ CC-BY-4.0. See https://creativecommons.org/licenses/by/4.0/legalcode for
216
+ the full license text.
package/README.md CHANGED
@@ -1,153 +1,153 @@
1
- # @cosmosos/mcp-ephemeris
1
+ # MCP Registry
2
2
 
3
- **The real sky, for your AI.** An [MCP](https://modelcontextprotocol.io) server
4
- that gives any assistant (Claude, Cursor, agents) **computed planetary
5
- positions** — never guessed — powered by the
6
- [Swiss Ephemeris](https://www.astro.com/swisseph/) engine, and **validated
7
- against JPL Horizons (NASA)** to under one arcsecond.
3
+ The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
8
4
 
9
- > **Cardinal rule: the LLM never computes.** This server is a facade over an
10
- > ephemeris engine. The model interprets; the sky is a fact.
5
+ [**📤 Publish my MCP server**](docs/modelcontextprotocol-io/quickstart.mdx) | [**⚡️ Live API docs**](https://registry.modelcontextprotocol.io/docs) | [**👀 Ecosystem vision**](docs/design/ecosystem-vision.md) | 📖 **[Full documentation](./docs)**
11
6
 
12
- *(Version française : <https://llmastro.com/notre-moteur>)*
7
+ ## Development Status
13
8
 
14
- ## Quick start (Claude Desktop)
9
+ **2025-10-24 update**: The Registry API has entered an **API freeze (v0.1)** 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!
15
10
 
16
- Open **Settings Developer Edit Config**, then add:
11
+ **2025-09-08 update**: The registry has launched in preview 🎉 ([announcement blog post](https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview/)). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in [GitHub discussions](https://github.com/modelcontextprotocol/registry/discussions/new?category=ideas) or in the [#registry-dev Discord](https://discord.com/channels/1358869848138059966/1369487942862504016) ([joining details here](https://modelcontextprotocol.io/community/communication)).
17
12
 
18
- ```json
19
- {
20
- "mcpServers": {
21
- "llmastro": {
22
- "command": "npx",
23
- "args": ["-y", "@cosmosos/mcp-ephemeris"]
24
- }
25
- }
26
- }
27
- ```
13
+ Registry Working Group:
14
+ - **Tadas Antanavicius** (PulseMCP) [@tadasant](https://github.com/tadasant)
15
+ - **Radoslav (Rado) Dimitrov** (Stacklok) [@rdimitrov](https://github.com/rdimitrov)
16
+ - **Bob Dickinson** (TeamSpark) [@BobDickinson](https://github.com/BobDickinson)
17
+ - **Preeti (Pree) Dewani** (Ravenmail) [@pree-dew](https://github.com/pree-dew)
28
18
 
29
- Fully quit Claude Desktop (system tray) and relaunch it. Then ask:
30
- *"What's the moon phase today?"* — Claude calls the server and answers from
31
- genuinely computed positions.
19
+ ## Contributing
32
20
 
33
- **Cursor / Windsurf / others**: add the same `llmastro` entry
34
- (`command: npx`, `args: ["-y", "@cosmosos/mcp-ephemeris"]`) to your client's MCP
35
- configuration.
21
+ We use multiple channels for collaboration - see [modelcontextprotocol.io/community/communication](https://modelcontextprotocol.io/community/communication).
36
22
 
37
- ## Tools exposed
23
+ Often (but not always) ideas flow through this pipeline:
38
24
 
39
- **19 tools**, all backed by the same server-side computed engine.
25
+ - **[Discord](https://modelcontextprotocol.io/community/communication)** - Real-time community discussions
26
+ - **[Discussions](https://github.com/modelcontextprotocol/registry/discussions)** - Propose and discuss product/technical requirements
27
+ - **[Issues](https://github.com/modelcontextprotocol/registry/issues)** - Track well-scoped technical work
28
+ - **[Pull Requests](https://github.com/modelcontextprotocol/registry/pulls)** - Contribute work towards issues
40
29
 
41
- ### Positions & sky
42
- | Tool | Input | Output |
43
- |---|---|---|
44
- | `get_planet_positions` | `datetime` (ISO UTC) | ecliptic positions of all bodies (sign, degree, retro) |
45
- | `get_moon_phase` | `datetime` (ISO UTC) | moon phase, illumination %, description |
46
- | `get_current_sky` | `latitude`, `longitude` | the sky right now (current transits) for a place |
47
- | `get_aspects` | `datetime` (ISO UTC) | grid of major + minor aspects between bodies |
30
+ ### Quick start:
48
31
 
49
- ### Natal chart & relationships
50
- | Tool | Input | Output |
51
- |---|---|---|
52
- | `get_natal_chart` | birth + `zodiac` (tropical/sidereal), `houseSystem` (7 systems) | full chart: houses, aspects, ASC/MC, moon phase, Hermetic Lots |
53
- | `get_transits` | birth + optional `datetime` | transit→natal aspects, sorted by orb |
54
- | `get_synastry` | two births | inter-chart aspects + harmony/tension summary |
55
- | `get_composite_chart` | two births | midpoint composite chart |
56
- | `get_secondary_progressions` | birth + `targetDate` | progressed positions ("a day for a year") |
57
- | `get_solar_return` | birth + `year` (+ optional place) | instant + chart of the solar return |
58
- | `get_lunar_return` | birth + optional `after` | instant + chart of the next lunar return |
32
+ #### Pre-requisites
59
33
 
60
- ### Celestial events
61
- | Tool | Input | Output |
62
- |---|---|---|
63
- | `get_ingresses` | `body`, `start`, `end` | sign-change dates (retrograde-robust) |
64
- | `get_retrograde_windows` | `body`, `start`, `end` | retrograde/direct stations over the range |
65
- | `get_eclipse_details` | `datetime`, `kind` | magnitude, obscuration, Saros of a known eclipse *(swisseph)* |
66
- | `get_next_eclipse` | `from`, `kind`, optional `backward` | next/previous eclipse: maximum, type, contacts *(swisseph)* |
34
+ - **Docker**
35
+ - **Go 1.24.x**
36
+ - **ko** - Container image builder for Go ([installation instructions](https://ko.build/install/))
37
+ - **golangci-lint v2.4.0**
67
38
 
68
- ### Astrocartography, numerology, authority
69
- | Tool | Input | Output |
70
- |---|---|---|
71
- | `get_astrocartography` | `datetime` (ISO UTC) | planetary MC/IC lines + parans (crossings) |
72
- | `get_life_path` | `date` (YYYY-MM-DD) | life-path number (numerology) |
73
- | `get_engine_diagnostic` | — | active engine, native addon load status, real precision |
74
- | `validate_against_horizons` | `datetime`, optional `bodies` | delta of our positions vs JPL Horizons (NASA) in arcseconds — network required |
39
+ #### Running the server
75
40
 
76
- *(swisseph)* = requires the native Swiss Ephemeris addon; returns `null` on the AstraCore fallback.
41
+ ```bash
42
+ # Start full development environment
43
+ make dev-compose
44
+ ```
77
45
 
78
- ## Precision
46
+ This starts the registry at [`localhost:8080`](http://localhost:8080) with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.
79
47
 
80
- Under [Swiss Ephemeris](https://www.astro.com/swisseph/), positions match the
81
- world reference **JPL Horizons (NASA)** to under one arcsecond (measured
82
- 2026-07-19):
48
+ **Note:** The registry uses [ko](https://ko.build) to build container images. The `make dev-compose` command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.
83
49
 
84
- | Body | Difference vs NASA |
85
- |---|---|
86
- | Sun | 0.2″ |
87
- | Moon | 1.5″ |
88
- | Jupiter | 0.1″ |
89
- | Pluto | 0.4″ |
50
+ By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with `MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose`.
90
51
 
91
- Check it yourself with the `validate_against_horizons` tool.
52
+ The setup can be configured with environment variables in [docker-compose.yml](./docker-compose.yml) - see [.env.example](./.env.example) for a reference.
92
53
 
93
- ## Two engines
54
+ <details>
55
+ <summary>Alternative: Running a pre-built Docker image</summary>
94
56
 
95
- Computation is routed by the `ASTRO_ENGINE` variable:
57
+ Pre-built Docker images are automatically published to GitHub Container Registry. Note that the image does not bundle PostgreSQL, so you need to run your own and point the registry at it via `MCP_REGISTRY_DATABASE_URL` (see [docker-compose.yml](./docker-compose.yml) for a working example):
96
58
 
97
- - **`swisseph`** (default) — Swiss Ephemeris, native addon, sub-arcsecond
98
- precision. Compiles automatically wherever a C++ build chain is present
99
- (Linux, macOS, most servers).
100
- - **`astracore`** — in-house pure-TypeScript engine (VSOP/Meeus), **no native
101
- binary**. Used as an automatic fallback when `swisseph` couldn't be compiled
102
- (common on Windows). Sun and Moon stay accurate; outer planets drift by a few
103
- arcminutes.
59
+ ```bash
60
+ # Run latest stable release
61
+ docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest
104
62
 
105
- To force an engine: `ASTRO_ENGINE=swisseph` or `ASTRO_ENGINE=astracore`.
63
+ # Run latest from main branch (continuous deployment)
64
+ docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main
106
65
 
107
- ## Privacy
66
+ # Run specific release version
67
+ docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0
108
68
 
109
- The server runs **on your machine**: your birth data is sent nowhere. Only
110
- `validate_against_horizons` makes an outbound request (to NASA's public API).
69
+ # Run development build from main branch
70
+ docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d
71
+ ```
111
72
 
112
- ## Requirements
73
+ **Available tags:**
74
+ - **Releases**: `latest`, `v1.0.0`, `v1.1.0`, etc.
75
+ - **Continuous**: `main` (latest main branch build)
76
+ - **Development**: `main-<date>-<sha>` (specific commit builds)
113
77
 
114
- - Node.js ≥ 20.
115
- - For maximum precision (`swisseph`): a C++ build chain (`python3`, `make`, a
116
- compiler) on the machine. Otherwise, automatic fallback to `astracore`, with
117
- no configuration.
78
+ </details>
118
79
 
119
- ## About
80
+ #### Publishing a server
120
81
 
121
- Powered by the astrology engine of [Llmastro](https://llmastro.com). Learn more
122
- about the precision and architecture: <https://llmastro.com/notre-moteur>.
82
+ To publish a server, we've built a simple CLI. You can use it with:
123
83
 
124
- ## License
84
+ ```bash
85
+ # Build the latest CLI
86
+ make publisher
125
87
 
126
- **Free for non-commercial use** (personal, research, education, non-profit
127
- organizations) — under the
128
- [PolyForm Noncommercial 1.0.0](./LICENSE) license.
88
+ # Use it!
89
+ ./bin/mcp-publisher --help
90
+ ```
129
91
 
130
- **Commercial / professional use: a paid license is required.** To obtain one,
131
- contact KAIROSAST LTD via <https://llmastro.com/contact>.
92
+ See [the publisher guide](./docs/modelcontextprotocol-io/quickstart.mdx) for more details.
132
93
 
133
- Note: the optional `swisseph` dependency (Swiss Ephemeris, Astrodienst) has its
134
- own license (AGPL or a commercial Swiss Ephemeris license) and is not covered by
135
- this one. Professional use must comply with it separately.
94
+ #### Other commands
136
95
 
137
- ## Development
96
+ ```bash
97
+ # Run lint, unit tests and integration tests
98
+ make check
99
+ ```
138
100
 
139
- This repository is **self-contained**: the ephemeris engine is vendored in
140
- `vendor/ephemeris/` (source), and the build inlines it into `dist/` via
141
- [`tsup`](https://tsup.egoist.dev/).
101
+ There are also a few more helpful commands for development. Run `make help` to learn more, or look in [Makefile](./Makefile).
102
+
103
+ <!--
104
+ For Claude and other AI tools: Always prefer make targets over custom commands where possible.
105
+ -->
106
+
107
+ ## Architecture
108
+
109
+ ### Project Structure
142
110
 
143
- ```bash
144
- pnpm install # or npm install
145
- pnpm build # bundles dist/index.js (engine inlined)
146
- pnpm start # runs the MCP server (stdio) locally
147
111
  ```
112
+ ├── cmd/ # Application entry points
113
+ │ └── publisher/ # Server publishing tool
114
+ ├── data/ # Seed data
115
+ ├── deploy/ # Deployment configuration (Pulumi)
116
+ ├── docs/ # Documentation
117
+ ├── internal/ # Private application code
118
+ │ ├── api/ # HTTP handlers and routing
119
+ │ ├── auth/ # Authentication (GitHub OAuth, JWT, namespace blocking)
120
+ │ ├── config/ # Configuration management
121
+ │ ├── database/ # Data persistence (PostgreSQL)
122
+ │ ├── service/ # Business logic
123
+ │ ├── telemetry/ # Metrics and monitoring
124
+ │ └── validators/ # Input validation
125
+ ├── pkg/ # Public packages
126
+ │ ├── api/ # API types and structures
127
+ │ │ └── v0/ # Version 0 API types
128
+ │ └── model/ # Data models for server.json
129
+ ├── scripts/ # Development and testing scripts
130
+ ├── tests/ # Integration tests
131
+ └── tools/ # CLI tools and utilities
132
+ └── validate-*.sh # Schema validation tools
133
+ ```
134
+
135
+ ### Authentication
136
+
137
+ Publishing supports multiple authentication methods:
138
+ - **GitHub OAuth** - For publishing by logging into GitHub
139
+ - **GitHub OIDC** - For publishing from GitHub Actions
140
+ - **DNS verification** - For proving ownership of a domain and its subdomains
141
+ - **HTTP verification** - For proving ownership of a domain
142
+
143
+ The registry validates namespace ownership when publishing. E.g. to publish...:
144
+ - `io.github.domdomegg/my-cool-mcp` you must login to GitHub as `domdomegg`, or be in a GitHub Action on domdomegg's repos
145
+ - `me.adamjones/my-cool-mcp` you must prove ownership of `adamjones.me` via DNS or HTTP challenge
146
+
147
+ ## Community Projects
148
+
149
+ Check out [community projects](docs/community-projects.md) to explore notable registry-related work created by the community.
150
+
151
+ ## More documentation
148
152
 
149
- - Default engine: `swisseph` (sub-arcsecond precision) if the native addon
150
- compiles, otherwise automatic fallback to `astracore` (pure TypeScript, no
151
- binary). Force via `ASTRO_ENGINE=swisseph|astracore`.
152
- - The vendored engine is a snapshot of `@astro-platform/ephemeris` (Llmastro),
153
- re-synced manually.
153
+ See the [documentation](./docs) for more details if your question has not been answered here!
package/package.json CHANGED
@@ -1,8 +1,9 @@
1
1
  {
2
2
  "name": "@cosmosos/mcp-ephemeris",
3
- "version": "0.2.1",
3
+ "version": "0.2.2",
4
+ "mcpName": "io.github.kairosastro-sketch/mcp-ephemeris",
4
5
  "type": "module",
5
- "description": "Serveur MCP exposant des positions planétaires calculées côté serveur (Swiss Ephemeris) validées contre JPL Horizons (NASA). Branchez n'importe quel LLM/agent au vrai ciel.",
6
+ "description": "MCP server exposing server-computed planetary positions (Swiss Ephemeris), validated against JPL Horizons (NASA). Plug any LLM/agent into the real sky — 19 astrology tools, never hallucinated.",
6
7
  "keywords": [
7
8
  "mcp",
8
9
  "model-context-protocol",