SKILL.md Lint
REMOTE · MCP.MOLTLINESTUDIO.COM · SCANNED SEP 21
Lint a SKILL.md for frontmatter, structure, secrets and size. All 6 tools free.
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1593 tokens (~265/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the SKILL.md Lint MCP server?
SKILL.md Lint is a hosted endpoint at https://mcp.moltlinestudio.com/skillmd-lint, 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 · mcp.moltlinestudio.com
claude mcp add --transport http com-moltlinestudio-skillmd-lint 'https://mcp.moltlinestudio.com/skillmd-lint'
{
"mcpServers": {
"com-moltlinestudio-skillmd-lint": {
"url": "https://mcp.moltlinestudio.com/skillmd-lint"
}
}
} {
"servers": {
"com-moltlinestudio-skillmd-lint": {
"type": "http",
"url": "https://mcp.moltlinestudio.com/skillmd-lint"
}
}
} [mcp_servers.com-moltlinestudio-skillmd-lint] url = "https://mcp.moltlinestudio.com/skillmd-lint"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-moltlinestudio-skillmd-lint": {
"type": "remote",
"url": "https://mcp.moltlinestudio.com/skillmd-lint",
"enabled": true
}
}
} openclaw mcp add com-moltlinestudio-skillmd-lint --url 'https://mcp.moltlinestudio.com/skillmd-lint' --transport streamable-http
mcp_servers:
com-moltlinestudio-skillmd-lint:
url: "https://mcp.moltlinestudio.com/skillmd-lint" {
"McpServers": {
"com-moltlinestudio-skillmd-lint": {
"Transport": "http",
"Url": "https://mcp.moltlinestudio.com/skillmd-lint"
}
}
} assistant mcp add com-moltlinestudio-skillmd-lint -t streamable-http -u 'https://mcp.moltlinestudio.com/skillmd-lint'
{
"mcpServers": {
"com-moltlinestudio-skillmd-lint": {
"type": "http",
"url": "https://mcp.moltlinestudio.com/skillmd-lint"
}
}
} 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.
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 0
- Tool “regex_test” rewrote its description, which is the text the model reads security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +10
- Authorization: unverified → partial ▲ security
- HSTS header: unverified → pass ▲ security
- 6 Sept 26 −9
- Authorization: partial → unverified ▼ security
- HSTS header: pass → unverified ▼ security
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 21 Sept 2026 · Probed https://mcp.moltlinestudio.com/skillmd-lint
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=moltlinestudio.com | CN=WE1,O=Google Trust Services,C=US | 15 Aug 2026 | 13 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 72e09c6114448e7a0ed370fb03c277cb |
| SANs: moltlinestudio.com, *.moltlinestudio.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.moltlinestudio.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| moltlinestudio.com. | present | 2371 | 13 | Verified |
| mcp.moltlinestudio.com. | Verified address RRset verified with the apex keys |
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=15576000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://api.moltlinestudio.com https://mcp.moltlinestudio.com; form-action 'self'; frame-ancestors 'none'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.moltlinestudio.com/skillmd-lint | Verified | 200 | |
| http (plaintext) | http://mcp.moltlinestudio.com/skillmd-lint | HTTPS enforced | 301 | https://mcp.moltlinestudio.com/skillmd-lint |
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 →
cron_explain Cron Explain ~252
Explain a 5-field cron expression in plain English and flag mistakes. FREE. Typical input {"expression": "0 9 * * 1-5"} returns {"expression": "0 9 * * 1-5", "meaning": "at minute 0; at hour 9; every day of month; every month; day of week 1-5", "issues": ["none"]}; out-of-range fields are listed in "issues". Use to read a schedule back in plain English before trusting it. Assumes 5-field cron; not for 6-field or seconds-precision variants. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "expected 5 fields, got <value>"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Type | Req | Description |
|---|---|---|---|
| expression | string | yes | A standard 5-field cron string (minute hour day-of-month month day-of-week), e.g. "0 9 * * 1-5"; must be non-empty. |
Structured output declared, but exposes no named fields.
No examples provided.
diff_texts Diff Texts ~263
Produce a unified diff between two texts. FREE. Useful for comparing two SKILL.md versions. Typical input {"a": "<old text>", "b": "<new text>"} returns {"changed_lines": N, "diff": "--- \n+++ \n@@ ... @@\n-old line\n+new line"}; identical inputs return {"changed_lines": 0, "diff": "(identical)"}. The diff is capped at 400 lines. Use to show exactly what changed between two versions of a text. Not for judging the risk of a code change - the codereview server's review_diff does that. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "each text must be at most 500000 characters"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | The original text (left side of the diff); at most 500000 characters. |
| b | string | yes | The revised text (right side of the diff); at most 500000 characters. |
Structured output declared, but exposes no named fields.
No examples provided.
json_validate Json Validate ~213
Validate JSON text and summarize its structure. FREE. Typical input {"text": "{\"a\": [1, 2]}"} returns {"valid": true, "structure": {"a": ["array[2]", "int"]}}; invalid JSON returns {"valid": false, "error": "<parser message>", "line": N, "column": N} instead. Use when JSON may be malformed or its shape is unknown. Reports structure, not conformance to a schema. Not for testing a pattern (regex_test). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "text is empty — pass the JSON document as a raw string"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The JSON document to validate, as a raw string; must be non-empty. |
Structured output declared, but exposes no named fields.
No examples provided.
lint_skill Lint Skill ~252
Lint one SKILL.md file the way marketplaces and agents parse it. FREE. Checks YAML frontmatter presence and required fields (name, description), description quality, body structure (procedure steps, rules, degradation), secret/credential leakage, injection-style phrasing, and size budget. Typical input {"content": "<full SKILL.md text>"} returns {"verdict": "pass" | "pass-with-warnings" | "fail", "errors": ["..."], "warnings": ["..."], "stats": {"body_words": N, "has_frontmatter": bool}}. Use on the full text of one SKILL.md. Not for the surrounding archive layout (packaging_check). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "content is empty — pass the full SKILL.md text including frontmatter"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The complete SKILL.md file text, frontmatter included; must be non-empty. |
Structured output declared, but exposes no named fields.
No examples provided.
packaging_check Packaging Check ~283
Validate a zip layout plan for a skill marketplace before packaging. FREE. Checks SKILL.md placement rules and flags junk files. Typical input {"file_paths": ["my-skill/SKILL.md", "my-skill/examples.md"], "marketplace": "agensi"} returns {"verdict": "pass" | "fail", "issues": ["..."], "skill_files_found": ["my-skill/SKILL.md"]}. Use on a planned file layout, before zipping. Not for the content of a skill file (lint_skill). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "file_paths is empty — list every file that will be inside the zip"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Type | Req | Description |
|---|---|---|---|
| file_paths | array | yes | Every file path that will be inside the zip, relative to the zip root, e.g. ["my-skill/SKILL.md"]; at least 1 entry. |
| marketplace | string | – | Rule set to apply: "agensi" (SKILL.md at root or one folder deep) or "generic" (junk-file checks only). Default "agensi". |
Structured output declared, but exposes no named fields.
No examples provided.
regex_test Regex Test ~285
Test a regular expression against sample strings. FREE. Typical input {"pattern": "v(\\d+)", "samples": ["v12", "beta"]} returns {"pattern": ..., "results": [{"sample": "v12", "match": true, "matched_text": "v12", "groups": ["12"]}, {"sample": "beta", "match": false, ...}], "match_count": 1}. Use to confirm a pattern matches what you expect before shipping it. Not for validating JSON (json_validate). The pattern is compiled and run in a short-lived, CPU-capped child process, so a pattern that backtracks catastrophically is stopped instead of stalling the server. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "a sample is too long (max 10000 characters); shorten it and retry"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Type | Req | Description |
|---|---|---|---|
| pattern | string | yes | A Python-flavor regular expression as a string, e.g. "v(\\d+)". |
| samples | array | yes | Strings to test the pattern against; only the first 50 are evaluated. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the SKILL.md Lint MCP server?
SKILL.md Lint is an MCP server listed in the public MCP registry as com.moltlinestudio/skillmd-lint. Lint a SKILL.md for frontmatter, structure, secrets and size. All 6 tools free. This page covers its hosted endpoint (https://mcp.moltlinestudio.com/skillmd-lint).
Is the SKILL.md Lint MCP server safe to use?
SKILL.md Lint scores 87 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 SKILL.md Lint MCP server expose?
SKILL.md Lint exposes 6 tools: lint_skill, packaging_check, regex_test, json_validate, diff_texts, cron_explain. Their descriptions and schemas cost roughly 1,548 tokens of context every time the server is loaded.
Does the SKILL.md Lint MCP server require authentication?
No. We connected to SKILL.md Lint without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SKILL.md Lint MCP server still maintained?
SKILL.md Lint is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.