Oh My Posh MCP server
Featured official server
2 tools · Last check that passed 4 Nov 2026, 12:15 UTC
Oh My Posh's own remote MCP server gives an agent two tools that check an Oh My Posh prompt configuration, or one segment of it, against the project's official schema, in JSON, YAML or TOML, with no sign-in. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 2 tools
| Tool | Counted as |
|---|---|
validate_config | Said to only read |
validate_segment | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
21 of the last 21 checks passed
A check passes when the server lists its tools. Checked at https://ohmyposh.dev/api/mcp.
Recent changes
No change seen across the last 21 checks that passed.
From the scan of 4 Nov 2026, 12:43 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Oh My Posh's tools change.
One email when Oh My Posh's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- The whole configuration is sent to the server in the call. Oh My Posh says it is not stored or logged, and is validated in memory and discarded. Oh My Posh's MCP server documentation
- The validator uses the latest schema from the main branch, and Oh My Posh says some newer properties might not be recognized by an older Oh My Posh version. Oh My Posh's MCP server documentation
How to limit it
With Oh My Posh's own settings, as its documentation describes them. Stackduke has not tested them.
- We recommend checking a configuration for anything private before the agent sends it, even though Oh My Posh says the content is not stored or logged. Oh My Posh's MCP server documentation
- Oh My Posh says the server needs no authentication, so we recommend connecting it with no credentials. Oh My Posh's MCP server documentation
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.