MCPskills
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCPSKILLS_API_KEY | No | API key for full reports and advanced features. Get it at mcpskills.io/api |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_trust_scoreA | Score any AI skill, MCP server, or GitHub repo for trustworthiness. Returns a trust score (0-10) across 4 dimensions: Alive, Legit, Solid, Usable. Accepts: owner/repo, GitHub URL, npm package (npm:@scope/name or @scope/name), Smithery URL, or OpenClaw URL. AI skills get enhanced safety scanning. Set MCPSKILLS_API_KEY for full reports. |
| scan_safetyA | Run a focused safety scan on an AI skill or MCP server. Checks for prompt injection, shell execution, network exfiltration, credential theft, obfuscated payloads, public network binding (0.0.0.0), and risky npm lifecycle scripts (preinstall/install/postinstall). Accepts any input format (owner/repo, npm package, Smithery URL, etc.). |
| list_packagesA | Browse curated, pre-scored AI skill packages organized by use case. Each package contains vetted skills with trust scores. Available packages: Claude Power User, Full-Stack Vibe Coder, Data & Research, DevOps & Infrastructure, Content & Marketing. |
| get_badgeA | Get a trust badge URL for any repo or package. Returns a shields.io-style SVG badge showing the trust score and tier. Embed in READMEs. Badge auto-updates hourly. |
| watch_repoA | Start monitoring a repo or package for trust score changes. Alerts when score changes significantly (±0.3 points or tier change). Requires a paid API key. |
| check_watchedA | Re-scan all watched repos and check for score changes. Returns any repos whose trust score changed significantly since last check. |
| batch_checkA | Check up to 5 repos or packages in one call. Returns a trust assessment for each. Requires a Developer Pro or Team API key. Accepts any mix of formats (owner/repo, npm packages, registry URLs). |
| auto_gateA | Should I install this? Returns a simple go/no-go decision with reasoning. Accepts any format: owner/repo, npm package, Smithery URL, etc. Returns { proceed: true/false, reason: "..." }. |
| build_stackA | Recommend a vetted stack of trusted tools for a described task. Describe what you're building (e.g., "Next.js app with auth, payments, and AI chat") and get back a curated list of the highest-scoring repos in each relevant category, pre-scored and ready to install. Returns tool names, trust scores, tiers, and install hints. Use this instead of guessing which tools to recommend — every suggestion is backed by live trust data. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: auto_gate gives a simple go/no-go decision, check_trust_score provides detailed scoring, batch_check handles multiples, scan_safety focuses on safety, list_packages curates packages, build_stack recommends stacks, get_badge generates badges, check_watched and watch_repo monitor changes. No two tools have overlapping functionality that would cause confusion.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., auto_gate, batch_check, check_trust_score, watch_repo). The naming is predictable and easy to parse, with no mixing of conventions.
With 9 tools, the set is well-scoped for a trust and safety assessment server. Each tool serves a necessary function without being redundant or excessive, fitting comfortably within the ideal 3-15 range.
The tool surface covers the full lifecycle of trust assessment: single and batch scoring, safety scanning, recommendation (build_stack), curated packages (list_packages), monitoring (watch_repo, check_watched), and a badge output (get_badge). There are no obvious gaps for the stated purpose.