Oh My Posh Validator
REMOTE · OHMYPOSH.DEV · SCANNED SEP 24
Validate oh-my-posh configurations and segment snippets against the official schema.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 142 tokens (~71/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Oh My Posh Validator MCP server?
Oh My Posh Validator is a hosted endpoint at https://ohmyposh.dev/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ohmyposh.dev
claude mcp add --transport http dev-ohmyposh-validator 'https://ohmyposh.dev/api/mcp'
{
"mcpServers": {
"dev-ohmyposh-validator": {
"url": "https://ohmyposh.dev/api/mcp"
}
}
} {
"servers": {
"dev-ohmyposh-validator": {
"type": "http",
"url": "https://ohmyposh.dev/api/mcp"
}
}
} [mcp_servers.dev-ohmyposh-validator] url = "https://ohmyposh.dev/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-ohmyposh-validator": {
"type": "remote",
"url": "https://ohmyposh.dev/api/mcp",
"enabled": true
}
}
} openclaw mcp add dev-ohmyposh-validator --url 'https://ohmyposh.dev/api/mcp' --transport streamable-http
mcp_servers:
dev-ohmyposh-validator:
url: "https://ohmyposh.dev/api/mcp" {
"McpServers": {
"dev-ohmyposh-validator": {
"Transport": "http",
"Url": "https://ohmyposh.dev/api/mcp"
}
}
} assistant mcp add dev-ohmyposh-validator -t streamable-http -u 'https://ohmyposh.dev/api/mcp'
{
"mcpServers": {
"dev-ohmyposh-validator": {
"type": "http",
"url": "https://ohmyposh.dev/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 78
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 24 Sept 2026 · Probed https://ohmyposh.dev/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ohmyposh.dev | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 7 Aug 2026 | 6 Feb 2027 | RSA 2048 | SHA256-RSA | ddf2f39b5b69fbce89778a9c8d3e438 |
| SANs: ohmyposh.dev | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ohmyposh.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| ohmyposh.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ohmyposh.dev/api/mcp | Verified | 200 | |
| http (plaintext) | http://ohmyposh.dev/api/mcp | HTTPS enforced | 307 | https://ohmyposh.dev/api/mcp |
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 →
validate_config ~69
Validate an oh-my-posh configuration against the schema. Supports JSON, YAML, and TOML formats.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The configuration content as a string (JSON, YAML, or TOML) |
| format | string | – | The format of the configuration (auto-detect if not specified) |
No output schema declared.
No examples provided.
validate_segment ~73
Validate a segment snippet against the oh-my-posh schema. Useful for validating individual prompt segments before adding them to a configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The segment content as a string (JSON, YAML, or TOML) |
| format | string | – | The format of the segment (auto-detect if not specified) |
No output schema declared.
No examples provided.
What is the Oh My Posh Validator MCP server?
Oh My Posh Validator is an MCP server listed in the public MCP registry as dev.ohmyposh/validator. Validate oh-my-posh configurations and segment snippets against the official schema. This page covers its hosted endpoint (https://ohmyposh.dev/api/mcp).
Is the Oh My Posh Validator MCP server safe to use?
Oh My Posh Validator scores 78 out of 100 on VerifyMCP. 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 Oh My Posh Validator MCP server expose?
Oh My Posh Validator exposes 2 tools: validate_config, validate_segment. Their descriptions and schemas cost roughly 142 tokens of context every time the server is loaded.
Does the Oh My Posh Validator MCP server require authentication?
No. We connected to Oh My Posh Validator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Oh My Posh Validator MCP server still maintained?
Oh My Posh Validator is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.