Skip to content
MCP server

Coarse moon age 0-29 from UTC day

Returns a coarse moon age from 0 to 29 for the current UTC day, over MCP

Install
Platforms
API
Runs
Remotely
Version
1.0.0
Listing updated
today

Similar MCP servers

About Coarse moon age 0-29 from UTC day

Coarse moon age 0-29 from UTC day is an MCP server for time utilities. It runs as a hosted remote server, so there is nothing to install locally.

Moon age is the number of days since the last new moon. This server reports a coarse version of it, bucketed into whole days from 0 to 29, and calculates it from the UTC date rather than a local time zone. It is exposed as a remote streamable-HTTP MCP endpoint, so clients can connect without installing a package.

The repository describes itself as a collection of small, independently listed MCP utilities, each with its own registry name. The README links this server alongside many similar single-purpose endpoints, several of which return only a yes/no or a band rather than a full value. The README does not describe a detailed method for the moon-age calculation or list its accuracy.

It suits developers who want a simple, deterministic time-related tool to test MCP client integrations, or who need a lightweight lunar-phase signal inside an agent workflow.

Install

Run in a terminal

claude mcp add --transport http moon-age https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/moon-age/mcp

Add to Settings → Connectors → Add custom connector

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/moon-age/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "moon-age": {
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/moon-age/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "moon-age": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/moon-age/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "moon-age": {
      "serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/moon-age/mcp"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "moon-age": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/moon-age/mcp"
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

What it does

Remote streamable HTTP endpoint
Connects over streamable HTTP at a hosted URL, with no local package install listed in the registry entry.
Coarse moon age value
Returns the moon age as a whole-day bucket between 0 and 29.
UTC day basis
The value is computed for the current UTC day, so results do not depend on the caller's time zone.
Registry-listed utility
Published under the official MCP registry name io.github.sadri-dridi/moon-age.

Good for

  • Adding a rough lunar-phase reading to an agent's date-aware workflow
  • Testing an MCP client's handling of a simple remote streamable-HTTP tool
  • Driving a playful astronomy or calendar feature with a daily moon-age value

Coarse moon age 0-29 from UTC day FAQ

How do I connect to this server?

The registry entry lists one remote endpoint using the streamable-http transport, and no packaged install is listed.

What time basis does it use?

The server name and description say the moon age is derived from the UTC day.

How do I add Coarse moon age 0-29 from UTC day to Claude Code?

Run this command in your terminal: claude mcp add --transport http moon-age https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/moon-age/mcp

What are the best alternatives to Coarse moon age 0-29 from UTC day?

The closest alternatives to Coarse moon age 0-29 from UTC day are Coarse moon phase from UTC day, Mean solar noon UTC-hour band, UTC second day of the current month, Days in the current UTC month and Days in current UTC month.

Where this comes from

  • Description: written from the project's README and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers