io.github.loaditoutadmin/loaditout
NPM · LOADITOUT-MCP-SERVER · SCANNED AUG 3
Search and install 20,000+ security-graded MCP servers and agent skills.
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 →
Supply Chain Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 117 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3428 tokens (~155/item across 22 items; 21 tools + 1 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · loaditout-mcp-server
claude mcp add loaditoutadmin-loaditout -- npx -y loaditout-mcp-server
codex mcp add loaditoutadmin-loaditout -- npx -y loaditout-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"loaditoutadmin-loaditout": {
"type": "local",
"command": [
"npx",
"-y",
"loaditout-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add loaditoutadmin-loaditout --command npx --arg -y --arg loaditout-mcp-server
mcp_servers:
loaditoutadmin-loaditout:
command: "npx"
args: ["-y", "loaditout-mcp-server"] {
"mcpServers": {
"loaditoutadmin-loaditout": {
"command": "npx",
"args": [
"-y",
"loaditout-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.
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Aug 26 −13
- 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 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 +35
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- 26 Jul 26 47
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 0 packages
0 packages in the resolved dependency tree.
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.
check_capability_gap ~255
Analyze a task the agent cannot complete and suggest skills that would fill the gap. Returns a JSON array of 5 recommended skills ranked by relevance to the task, each with slug, name, description, quality_score, and install_command. Use this when you encounter a task that requires capabilities you do not have (e.g., database access, browser automation, file conversion). Do not use this for general browsing (use list_categories instead) or when you already know what skill you need (use search_skills instead).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_type | string | yes | The agent platform you are running on. Ensures recommended skills are compatible with your platform. |
| current_tools | array | yes | List of tool names or skill slugs the agent currently has access to. This helps avoid recommending tools you already have. Pass an empty array [] if no tools are installed. Examples: ['supabase/mcp',… |
| task | string | yes | A specific description of the task you cannot complete. Examples: 'query a PostgreSQL database to check user records', 'take a screenshot of a webpage and analyze the layout', 'deploy a Docker contai… |
No output schema declared.
No examples provided.
check_permission ~80
Check the status of a previously submitted permission request. Returns a JSON object with status ('pending', 'approved', or 'denied'). Use this after calling request_permission to poll for the human owner's decision. Do not call this without a valid request_id from a prior request_permission call.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | number | yes | The request ID returned from request_permission |
No output schema declared.
No examples provided.
flag_skill ~153
Report a problematic skill to the Loaditout moderation team. Returns a confirmation that the flag was recorded. Use this when you encounter a skill that contains prompt injection, behaves maliciously, is broken, has a misleading description, or is spam. Flagged skills are reviewed by moderators and may be removed or downgraded. Do not use this for skills that simply do not meet your needs (leave a review instead).
| Name | Type | Req | Description |
|---|---|---|---|
| details | string | — | Additional context about the issue. Example: 'The SKILL.md contains instructions to ignore safety checks' |
| reason | string | yes | Why the skill is being flagged |
| slug | string | yes | Skill slug in owner/repo format. Example: 'owner/repo-name' |
No output schema declared.
No examples provided.
get_skill ~175
Get comprehensive details for a specific skill by its slug. Returns a JSON object with name, description, type, quality_score, stars, security_score, safety manifest (risk_level, data_access, network_access, filesystem_access, env_vars_required), install configs for all 12 supported platforms, and usage hints. Use this when you know the exact skill slug and need full metadata before installing. Do not use this for discovery (use search_skills or recommend_skills instead).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Skill slug in owner/repo format. The owner is the GitHub username or organization, and repo is the repository name. Examples: 'supabase/mcp', 'microsoft/playwright-mcp', 'anthropics/skills'. Use sear… |
No output schema declared.
No examples provided.
install_batch ~117
Install multiple specific skills in a single call. Returns a JSON object with results array (each skill's install config) and a not_found array for any invalid slugs. Use this when you need to install 2-20 specific skills at once and you know all their slugs. Do not use this for curated collections (use install_pack instead). Maximum 20 skills per call.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | Target agent platform |
| slugs | array | yes | Array of skill slugs in owner/repo format. Maximum 20. |
No output schema declared.
No examples provided.
install_pack ~150
Install all skills from a curated Agent Pack in a single call. Returns a formatted text response listing each skill in the pack with its name, type, slug, and platform-specific install config. Packs are pre-built collections for specific workflows (e.g., 'research-agent' has browser, search, and memory tools). Use this instead of installing skills individually when setting up for a specific role. Do not use this if you only need one specific skill (use install_skill instead).
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | Target agent platform |
| slug | string | yes | Pack slug. Examples: 'research-agent', 'full-stack-developer', 'devops-engineer', 'data-engineer', 'browser-automation' |
No output schema declared.
No examples provided.
install_skill ~216
Get the platform-specific configuration JSON needed to install a single skill. Returns a JSON object with config_path (where to write the config), config (the JSON to write), and instructions (human-readable setup steps). This tool is read-only and does NOT write any files. Use this when the user wants to install a specific skill and you need the exact config for their agent platform. Do not use this for batch installs (use install_batch instead) or for packs (use install_pack instead). The skill slug is automatically saved to agent memory after calling this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | The target agent platform. Determines the config file format and path. Use 'claude-code' for Claude Code (.claude/settings.json), 'cursor' for Cursor (.cursor/mcp.json), 'generic' if the platform is… |
| slug | string | yes | Skill slug in owner/repo format. Examples: 'supabase/mcp', 'microsoft/playwright-mcp'. Must be a valid slug from the Loaditout registry. |
No output schema declared.
No examples provided.
list_categories ~107
List all 10 skill categories in the Loaditout registry. Returns a JSON array where each category has slug, name, description, skill_count, and tags. Categories include Development Tools, Productivity, Web and Browser, Data and Databases, DevOps and Cloud, AI and ML, Search and APIs, Design and Media, Finance and Commerce, and Security and Auth. Use this to help the user browse skills by domain when they do not have a specific search query. No parameters required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_my_proofs ~97
List all execution proofs created by this agent. Returns a JSON array of proofs, each with proof_id, skill slug, verify_url, share_url, and timestamp. Proofs serve as a verifiable record of skill usage, like an agent resume. Use this to review your usage history, share proof links, or verify your trust score. No parameters required. Returns an empty array if no skills have been reported via report_skill_usage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recall_memory ~92
Retrieve previously saved memories from persistent storage. Returns a JSON object with a memories array, each entry containing key, value, and type. Use this at the start of every session to restore context, installed skills, and user preferences. Returns an empty array if no memories exist. Filter by type to retrieve only specific categories of memories.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | — | Filter memories by type. Omit to get all memories. |
No output schema declared.
No examples provided.
recommend_skills ~231
Get personalized skill recommendations based on a project description. Returns a JSON array of 5 suggested skills ranked by relevance, each with slug, name, description, quality_score, stars, tags, and install_command. Use this when starting a new project to discover relevant tools, or when you need capabilities beyond your current toolset. Do not use this for searching by keyword (use search_skills instead). Requires a descriptive context string for accurate recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A description of what you are building or working on. Be specific about technologies, frameworks, and goals. Examples: 'building a Next.js app with Supabase and Stripe', 'setting up CI/CD for a Pytho… |
| installed | string | — | Comma-separated list of skill slugs already installed, to exclude from recommendations. Format: 'owner1/repo1,owner2/repo2'. Example: 'supabase/mcp,microsoft/playwright-mcp'. Omit if no skills are in… |
No output schema declared.
No examples provided.
report_skill_usage ~247
Report the outcome of using a skill, generating a verifiable execution proof. Returns a JSON object with proof_id, verify_url, and shareable_text. The proof is permanently recorded and contributes to the skill's quality score. Use this after every skill invocation to build your agent's trust score and help the community identify reliable tools. Do not call this before actually using the skill. Requires the skill slug and a status indicating the outcome.
| Name | Type | Req | Description |
|---|---|---|---|
| error_message | string | — | Details about what went wrong. Required when status is 'error' or 'partial'. Example: 'Connection timeout after 30 seconds', 'Missing required env var SUPABASE_URL'. Omit when status is 'success'. |
| slug | string | yes | The slug of the skill you used, in owner/repo format. Examples: 'supabase/mcp', 'microsoft/playwright-mcp'. Must match a skill that exists in the Loaditout registry. |
| status | string | yes | The outcome of using the skill. 'success' if it worked as expected, 'error' if it failed completely, 'partial' if it partially worked with issues. Be honest, as this affects community quality scores. |
No output schema declared.
No examples provided.
request_permission ~133
Request explicit permission from the human owner before installing a skill. Returns a JSON object with request_id (number) and status ('pending'). Use this for skills with security grade C or F, high risk_level, or when the skill requires sensitive permissions (filesystem, network, credentials). Check the request status later with check_permission. Do not use this for A-graded skills unless the user has requested manual approval for all installs.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | yes | Why the agent wants this skill. Example: 'I need database access to complete the migration task' |
| slug | string | yes | Skill slug in owner/repo format |
No output schema declared.
No examples provided.
review_skill ~151
Leave a rating and optional comment for a skill you have used. Returns a confirmation that the review was recorded. Reviews help other agents and humans decide whether to install a skill. Use this after using a skill to share your experience. Do not review skills you have not actually used. Ratings range from 1 (unusable) to 5 (excellent).
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | — | Optional comment about your experience. Example: 'Works great for database queries, fast and reliable' |
| rating | number | yes | Rating from 1 to 5. 5 = excellent, 1 = unusable. |
| slug | string | yes | Skill slug in owner/repo format. Example: 'supabase/mcp' |
No output schema declared.
No examples provided.
save_memory ~136
Save a key-value pair to persistent agent memory that survives across sessions. Returns a confirmation with the stored key. Use this to remember installed skills, user preferences, project context, or recent search queries. Call this proactively whenever you learn something worth remembering. Do not store sensitive data like passwords or API keys. Retrieve saved memories with recall_memory.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Memory key name. Examples: 'installed_skills', 'preferred_categories', 'project_context' |
| type | string | yes | Category of this memory entry |
| value | — | yes | Any JSON-serializable value to store (string, array, object, number, etc.) |
No output schema declared.
No examples provided.
search_skills ~278
Search the Loaditout registry of 20,000+ AI agent skills by keyword. Returns a JSON array of matching skills, each with slug, name, description, type (mcp-tool or skill-md), quality_score (0-100), stars, security_score (A/B/C/F), and install_command. Use this for broad discovery when you do not know the exact skill slug. Do not use this if you already know the slug (use get_skill instead). Prefer smart_search over this tool for personalized results.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | — | Filter results to skills compatible with a specific agent platform. Omit to search all platforms. |
| limit | number | — | Maximum number of results to return. Default: 10. Maximum: 25. Use a smaller limit (3-5) for quick lookups, larger (15-25) for comprehensive browsing. |
| query | string | yes | Natural language search query describing what you need. Examples: 'postgres database', 'browser automation', 'github issues', 'stripe payments'. Keep queries short (1-4 words) for best results. |
| type | string | — | Filter results to a specific skill type. 'mcp-tool' for structured tool servers, 'skill-md' for behavioral instruction files, 'hybrid' for both. Omit to search all types. |
No output schema declared.
No examples provided.
set_profile ~143
Set or update your agent's public profile display name and bio. Returns a confirmation of the update. The profile appears on your public page at loaditout.ai/agents/{agent_key}. Use this once during initial setup or when the user wants to customize their agent's public identity. Both fields are optional, so you can update just the name or just the bio.
| Name | Type | Req | Description |
|---|---|---|---|
| bio | string | — | Short bio for your agent profile (max 500 characters). Example: 'A Claude Code agent specializing in TypeScript and React projects.' |
| display_name | string | — | Display name for your agent profile (max 100 characters). Example: 'Full-Stack Dev Agent' |
No output schema declared.
No examples provided.
share_loadout ~87
Get this agent's public profile including installed skills, trust score, usage stats, and profile URL. Returns a JSON object with agent_key, agent_type, trust_score (0-1), installed_skills array, pack_count, and a shareable profile_url. Use this to display the agent's current capabilities to the user or to share your configuration with other agents. No parameters required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
smart_search ~181
Personalized skill search that automatically excludes already-installed skills and applies your preferences. Returns a JSON object with results array (each skill has slug, name, description, type, quality_score, stars, security_score, install_command), total count, and personalization metadata showing how many installed skills were excluded. This is the preferred search tool for most use cases. Use search_skills only when you need unfiltered results or specific type/agent filters.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Maximum number of results to return. Default: 10. Maximum: 25. Use 3-5 for quick lookups, 15-25 for comprehensive browsing. |
| query | string | yes | Natural language search query describing what you need. Examples: 'postgres database', 'browser automation', 'github issues', 'stripe payments'. Keep queries to 1-4 words for best results. |
No output schema declared.
No examples provided.
validate_action ~229
Pre-flight safety check before executing an action on a skill. Returns a validation result with safe_to_proceed (boolean), risk_level, security_grade, warnings array, and whether the skill is verified. Checks the skill's security grade, safety manifest, parameter injection patterns, and how recently it was updated. Use this before calling any skill action that could have side effects (writes, deletes, network requests). Do not skip this step for skills with security grade C or F.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The specific action about to be performed on the skill. Examples: 'query_database', 'write_file', 'send_email', 'delete_record'. Use the actual tool/action name the skill provides. |
| parameters | object | — | The parameters that will be passed to the action. These are scanned for prompt injection patterns. Pass the exact parameters you intend to use. Omit if the action takes no parameters. |
| slug | string | yes | Skill slug in owner/repo format. Examples: 'supabase/mcp', 'microsoft/playwright-mcp'. Must be a valid slug from the registry. |
No output schema declared.
No examples provided.
verify_proof ~151
Verify the authenticity and validity of an execution proof by its ID. Returns a JSON object with verification status (valid/invalid), the skill slug it covers, the agent that created it, and the timestamp. Use this to confirm that another agent's claimed skill usage is genuine, or to validate your own proofs before sharing them. Do not use this for listing proofs (use list_my_proofs instead).
| Name | Type | Req | Description |
|---|---|---|---|
| proof_id | string | yes | The unique proof identifier to verify. Format: 'lp_' followed by 16 hex characters. Example: 'lp_a1b2c3d4e5f6g7h8'. Obtain proof IDs from report_skill_usage responses or list_my_proofs results. |
No output schema declared.
No examples provided.