Store

com.thenightskyPublished by thenightsky.comOfficial publisherv0.1.0Updated Oct 24, 2026

Design custom star maps and engraved jewellery in chat; checkout finishes on thenightsky.com.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant design custom star maps and engraved jewellery in chat, with checkout completed on thenightsky.com.

What you can do
This remote server supports designing custom star maps and engraved jewellery through a conversation with the assistant. The design work happens in chat, but the purchase is not finished there: checkout is completed on thenightsky.com. No individual tools are listed in the available information.
When to use it
Worth adding when someone wants to create a personalised star map or engraved jewellery piece and would like help shaping the design conversationally before buying.
Requirements
A remote MCP endpoint reached over streamable HTTP at mcp.thenightsky.com. OAuth authentication is required. No environment variables or headers are declared.
Before you install
The server requires OAuth sign-in, so it will have access to an account. Checkout and payment happen on thenightsky.com, so any purchase is a real transaction outside the chat. Review the design and price on the site before paying.

Installation

In SourceWeft

  1. Open Store in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.thenightsky%2Fstore/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "store": {
      "type": "http",
      "url": "https://mcp.thenightsky.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.