Daily Horoscope

live.alpic.daily-horoscope-mcp-66c71311Published by daily-horoscope-mcp-66c71311.alpic.liveOfficial publisherv0.0.3Updated Oct 24, 2026

Daily horoscope readings providing valuable insights, crafted from consulting the cosmic energies.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote MCP server that gives an assistant daily horoscope readings drawn from astrological "cosmic energies".

What you can do
  • Provides daily horoscope readings for the assistant to look up and share.
  • Frames the readings as insights derived from consulting cosmic energies.
  • No tool list is published, so the exact operations are not documented.
When to use it
Add it when you want an assistant to fetch and present daily horoscope content, for example in a lifestyle or entertainment chat.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. An API key is required and must be sent in the x-api-key header.
Before you install
You must supply an API key in the x-api-key header, so treat it as a secret. Readings are entertainment content, not advice. No tool list or documentation is published, so what the server does with requests is unclear.

Installation

In SourceWeft

  1. Open Daily Horoscope in the dashboard and add it to a workspace.
  2. Connect x-api-key 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/live.alpic.daily-horoscope-mcp-66c71311%2FDaily-Horoscope/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.

{
  "mcpServers": {
    "daily-horoscope": {
      "type": "http",
      "url": "https://daily-horoscope-mcp-66c71311.alpic.live/",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v0.0.3LatestOct 19, 2026
  2. v0.0.1Sep 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 listedRequired15 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.