A
licenseA
qualityD
maintenanceSearch and discover 3,500+ AI tools, MCP servers, and Claude Skills with community ratings. Find the best tools by category, compatibility, and real user reviews.
3
54 npm
MIT
Skill of Skills
Server Details
Quality-ranked, cross-platform directory of AI coding skills, plugins and MCP servers.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over 68 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- the911fund/skill-of-skills
- GitHub Stars
- 11
TDQS
A3.9/5.0
Scored across 6 tools
Disambiguation5/5
Each tool targets a distinct function: search, single lookup, comparison, collection listing, collection contents, and demand trends. No two tools overlap in intent, and descriptions clarify the boundaries (e.g. list_collections vs get_collection vs get_skill).
Naming Consistency4/5
Five of six tools follow a clean verb_noun pattern (compare_tools, get_collection, get_skill, list_collections, search_skills). demand_pulse breaks the pattern as a noun_verb label, a minor but noticeable deviation.
Tool Count5/5
Six tools is well-scoped for a discovery/catalog server, with each tool earning its place across search, browse, detail, compare, and trend operations. Nothing feels padded or missing.
Completeness4/5
The surface covers the full read-only discovery lifecycle: search, browse collections, inspect details, compare, and view demand signals. No obvious dead ends, though a dedicated browse/pagination option for the whole directory is not exposed.
Available Tools
6 toolscompare_toolsCompare toolsARead-onlyIdempotentInspect
Side-by-side quality profiles for 2–5 tools by slug. Same fields as get_skill; ordering follows the request, not rank.
| Name | Required | Description | Default |
|---|---|---|---|
| slugs | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| compared | Yes | |
| not_found | No |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: output ordering follows the request order, not a quality rank, which prevents a real misinterpretation of the results.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two compact clauses, zero filler, and the core identity (side-by-side comparison for 2–5 tools) is front-loaded before the secondary ordering caveat.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists so return-field detail is unnecessary, and the description still helpfully points to get_skill for field shape plus the ordering semantics. Nothing critical is missing for correct invocation; only explicit when-to-use routing would improve it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must carry the parameter meaning — and it does, giving the input type (slugs), the slug format, and the valid count range (2–5). That largely compensates for the undocumented array constraints, though slug pattern/length details only live in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (compare) and resource (tools), with scope bounds (2–5 tools by slug). It explicitly contrasts with the single-tool sibling by noting it returns 'the same fields as get_skill', so an agent can distinguish it from get_skill without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
'For 2–5 tools by slug' implies the bulk/multi-entity case versus get_skill, but the description never states when to prefer this over get_skill or search_skills, nor any exclusions. Usage is inferable from the count constraint rather than spelled out.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
demand_pulseDemand pulseARead-onlyIdempotentInspect
Public, k-anonymous demand signal from the directory: trending searches, most-saved and most-installed tools. Aggregates only — sourced from ≥5 distinct anonymous sessions per entry.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| most_saved | Yes | |
| most_installed | Yes | |
| trending_searches | Yes | |
| total_interactions | Yes |
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond annotations: the k-anonymity guarantee (≥5 distinct anonymous sessions per entry) and the 'Aggregates only' privacy constraint, which are important behavioral traits not visible in the schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no waste. The first sentence states the core purpose and data types; the second adds the critical privacy/aggregation constraint. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless, read-only tool with an output schema present, the description is complete. It explains what the tool returns, the privacy model, and the aggregation source. The output schema presumably details the response structure, so the description doesn't need to.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters, so there is no parameter semantics to document. The description compensates by explaining what the output represents (trending searches, most-saved, most-installed) and the aggregation guarantee, which is the closest thing to parameter semantics for a parameterless tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as a public, k-anonymous demand signal from the directory, listing the specific data types it provides (trending searches, most-saved, most-installed tools). It distinguishes itself from sibling tools like search_skills or get_skill by emphasizing aggregated, anonymous demand data rather than individual tool details or collections.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this is for retrieving aggregate demand signals, and the 'Public' label plus 'Aggregates only' clarifies when it's appropriate. It doesn't explicitly name alternatives or state when not to use it, but the context signals (0 params, read-only) and sibling names make the use case clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_collectionGet collectionBRead-onlyIdempotentInspect
Quality-ranked tools inside one curated collection. Critical-risk tools are excluded by default (risk_filter); every result carries risk_level and risk_reasons.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| limit | No | ||
| risk_filter | No | Risk gate: exclude_critical omits critical risk (default); exclude_high omits high and critical risk; none omits no risk levels | exclude_critical |
| include_high_risk | No | Deprecated alias for risk_filter=none |
Output Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| results | Yes | |
| collection | Yes | |
| total_in_collection | Yes |
TDQS
B3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds real behavioral value by disclosing that critical-risk tools are filtered out by default (an implicit omission the agent must know about), but its second clause about risk_level/risk_reasons re-states return data already covered by the output schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with no filler, and the default-filter constraint is front-loaded. The opening is a noun fragment rather than an action statement, which costs a little immediate clarity but wastes no words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given an output schema that already documents the returned risk fields, the description is close to complete, and it usefully flags the default exclusion of critical-risk tools. The remaining gap is the undocumented slug and limit parameters plus the absence of any routing guidance against the sibling collection/search tools. Wait -- I gave parameter_semantics 3 and usage 2; to keep independence, this dimension focuses on overall sufficiency, which is still short on slug/limit semantics and sibling routing, so 3.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50%: risk_filter and include_high_risk carry inline descriptions (including the deprecation of include_high_risk), while slug and limit are undocumented. The description reinforces the risk_filter gate semantics ('critical-risk tools are excluded by default'), which adds marginal value, but contributes nothing about slug enumeration or the limit cap of 25. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description conveys the resource ('tools inside one curated collection') and a quality ranking, so the agent knows roughly what comes back. But it never states the operative verb or that the required 'slug' selects a single named collection, so the action is inferred from the tool name rather than described. It is distinguishable from list_collections and search_skills only weakly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to call this instead of the very close siblings list_collections, search_skills, or compare_tools. The only conditional information offered is the default risk filtering behavior, which is a parameter effect rather than a use-case rule.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_skillGet skill profileARead-onlyIdempotentInspect
Full quality profile for one tool by slug (slugs come from search_skills / get_collection): score breakdown, structural signals, risk level and reasons, platforms, repo link. Direct lookups return any active tool regardless of risk — the risk assessment is part of the answer, not a filter here.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| name | Yes | |
| slug | Yes | |
| tier | Yes | |
| type | Yes | |
| forks | Yes | |
| stars | Yes | |
| scores | Yes | |
| license | Yes | |
| category | Yes | |
| repo_url | Yes | |
| platforms | Yes | |
| risk_level | Yes | |
| updated_at | Yes | |
| description | Yes | |
| is_official | Yes | |
| profile_url | Yes | |
| risk_reasons | Yes | |
| verification | Yes | |
| discovered_at | Yes | |
| quality_score | Yes | |
| readme_length | Yes | |
| release_count | Yes | |
| last_commit_at | Yes | |
| composite_score | Yes | |
| latest_release_at | Yes | |
| structural_signals | Yes |
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond them: the tool returns any active tool regardless of risk, and risk is presented as answer content rather than a filter.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences: the first front-loads what the tool returns, the second resolves the risk-filter misconception. Every clause earns its place with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read tool with a full output schema and complete annotations, the description supplies everything else an agent needs, including slug provenance and the risk-inclusion behavior. No gaps remain for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description carries the burden. It compensates by naming the parameter's role ('by slug') and its provenance (search_skills / get_collection), which resolves the main ambiguity, though it does not restate the slug syntax that the schema pattern already enforces.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('full quality profile for one tool by slug') and enumerates the profile contents (score breakdown, structural signals, risk level, platforms, repo link). The parenthetical naming search_skills / get_collection as slug sources cleanly disambiguates it from the sibling list tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explains how to obtain the required input ('slugs come from search_skills / get_collection') and clarifies the lookup is direct and unrestricted by risk. It stops short of an explicit when-to-use-this-vs-compare_tools statement, but the single-tool scope is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_collectionsList collectionsARead-onlyIdempotentInspect
The curated buyer-intent collections (e.g. mcp-servers, testing-qa, browser-automation). Use get_collection for the ranked tools inside one.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| collections | Yes |
TDQS
A4.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile: readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds context that the collections are curated and buyer-intent oriented, but does not describe return shape, ordering, or pagination behavior. Since the annotations carry the behavioral burden, a middle score is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no filler. It front-loads the core subject, provides concrete examples, and immediately routes to the relevant sibling tool. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only list operation with a full output schema and robust annotations, the description is complete. It indicates what is returned, gives representative values, and distinguishes this tool from the closely related sibling. Nothing material is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters)Skip; with no parameters and 100% schema coverage, the description need not explain parameter behavior. It still adds value by naming example collections, which helps an agent understand the domain, so a 4 is reasonable.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The title and description together clearly identify the tool as listing curated buyer-intent collections, with concrete examples of what those collections are. It explicitly distinguishes itself from get_collection, which returns the ranked tools inside a single collection, so an agent can tell them apart immediately.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear routing by saying to use get_collection when the agent needs the ranked tools inside a specific collection. It implies the proper use case for this tool, though it does not enumerate exclusions beyond that one sibling. This is adequate but not exhaustive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_skillsSearch skillsARead-onlyIdempotentInspect
Full-text search over the Skill of Skills directory (AI coding skills, plugins, MCP servers across Claude Code, Cursor, Codex, Windsurf, Cline). Results are ranked by the quality-first composite score, not popularity; when no tool matches every term, the closest partial matches are returned instead (match_mode: "any"), most relevant first. Critical-risk tools are excluded by default (risk_filter); every result carries risk_level and risk_reasons. Scores are evidence, not endorsements.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes | What capability you need, e.g. "postgres migrations" | |
| min_tier | No | Quality floor: curated ≥120, promising ≥80, experimental ≥40 | experimental |
| platform | No | Restrict to one client platform | |
| verified | No | Current Verified Working result: runs only, or any verified tier | |
| risk_filter | No | Risk gate: exclude_critical omits critical risk (default); exclude_high omits high and critical risk; none omits no risk levels | exclude_critical |
| include_high_risk | No | Deprecated alias for risk_filter=none |
Output Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| query | Yes | |
| results | Yes | |
| match_mode | Yes |
TDQS
A3.9/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds substantive context: ranking is by a quality-first composite score rather than popularity, partial-match fallback uses match_mode "any", critical-risk tools are excluded by default, and every result carries risk_level/risk_reasons. It does not explain pagination or result ordering beyond relevance, but the ranking semantics disclosure is genuinely beyond what the annotations provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three dense sentences with the resource, ranking model, and risk behavior front-loaded before the disclaimer. "Scores are evidence, not endorsements" earns its place by telling the agent how to interpret results, though the match_mode aside is slightly parenthetical.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-value explanation is not required, and the description still covers ranking, partial-match fallback, risk gating, and per-result risk fields. The one gap is that no cue is given about result limits or result-set size behavior, but for a 7-param search tool this is close to complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 86% and four parameters have enums, so the schema already carries the parameter burden — baseline 3. The description restates the risk_filter default ("Critical-risk tools are excluded by default") which the schema already documents, and adds nothing about min_tier, platform, or verified semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The first sentence names a specific verb and resource ("Full-text search over the Skill of Skills directory") and enumerates the corpus (AI coding skills, plugins, MCP servers). This scopes it clearly against siblings like get_skill (single lookup) and list_collections without needing to name them explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied — search is self-evidently for discovery — and no alternative tool is ever named (e.g., use get_skill once you have an identifier, or compare_tools for head-to-head evaluation). The fallback behavior ("when no tool matches every term, the closest partial matches are returned") describes mechanics rather than when-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
4 tool updates
- Changed
compare_tools2 fields changed- added
Output schema / properties / compared / items / properties / verificationAdded value: +{ + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "commit_sha": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "failing_check": { + "additionalProperties": false, + "properties": { + "id": { + "type": "string" + }, + "path": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "id", + "path" + ], + "type": "object" + }, + "stale": { + "type": "boolean" + }, + "status": { + "type": "string" + }, + "tier": { + "anyOf": [ + { + "enum": [ + "runs", + "loads-clean" + ], + "type": "string" + }, + { + "type": "null" + } + ] + }, + "verified_at": { + "type": "string" + } + }, + "required": [ + "status", + "tier", + "commit_sha", + "verified_at", + "stale" + ], + "type": "object" + }, + { + "type": "null" + } + ] +} - changed
Output schema / properties / compared / items / requiredPrevious value: -[ - "name", - "slug", - "tier", - "quality_score", - "composite_score", - "risk_level", - "risk_reasons", - "type", - "category", - "platforms", - "description", - "repo_url", - "profile_url", - "stars", - "is_official", - "last_commit_at", - "license", - "forks", - "scores", - "structural_signals", - "readme_length", - "release_count", - "latest_release_at", - "discovered_at", - "updated_at" -]New value: +[ + "name", + "slug", + "tier", + "quality_score", + "composite_score", + "risk_level", + "risk_reasons", + "type", + "category", + "platforms", + "description", + "repo_url", + "profile_url", + "stars", + "is_official", + "last_commit_at", + "verification", + "license", + "forks", + "scores", + "structural_signals", + "readme_length", + "release_count", + "latest_release_at", + "discovered_at", + "updated_at" +]
- Changed
get_collection2 fields changed- added
Output schema / properties / results / items / properties / verificationAdded value: +{ + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "commit_sha": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "failing_check": { + "additionalProperties": false, + "properties": { + "id": { + "type": "string" + }, + "path": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "id", + "path" + ], + "type": "object" + }, + "stale": { + "type": "boolean" + }, + "status": { + "type": "string" + }, + "tier": { + "anyOf": [ + { + "enum": [ + "runs", + "loads-clean" + ], + "type": "string" + }, + { + "type": "null" + } + ] + }, + "verified_at": { + "type": "string" + } + }, + "required": [ + "status", + "tier", + "commit_sha", + "verified_at", + "stale" + ], + "type": "object" + }, + { + "type": "null" + } + ] +} - changed
Output schema / properties / results / items / requiredPrevious value: -[ - "name", - "slug", - "tier", - "quality_score", - "composite_score", - "risk_level", - "risk_reasons", - "type", - "category", - "platforms", - "description", - "repo_url", - "profile_url", - "stars", - "is_official", - "last_commit_at" -]New value: +[ + "name", + "slug", + "tier", + "quality_score", + "composite_score", + "risk_level", + "risk_reasons", + "type", + "category", + "platforms", + "description", + "repo_url", + "profile_url", + "stars", + "is_official", + "last_commit_at", + "verification" +]
- Changed
get_skill2 fields changed- added
Output schema / properties / verificationAdded value: +{ + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "commit_sha": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "failing_check": { + "additionalProperties": false, + "properties": { + "id": { + "type": "string" + }, + "path": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "id", + "path" + ], + "type": "object" + }, + "stale": { + "type": "boolean" + }, + "status": { + "type": "string" + }, + "tier": { + "anyOf": [ + { + "enum": [ + "runs", + "loads-clean" + ], + "type": "string" + }, + { + "type": "null" + } + ] + }, + "verified_at": { + "type": "string" + } + }, + "required": [ + "status", + "tier", + "commit_sha", + "verified_at", + "stale" + ], + "type": "object" + }, + { + "type": "null" + } + ] +} - changed
Output schema / requiredPrevious value: -[ - "name", - "slug", - "tier", - "quality_score", - "composite_score", - "risk_level", - "risk_reasons", - "type", - "category", - "platforms", - "description", - "repo_url", - "profile_url", - "stars", - "is_official", - "last_commit_at", - "license", - "forks", - "scores", - "structural_signals", - "readme_length", - "release_count", - "latest_release_at", - "discovered_at", - "updated_at" -]New value: +[ + "name", + "slug", + "tier", + "quality_score", + "composite_score", + "risk_level", + "risk_reasons", + "type", + "category", + "platforms", + "description", + "repo_url", + "profile_url", + "stars", + "is_official", + "last_commit_at", + "verification", + "license", + "forks", + "scores", + "structural_signals", + "readme_length", + "release_count", + "latest_release_at", + "discovered_at", + "updated_at" +]
- Changed
search_skills3 fields changed- added
Input schema / properties / verifiedAdded value: +{ + "description": "Current Verified Working result: runs only, or any verified tier", + "enum": [ + "runs", + "any" + ], + "type": "string" +} - added
Output schema / properties / results / items / properties / verificationAdded value: +{ + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "commit_sha": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "failing_check": { + "additionalProperties": false, + "properties": { + "id": { + "type": "string" + }, + "path": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "id", + "path" + ], + "type": "object" + }, + "stale": { + "type": "boolean" + }, + "status": { + "type": "string" + }, + "tier": { + "anyOf": [ + { + "enum": [ + "runs", + "loads-clean" + ], + "type": "string" + }, + { + "type": "null" + } + ] + }, + "verified_at": { + "type": "string" + } + }, + "required": [ + "status", + "tier", + "commit_sha", + "verified_at", + "stale" + ], + "type": "object" + }, + { + "type": "null" + } + ] +} - changed
Output schema / properties / results / items / requiredPrevious value: -[ - "name", - "slug", - "tier", - "quality_score", - "composite_score", - "risk_level", - "risk_reasons", - "type", - "category", - "platforms", - "description", - "repo_url", - "profile_url", - "stars", - "is_official", - "last_commit_at" -]New value: +[ + "name", + "slug", + "tier", + "quality_score", + "composite_score", + "risk_level", + "risk_reasons", + "type", + "category", + "platforms", + "description", + "repo_url", + "profile_url", + "stars", + "is_official", + "last_commit_at", + "verification" +]
6 tool updates
- Changed
compare_tools2 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "compared": { + "items": { + "additionalProperties": false, + "properties": { + "category": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "composite_score": { + "type": "number" + }, + "description": { + "type": "string" + }, + "discovered_at": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "forks": { + "type": "number" + }, + "is_official": { + "type": "boolean" + }, + "last_commit_at": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "latest_release_at": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "license": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "type": "string" + }, + "platforms": { + "items": { + "type": "string" + }, + "type": "array" + }, + "profile_url": { + "type": "string" + }, + "quality_score": { + "type": "number" + }, + "readme_length": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "release_count": { + "type": "number" + }, + "repo_url": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "risk_level": { + "type": "string" + }, + "risk_reasons": { + "items": { + "type": "string" + }, + "type": "array" + }, + "scores": { + "additionalProperties": false, + "properties": { + "composite": { + "type": "number" + }, + "github": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "quality": { + "type": "number" + }, + "recency": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "social": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "star_velocity_30d": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "trending": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "quality", + "composite", + "github", + "social", + "recency", + "trending", + "star_velocity_30d" + ], + "type": "object" + }, + "slug": { + "type": "string" + }, + "stars": { + "type": "number" + }, + "structural_signals": { + "additionalProperties": false, + "properties": { + "config_files": { + "type": "boolean" + }, + "examples": { + "type": "boolean" + }, + "gotchas": { + "type": "boolean" + }, + "progressive_disclosure": { + "type": "boolean" + }, + "scripts": { + "type": "boolean" + }, + "skill_md": { + "type": "boolean" + }, + "verification": { + "type": "boolean" + } + }, + "required": [ + "skill_md", + "examples", + "gotchas", + "verification", + "scripts", + "progressive_disclosure", + "config_files" + ], + "type": "object" + }, + "tier": { + "enum": [ + "curated", + "promising", + "experimental", + "review_required" + ], + "type": "string" + }, + "type": { + "type": "string" + }, + "updated_at": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "name", + "slug", + "tier", + "quality_score", + "composite_score", + "risk_level", + "risk_reasons", + "type", + "category", + "platforms", + "description", + "repo_url", + "profile_url", + "stars", + "is_official", + "last_commit_at", + "license", + "forks", + "scores", + "structural_signals", + "readme_length", + "release_count", + "latest_release_at", + "discovered_at", + "updated_at" + ], + "type": "object" + }, + "type": "array" + }, + "not_found": { + "items": { + "type": "string" + }, + "type": "array" + } + }, + "required": [ + "compared" + ], + "type": "object" +}
- Changed
demand_pulse2 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "most_installed": { + "items": { + "additionalProperties": false, + "properties": { + "category": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "type": "string" + }, + "sessions": { + "type": "number" + }, + "slug": { + "type": "string" + } + }, + "required": [ + "name", + "slug", + "category", + "sessions" + ], + "type": "object" + }, + "type": "array" + }, + "most_saved": { + "items": { + "additionalProperties": false, + "properties": { + "category": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "type": "string" + }, + "sessions": { + "type": "number" + }, + "slug": { + "type": "string" + } + }, + "required": [ + "name", + "slug", + "category", + "sessions" + ], + "type": "object" + }, + "type": "array" + }, + "total_interactions": { + "type": "number" + }, + "trending_searches": { + "items": { + "additionalProperties": false, + "properties": { + "query": { + "type": "string" + }, + "sessions": { + "type": "number" + } + }, + "required": [ + "query", + "sessions" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "total_interactions", + "trending_searches", + "most_saved", + "most_installed" + ], + "type": "object" +}
- Changed
get_collection2 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "collection": { + "additionalProperties": false, + "properties": { + "slug": { + "type": "string" + }, + "tagline": { + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "slug", + "title", + "tagline" + ], + "type": "object" + }, + "count": { + "type": "number" + }, + "results": { + "items": { + "additionalProperties": false, + "properties": { + "category": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "composite_score": { + "type": "number" + }, + "description": { + "type": "string" + }, + "is_official": { + "type": "boolean" + }, + "last_commit_at": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "type": "string" + }, + "platforms": { + "items": { + "type": "string" + }, + "type": "array" + }, + "profile_url": { + "type": "string" + }, + "quality_score": { + "type": "number" + }, + "repo_url": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "risk_level": { + "type": "string" + }, + "risk_reasons": { + "items": { + "type": "string" + }, + "type": "array" + }, + "slug": { + "type": "string" + }, + "stars": { + "type": "number" + }, + "tier": { + "enum": [ + "curated", + "promising", + "experimental", + "review_required" + ], + "type": "string" + }, + "type": { + "type": "string" + } + }, + "required": [ + "name", + "slug", + "tier", + "quality_score", + "composite_score", + "risk_level", + "risk_reasons", + "type", + "category", + "platforms", + "description", + "repo_url", + "profile_url", + "stars", + "is_official", + "last_commit_at" + ], + "type": "object" + }, + "type": "array" + }, + "total_in_collection": { + "type": "number" + } + }, + "required": [ + "collection", + "total_in_collection", + "count", + "results" + ], + "type": "object" +}
- Changed
get_skill2 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "category": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "composite_score": { + "type": "number" + }, + "description": { + "type": "string" + }, + "discovered_at": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "forks": { + "type": "number" + }, + "is_official": { + "type": "boolean" + }, + "last_commit_at": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "latest_release_at": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "license": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "type": "string" + }, + "platforms": { + "items": { + "type": "string" + }, + "type": "array" + }, + "profile_url": { + "type": "string" + }, + "quality_score": { + "type": "number" + }, + "readme_length": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "release_count": { + "type": "number" + }, + "repo_url": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "risk_level": { + "type": "string" + }, + "risk_reasons": { + "items": { + "type": "string" + }, + "type": "array" + }, + "scores": { + "additionalProperties": false, + "properties": { + "composite": { + "type": "number" + }, + "github": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "quality": { + "type": "number" + }, + "recency": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "social": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "star_velocity_30d": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "trending": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "quality", + "composite", + "github", + "social", + "recency", + "trending", + "star_velocity_30d" + ], + "type": "object" + }, + "slug": { + "type": "string" + }, + "stars": { + "type": "number" + }, + "structural_signals": { + "additionalProperties": false, + "properties": { + "config_files": { + "type": "boolean" + }, + "examples": { + "type": "boolean" + }, + "gotchas": { + "type": "boolean" + }, + "progressive_disclosure": { + "type": "boolean" + }, + "scripts": { + "type": "boolean" + }, + "skill_md": { + "type": "boolean" + }, + "verification": { + "type": "boolean" + } + }, + "required": [ + "skill_md", + "examples", + "gotchas", + "verification", + "scripts", + "progressive_disclosure", + "config_files" + ], + "type": "object" + }, + "tier": { + "enum": [ + "curated", + "promising", + "experimental", + "review_required" + ], + "type": "string" + }, + "type": { + "type": "string" + }, + "updated_at": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "name", + "slug", + "tier", + "quality_score", + "composite_score", + "risk_level", + "risk_reasons", + "type", + "category", + "platforms", + "description", + "repo_url", + "profile_url", + "stars", + "is_official", + "last_commit_at", + "license", + "forks", + "scores", + "structural_signals", + "readme_length", + "release_count", + "latest_release_at", + "discovered_at", + "updated_at" + ], + "type": "object" +}
- Changed
list_collections2 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "collections": { + "items": { + "additionalProperties": false, + "properties": { + "slug": { + "type": "string" + }, + "tagline": { + "type": "string" + }, + "title": { + "type": "string" + }, + "url": { + "type": "string" + } + }, + "required": [ + "slug", + "title", + "tagline", + "url" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "collections" + ], + "type": "object" +}
- Changed
search_skills2 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "count": { + "type": "number" + }, + "match_mode": { + "enum": [ + "all", + "any" + ], + "type": "string" + }, + "query": { + "type": "string" + }, + "results": { + "items": { + "additionalProperties": false, + "properties": { + "category": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "composite_score": { + "type": "number" + }, + "description": { + "type": "string" + }, + "is_official": { + "type": "boolean" + }, + "last_commit_at": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "type": "string" + }, + "platforms": { + "items": { + "type": "string" + }, + "type": "array" + }, + "profile_url": { + "type": "string" + }, + "quality_score": { + "type": "number" + }, + "repo_url": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "risk_level": { + "type": "string" + }, + "risk_reasons": { + "items": { + "type": "string" + }, + "type": "array" + }, + "slug": { + "type": "string" + }, + "stars": { + "type": "number" + }, + "tier": { + "enum": [ + "curated", + "promising", + "experimental", + "review_required" + ], + "type": "string" + }, + "type": { + "type": "string" + } + }, + "required": [ + "name", + "slug", + "tier", + "quality_score", + "composite_score", + "risk_level", + "risk_reasons", + "type", + "category", + "platforms", + "description", + "repo_url", + "profile_url", + "stars", + "is_official", + "last_commit_at" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "query", + "count", + "match_mode", + "results" + ], + "type": "object" +}
2 tool updates
- Changed
get_collection3 fields changed- removed
Input schema / properties / include_high_risk / defaultRemoved value: -false - added
Input schema / properties / include_high_risk / descriptionAdded value: +"Deprecated alias for risk_filter=none" - added
Input schema / properties / risk_filterAdded value: +{ + "default": "exclude_critical", + "description": "Risk gate: exclude_critical omits critical risk (default); exclude_high omits high and critical risk; none omits no risk levels", + "enum": [ + "exclude_critical", + "exclude_high", + "none" + ], + "type": "string" +}
- Changed
search_skills3 fields changed- removed
Input schema / properties / include_high_risk / defaultRemoved value: -false - changed
Input schema / properties / include_high_risk / descriptionPrevious value: -"Also return tools assessed high/critical risk (off by default)"New value: +"Deprecated alias for risk_filter=none" - added
Input schema / properties / risk_filterAdded value: +{ + "default": "exclude_critical", + "description": "Risk gate: exclude_critical omits critical risk (default); exclude_high omits high and critical risk; none omits no risk levels", + "enum": [ + "exclude_critical", + "exclude_high", + "none" + ], + "type": "string" +}
6 tool updates
- First observed
compare_tools - First observed
demand_pulse - First observed
get_collection - First observed
get_skill - First observed
list_collections - First observed
search_skills
Related MCP Connectors
AI tool directory MCP server, live since July 2026. Tools, agents, models, companies, services.
Find MCP servers, skills, plugins, agents, prompts and rules for any task.
Capability registry for the agentic economy. Semantic search over verified MCP server listings.
Find, compare, and audit software for AI agents. Scored registry of tools and MCP servers.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to search a directory of 13,870+ MCP servers, 4,384+ agent skills, and plugins from Remote OpenClaw, returning install commands directly.321 npm6MIT
- AlicenseNot gradedqualityDmaintenanceA powerful MCP server that brings the skills.sh ecosystem directly to your AI agents, enabling effortless discovery, installation, and management of skills.1MIT
- AlicenseAqualityDmaintenanceMCP server for discovering and installing AI agent skills from Loaditout. Search 20,000+ security-gradedMCP servers, check A/B/C/F grades, get install configs, and browse trending skills and curated packs.2113 npm1MIT
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd
Glama MCP Gateway
Add one secure layer between your agents and this server.