SkillOS MCP Server
NPM · SKILLOS-MCP-SERVER · SCANNED SEP 26
SkillOS MCP Runtime exposes the SkillOS skill registry as activatable MCP tools for AI agents.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 33 of 107 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 2 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 951 tokens (~118/item across 8 items; 8 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "chain_skills" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the SkillOS MCP Server server?
SkillOS MCP Server runs locally as an npm package, launched with npx -y skillos-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · skillos-mcp-server
claude mcp add joshanihub-skillos-mcp-server -- npx -y skillos-mcp-server
{
"mcpServers": {
"joshanihub-skillos-mcp-server": {
"command": "npx",
"args": [
"-y",
"skillos-mcp-server"
]
}
}
} {
"servers": {
"joshanihub-skillos-mcp-server": {
"command": "npx",
"args": [
"-y",
"skillos-mcp-server"
]
}
}
} codex mcp add joshanihub-skillos-mcp-server -- npx -y skillos-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"joshanihub-skillos-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"skillos-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add joshanihub-skillos-mcp-server --command npx --arg -y --arg skillos-mcp-server
mcp_servers:
joshanihub-skillos-mcp-server:
command: "npx"
args: ["-y", "skillos-mcp-server"] {
"McpServers": {
"joshanihub-skillos-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"skillos-mcp-server"
]
}
}
} assistant mcp add joshanihub-skillos-mcp-server -t stdio -c npx -a -y skillos-mcp-server
{
"mcpServers": {
"joshanihub-skillos-mcp-server": {
"command": "npx",
"args": [
"-y",
"skillos-mcp-server"
]
}
}
} 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.
- 25 Sept 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
- 23 Sept 26 64
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 26 Sept 2026 · Analysed npm/skillos-mcp-server@3.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 107 packages
| Packages resolved | 107 |
|---|---|
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
activate_skill ~193
Activate a SkillOS skill. The model will operate under that skill's full professional identity, decision engine, constraint matrix, failure mode library, and quality gates. SDS compliance is enforced — incomplete skills cannot be activated.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | SkillOS platform API key (sk-os_...). Required to access premium or enterprise-only skills. Free-tier skills work without a key. |
| archive | boolean | – | Set to true to activate an archived (older) version. Requires version to also be specified. |
| skill_name | string | yes | The skill_name from list_skills (e.g., 'software_architect', 'mobile_specialist') |
| temperature_override | string | – | Override the skill's default temperature mode. Conservative for high-stakes domains, creative for prototyping. |
| version | string | – | Specific version to activate (e.g., '1.0.0'). Defaults to the latest stable version. |
No output schema declared.
No examples provided.
chain_skills ~211
Execute a multi-skill workflow in sequence. Each skill in the chain receives the output of the previous one as additional context, with constraints (regional_context, compliance requirements) propagating automatically through the chain.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | SkillOS platform API key (sk-os_...). Required if any skill in the workflow is premium or enterprise-only. |
| handoff_constraints | array | – | Mandatory constraints and contracts passed between skill transitions. |
| initial_context | string | yes | The user's request or project description to feed into the first skill in the chain. |
| permission_scope | array | – | Bounded permission scopes that propagate across all skills in the chain (e.g. ['read:only', 'env:staging']) |
| temperature_override | string | – | Apply the same temperature mode to all skills in the chain. |
| workflow | array | yes | Ordered list of skill_names to activate in sequence (minimum 2). E.g. ['software_architect', 'backend_specialist', 'database_specialist'] |
No output schema declared.
No examples provided.
create_workflow ~125
Design an optimal multi-skill workflow for a given task. Returns a recommended skill sequence with rationale, handoff fields, and estimated complexity — without activating any skills.
| Name | Type | Req | Description |
|---|---|---|---|
| max_steps | integer | – | Maximum number of skills in the workflow (2-6). Default: 4. |
| prefer_tier | integer | – | Prefer skills at or above this tier level. Omit to let the router decide. |
| task | string | yes | Describe the task or project you need help with. Be as specific as possible about the technology stack, scale, constraints, and deliverables. |
No output schema declared.
No examples provided.
get_skill_info ~62
Get detailed information about a skill including its Collaboration Contract (typed I/O), validation status, and SDS compliance report. Use this to plan workflows before activating skills.
| Name | Type | Req | Description |
|---|---|---|---|
| skill_name | string | yes | The skill_name to inspect (e.g., 'backend_specialist') |
No output schema declared.
No examples provided.
get_skill_routing ~94
Route a user request to the single best-matching skill. Returns the recommended skill with confidence score and explanation. Use this when you want one skill, not a full workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_hint | string | – | Optional domain keyword to narrow the search (e.g. 'security', 'frontend', 'database'). |
| request | string | yes | The user's request or question. The router will match it to the best skill. |
No output schema declared.
No examples provided.
list_connectors ~70
List all available and configured external tool connectors in SkillOS (GitHub, PostgreSQL, Slack, Stripe, M-Pesa, etc.). Shows integration status and capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category: 'Developer Tools', 'Data', 'Communication', 'Finance', 'Productivity' |
No output schema declared.
No examples provided.
list_skills ~131
List all available SkillOS skills in the registry. Filter by tier (0-4) or domain keyword. Shows SDS compliance status for each skill.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Filter by domain keyword (case-insensitive). E.g. 'security', 'mobile', 'database'. |
| include_archived | boolean | – | Include archived (superseded) skill versions. Default: false. |
| tier | integer | – | Filter by tier (0=Foundational, 1=Domain, 2=Technology, 3=Pattern, 4=Orchestration). Omit for all tiers. |
No output schema declared.
No examples provided.
test_connector ~65
Test connectivity to a SkillOS tool connector (e.g. 'github', 'slack', 'postgresql'). Verifies credentials and reports connection health.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The connector slug to test (e.g., 'github', 'slack', 'postgresql') |
No output schema declared.
No examples provided.
What is the SkillOS MCP Server server?
SkillOS MCP Server is listed in the public MCP registry as io.github.Joshanihub/skillos-mcp-server. SkillOS MCP Runtime exposes the SkillOS skill registry as activatable MCP tools for AI agents. This page covers its npm package (skillos-mcp-server).
Is the SkillOS MCP Server server safe to use?
SkillOS MCP Server scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. 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 SkillOS MCP Server server expose?
SkillOS MCP Server exposes 8 tools: list_skills, activate_skill, get_skill_info, chain_skills, create_workflow, and 3 more. Their descriptions and schemas cost roughly 951 tokens of context every time the server is loaded.
Is the SkillOS MCP Server server still maintained?
SkillOS MCP Server is still listed as active in the MCP registry. We last reached this channel on 26 September 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 SkillOS MCP Server server under?
SkillOS MCP Server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.