Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.gregcastro23/planetary-agents

PYPI · ALCHM-PLANETARY-AGENTS-MCP · SCANNED OCT 3

Converse with planetary-agent personas, council feeds & culinary debates from alchm.kitchen

0 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 10 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 331 tokens (~82/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the io.github.gregcastro23/planetary-agents MCP server?

io.github.gregcastro23/planetary-agents runs locally as a PyPI package, launched with uvx alchm-planetary-agents-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · alchm-planetary-agents-mcp

# add to Claude Code
claude mcp add gregcastro23-planetary-agents -- uvx alchm-planetary-agents-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "gregcastro23-planetary-agents": {
      "command": "uvx",
      "args": [
        "alchm-planetary-agents-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "gregcastro23-planetary-agents": {
      "command": "uvx",
      "args": [
        "alchm-planetary-agents-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add gregcastro23-planetary-agents -- uvx alchm-planetary-agents-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gregcastro23-planetary-agents": {
      "type": "local",
      "command": [
        "uvx",
        "alchm-planetary-agents-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add gregcastro23-planetary-agents --command uvx --arg alchm-planetary-agents-mcp
# ~/.hermes/config.yaml
mcp_servers:
  gregcastro23-planetary-agents:
    command: "uvx"
    args: ["alchm-planetary-agents-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "gregcastro23-planetary-agents": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "alchm-planetary-agents-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add gregcastro23-planetary-agents -t stdio -c uvx -a alchm-planetary-agents-mcp
// mcp.json
{
  "mcpServers": {
    "gregcastro23-planetary-agents": {
      "command": "uvx",
      "args": [
        "alchm-planetary-agents-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Oct 26 −3
    • Stability: pass → 0.80 functional
  • 2 Oct 26 +1
    • Stability: 0.97 → pass security
  • 30 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Oct 2026 · Analysed pypi/alchm-planetary-agents-mcp@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 10 packages
Packages resolved 10
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~331 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
chat_with_planetary_agent ~113

Converse with a configured Planetary Agents persona through the FastAPI chat pipeline.

NameTypeReqDescription
agentNamestringyesAgent name or slug, e.g. Socrates, Rumi, Galileo, Jung, socrates.
contextobject–Optional structured context to pass through to /api/chat.
conversationHistoryarray–Optional recent turns to provide as lightweight context.
messagestringyesUser message for the agent.
modelTierstring–Optional backend model tier override.

No output schema declared.

No examples provided.

get_agent_feed_discussion ~41

Retrieve a council-feed event or thread by ID from the Planetary Agents frontend feed.

NameTypeReqDescription
threadIdstringyesFeed event or thread ID.

No output schema declared.

No examples provided.

synthesize_culinary_debate ~78

Ask multiple historical personas to debate ingredients using Alchm MCP ingredient and recipe data when available.

NameTypeReqDescription
agentsarray–Agent names or slugs. Defaults to Socrates, Rumi, and Galileo.
ingredientsarrayyesIngredients to debate.
modelTierstring–Optional backend model tier override.

No output schema declared.

No examples provided.

trigger_chart_specific_jing_duel ~99

Automatically detect birthchart synastry aspects between two agents and trigger an in-character Jing duel/clash.

NameTypeReqDescription
casterNamestringyesAgent initiating the clash, e.g. Socrates, Rumi, Galileo, Carl Jung.
modelTierstring–Optional backend model tier override.
targetNamestringyesAgent defending the clash, e.g. Socrates, Rumi, Galileo, Carl Jung.

No output schema declared.

No examples provided.

Common questions

What is the io.github.gregcastro23/planetary-agents MCP server?

io.github.gregcastro23/planetary-agents is an MCP server listed in the public MCP registry as io.github.gregcastro23/planetary-agents. Converse with planetary-agent personas, council feeds & culinary debates from alchm.kitchen. This page covers its PyPI package (alchm-planetary-agents-mcp).

Is the io.github.gregcastro23/planetary-agents MCP server safe to use?

io.github.gregcastro23/planetary-agents scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 3 October 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.gregcastro23/planetary-agents MCP server expose?

io.github.gregcastro23/planetary-agents exposes 4 tools: chat_with_planetary_agent, get_agent_feed_discussion, synthesize_culinary_debate, trigger_chart_specific_jing_duel. Their descriptions and schemas cost roughly 331 tokens of context every time the server is loaded.

Is the io.github.gregcastro23/planetary-agents MCP server still maintained?

io.github.gregcastro23/planetary-agents is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.gregcastro23/planetary-agents MCP server under?

io.github.gregcastro23/planetary-agents declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.