Skip to content
Stoic Sage logo

Stoic Sage MCP server

Which MCP servers are Stoic Sage's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to Stoic Sage

Whose server it is
  • Registry nameai.stoicsage/stoic-sageverified in the MCP registry

The registry name sits under stoicsage.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-29
  • Stateanswerschecked 2026-10-29
  • Tools3
  • Server calls itselfstoic-sage
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 230 ms.

Should an agent connect itConnect it
  • Its tools do every use case we checked: look up passages by keyword across classic Stoic texts; get a daily reflection tied to one passage.

Once connected

  • For "look up passages by keyword across classic Stoic texts", the likely first call is search_texts.
  • For "get a daily reflection tied to one passage", the likely first call is daily_reflection.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 7, the first on 2026-10-29
  • INITE MCP score100 of 100answers 100 · does the job 100 · definitions 100 · context 100 · connects 100
  • What an agent can do with it2 of 2 use cases
  • Answered100% of days7 of 7 daily checks
  • Median first answer146 ms
  • Space in an agent's context≈ 339 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results3 of 3 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · look up passages by keyword across classic Stoic texts
  • can do · get a daily reflection tied to one passage
  • not sure · ask for plain-language explanations of difficult passages

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-29
  • search_texts

    Semantic search across the Stoic corpus (Marcus Aurelius, Seneca, Epictetus). Returns ranked passages with source, book/chapter, entry, text, and score. Does not cover the thematic essays at /notes — those are HTML pages, not corpus…

  • get_entry

    Fetch one passage by source, book/chapter, and entry id. Use search_texts when you do not already know the citation.

  • daily_reflection

    Get today's date-seeded Stoic reflection and its AI commentary (if generated). The same passage is returned for every caller on a given UTC date.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "stoic-sage": {
      "type": "http",
      "url": "https://stoicsage.ai/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http stoicsage https://stoicsage.ai/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://stoicsage.ai/mcp as a custom connector in the settings.

OpenAPI spec

6 paths, read 2026-10-29. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.