Oh My Posh Validator by ohmyposh.dev
MCP server · indexed, not reviewed
Hostedvendor's ownwidely used
Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
Validate oh-my-posh configurations and segment snippets against the official schema.
Facts
- MCP registry
dev.ohmyposh/validator· 29.37.0- Endpoint
https://ohmyposh.dev/api/mcp- GitHub stars
- 24k
- Registry entry
- updated 30 Jul 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under ohmyposh.dev, a namespace the registry only gives to whoever proves they control that domain.
- It's in real use: 23,531 GitHub stars.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 2 · about 421 tokens of context · checked 11 minutes ago
| Tool | What it does | Hint |
|---|---|---|
validate_config | Validate an oh-my-posh configuration against the schema. Supports JSON, YAML, and TOML formats. | |
validate_segment | Validate a segment snippet against the oh-my-posh schema. Useful for validating individual prompt segments before adding them to a configuration. |
What https://ohmyposh.dev/api/mcp answered to tools/list, asked without credentials. answered without the initialize handshake. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 2 warnings · 1 note
- warnTC16validate_configno readOnlyHint or destructiveHint
- warnTC16validate_segmentno readOnlyHint or destructiveHint
- noteTC24server2 of 2 tools have no outputSchema
The checks from /check and anchor check, run each day on the list above: about 421 tokens of definitions. Not part of the score yet. Check your own server.