{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-toolspeccore","slug":"npm-toolspeccore","name":"@toolspec/core","type":"mcp","url":"https://www.npmjs.com/package/@toolspec/core","page_url":"https://unfragile.ai/npm-toolspeccore","categories":["mcp-servers","testing-quality"],"tags":["mcp","model-context-protocol","linting","tool-schema","validation","quality"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-toolspeccore__cap_0","uri":"capability://tool.use.integration.mcp.tool.schema.validation.and.linting","name":"mcp tool schema validation and linting","description":"Validates MCP (Model Context Protocol) tool schema definitions against specification compliance rules, parsing JSON/YAML tool definitions and checking for structural correctness, required fields, type safety, and protocol adherence. Uses a rule-based linting engine that applies configurable validators to catch schema violations before tools are deployed to MCP servers.","intents":["I need to validate that my MCP tool schema conforms to the Model Context Protocol specification before publishing","I want to catch schema errors early in development rather than discovering them at runtime when tools fail to load","I need to enforce consistent schema patterns across multiple tools in my MCP server implementation"],"best_for":["MCP server developers building tool integrations","teams standardizing tool definitions across multiple MCP implementations","CI/CD pipelines validating tool schemas before deployment"],"limitations":["Linting rules are static and cannot validate runtime behavior or actual tool functionality","Does not validate tool implementations themselves, only schema structure and metadata","Limited to MCP protocol specification — cannot validate custom extensions or proprietary tool attributes"],"requires":["Node.js 14+","Valid MCP tool schema in JSON or YAML format","@toolspec/core package installed via npm"],"input_types":["JSON","YAML","MCP tool schema objects"],"output_types":["validation report (structured)","linting errors/warnings (structured)","compliance status (boolean/enum)"],"categories":["tool-use-integration","testing-quality"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-toolspeccore__cap_1","uri":"capability://data.processing.analysis.tool.schema.quality.scoring.and.metrics","name":"tool schema quality scoring and metrics","description":"Analyzes MCP tool schemas and assigns quality scores based on completeness, documentation, type safety, and best-practice adherence. Implements a multi-dimensional scoring system that evaluates schema metadata (descriptions, examples, parameter types) and generates actionable quality metrics to guide schema improvements.","intents":["I want to measure the quality and completeness of my tool schemas to identify gaps in documentation or type safety","I need to compare quality across multiple tools to prioritize which schemas need improvement","I want to enforce minimum quality standards for tools before they're added to our MCP server"],"best_for":["MCP tool developers iterating on schema quality","teams establishing tool quality standards and governance","organizations managing large tool catalogs requiring quality gates"],"limitations":["Quality scoring is heuristic-based and may not capture domain-specific quality requirements","Does not evaluate tool usefulness or user adoption — only schema characteristics","Scoring weights are fixed and cannot be customized per organization or use case"],"requires":["Node.js 14+","Valid MCP tool schema definition","@toolspec/core package installed"],"input_types":["MCP tool schema objects","JSON tool definitions","YAML tool definitions"],"output_types":["quality score (numeric)","dimension breakdown (structured metrics)","improvement recommendations (text)"],"categories":["data-processing-analysis","testing-quality"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-toolspeccore__cap_2","uri":"capability://tool.use.integration.configurable.linting.rule.engine.with.custom.rule.support","name":"configurable linting rule engine with custom rule support","description":"Provides an extensible rule-based linting framework where developers can define, configure, and compose custom validation rules for MCP tool schemas. Rules are applied as a pipeline with support for rule severity levels (error/warning/info), conditional rule application, and rule composition patterns.","intents":["I want to define custom validation rules specific to my organization's tool schema standards","I need to enforce different rule sets for different tool categories or use cases","I want to gradually enforce new schema standards by starting with warnings before promoting to errors"],"best_for":["organizations with custom tool schema governance requirements","teams building internal MCP tool ecosystems with specific standards","developers extending @toolspec/core with domain-specific validation logic"],"limitations":["Custom rule development requires understanding the rule API and schema structure","Rule composition complexity increases with number of custom rules — potential performance impact on large schemas","No built-in rule versioning or migration path when rule definitions change"],"requires":["Node.js 14+","Understanding of MCP tool schema structure","@toolspec/core package with rule API documentation","TypeScript or JavaScript for custom rule implementation"],"input_types":["rule definitions (code/config)","MCP tool schemas","rule configuration objects"],"output_types":["validation results with rule metadata","rule execution reports","severity-categorized findings"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-toolspeccore__cap_3","uri":"capability://automation.workflow.batch.schema.validation.with.reporting","name":"batch schema validation with reporting","description":"Processes multiple MCP tool schemas in batch mode, applying validation and quality scoring across an entire tool catalog or directory structure. Generates consolidated validation reports with aggregated metrics, failure summaries, and per-tool details, supporting both CLI and programmatic interfaces.","intents":["I need to validate all 50+ tools in my MCP server at once to identify which ones have schema issues","I want to generate a compliance report showing which tools meet our quality standards","I need to integrate schema validation into my CI/CD pipeline to block tool deployments with schema errors"],"best_for":["teams managing large MCP tool catalogs (10+ tools)","CI/CD pipelines requiring automated schema validation gates","organizations conducting tool audits or compliance reviews"],"limitations":["Batch processing performance degrades with very large tool catalogs (1000+ tools) without optimization","Report generation is synchronous — no streaming or incremental reporting for long-running validations","Memory usage scales with number of tools being validated simultaneously"],"requires":["Node.js 14+","@toolspec/core package installed","Tool schema files in accessible directory or programmatic schema objects","Sufficient memory for batch processing (varies with tool count)"],"input_types":["directory paths containing tool schemas","arrays of tool schema objects","file globs or patterns"],"output_types":["validation report (JSON/text)","aggregated metrics (structured)","per-tool results (structured)","summary statistics"],"categories":["automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-toolspeccore__cap_4","uri":"capability://text.generation.language.schema.documentation.extraction.and.generation","name":"schema documentation extraction and generation","description":"Extracts structured documentation metadata from MCP tool schemas (descriptions, parameter documentation, examples, usage patterns) and generates human-readable documentation or schema reference guides. Supports multiple output formats and can identify missing or incomplete documentation.","intents":["I want to auto-generate documentation for my MCP tools from their schema definitions","I need to identify which tools are missing documentation or have incomplete parameter descriptions","I want to generate a reference guide showing all available tools and their capabilities"],"best_for":["MCP tool developers documenting tool catalogs","teams maintaining tool reference documentation","organizations generating API documentation from tool schemas"],"limitations":["Documentation quality depends entirely on schema metadata completeness — cannot infer missing documentation","Generated documentation requires manual review and enhancement for production use","Limited to documentation present in schema — cannot extract runtime behavior or implementation details"],"requires":["Node.js 14+","@toolspec/core package installed","Well-documented MCP tool schemas with descriptions and examples"],"input_types":["MCP tool schema objects","JSON/YAML tool definitions"],"output_types":["Markdown documentation","HTML reference pages","JSON documentation objects","text summaries"],"categories":["text-generation-language","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-toolspeccore__cap_5","uri":"capability://tool.use.integration.type.safety.and.parameter.validation.rules","name":"type safety and parameter validation rules","description":"Analyzes tool schema parameter definitions to enforce type safety, validate parameter constraints (required/optional, min/max values, enum values), and detect type mismatches or unsafe patterns. Checks for proper type declarations, constraint definitions, and compatibility with MCP protocol type system.","intents":["I want to ensure all my tool parameters are properly typed and have appropriate constraints defined","I need to catch type mismatches or unsafe parameter definitions before tools are deployed","I want to enforce consistent parameter naming and type conventions across all tools"],"best_for":["MCP tool developers building type-safe tool integrations","teams enforcing strict type safety standards for tool schemas","organizations preventing runtime errors from type mismatches"],"limitations":["Type validation is schema-level only — does not validate actual runtime type behavior","Cannot detect type mismatches between schema declarations and actual tool implementations","Limited to MCP protocol type system — cannot validate custom or extended types"],"requires":["Node.js 14+","@toolspec/core package installed","MCP tool schemas with parameter type definitions"],"input_types":["MCP tool schema objects","parameter definitions (structured)"],"output_types":["type validation results","constraint violation reports","type safety recommendations"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":28,"verified":false,"data_access_risk":"high","permissions":["Node.js 14+","Valid MCP tool schema in JSON or YAML format","@toolspec/core package installed via npm","Valid MCP tool schema definition","@toolspec/core package installed","Understanding of MCP tool schema structure","@toolspec/core package with rule API documentation","TypeScript or JavaScript for custom rule implementation","Tool schema files in accessible directory or programmatic schema objects","Sufficient memory for batch processing (varies with tool count)"],"failure_modes":["Linting rules are static and cannot validate runtime behavior or actual tool functionality","Does not validate tool implementations themselves, only schema structure and metadata","Limited to MCP protocol specification — cannot validate custom extensions or proprietary tool attributes","Quality scoring is heuristic-based and may not capture domain-specific quality requirements","Does not evaluate tool usefulness or user adoption — only schema characteristics","Scoring weights are fixed and cannot be customized per organization or use case","Custom rule development requires understanding the rule API and schema structure","Rule composition complexity increases with number of custom rules — potential performance impact on large schemas","No built-in rule versioning or migration path when rule definitions change","Batch processing performance degrades with very large tool catalogs (1000+ tools) without optimization","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.22,"ecosystem":0.5800000000000001,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:24.483Z","last_scraped_at":"2026-04-22T08:11:36.936Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-toolspeccore","compare_url":"https://unfragile.ai/compare?artifact=npm-toolspeccore"}},"signature":"Gads+kUvkf38ho4FJvvmiEjHL5uoEtpd+NPceyYDT+iFNzYxCXePVyLk+0wHfBy4Kg00VJParwvGGmppIAJOBA==","signedAt":"2026-06-22T00:12:44.478Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-toolspeccore","artifact":"https://unfragile.ai/npm-toolspeccore","verify":"https://unfragile.ai/api/v1/verify?slug=npm-toolspeccore","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}