{"id":"stacklok-toolhive-catalog","name":"toolhive-catalog","homepage":null,"repo_url":"https://github.com/stacklok/toolhive-catalog","category":"devtools","subcategories":[],"tags":["mcp","model-context-protocol","registry","catalog","tooling","automation"],"what_it_does":"toolhive-catalog is a registry/catalog repository for listing Model Context Protocol (MCP) servers and reusable skills/workflows. It defines a directory structure and JSON/YAML schemas (e.g., server.json and SKILL.md) for contributors to add container-based (Docker/OCI) or remote (HTTP/HTTPS) MCP server endpoints and skill definitions.","use_cases":["Discovering and reusing MCP server capabilities via a standardized registry format","Publishing MCP server metadata (tools list, tiers/status, container image identifiers, remote endpoints) for downstream ToolHive usage","Sharing prompt/workflow “skills” that reference specific server tools"],"not_for":["Running an MCP server itself (it is a catalog/registry, not an execution service)","Providing a production API for querying the registry at runtime (no such API is described)"],"best_when":"You want to standardize how MCP servers and skills are described so an orchestrator (ToolHive) can integrate them consistently.","avoid_when":"You need a direct REST/GraphQL/SDK interface from this repo to call tools; you should use the MCP servers/skills that it references instead.","alternatives":["Other MCP registry/catalog approaches (community-maintained lists)","Direct integration to individual MCP servers (without a centralized registry)"],"af_score":37.2,"security_score":41.8,"reliability_score":15.0,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:34:57.728146+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Registry entry publishing (via Git workflows implied, not specified as an API auth mechanism)","MCP server authentication is described only as an example in server.json environmentVariables (e.g., API_KEY isRequired/isSecret) but no concrete auth flow is provided here"],"oauth":false,"scopes":false,"notes":"This repository does not implement runtime authentication. It provides metadata fields where MCP server auth details may be documented for downstream users."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information is provided; it is a code/catalog repository."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":37.2,"security_score":41.8,"reliability_score":15.0,"mcp_server_quality":35.0,"documentation_accuracy":75.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":80.0,"rate_limit_clarity":0.0,"tls_enforcement":40.0,"auth_strength":45.0,"scope_granularity":35.0,"dependency_hygiene":30.0,"secret_handling":55.0,"security_notes":"Catalog entries include guidance to avoid filesystem mounts (network permissions only) and to mark environment variables as secrets in server.json examples. However, this repo does not itself implement TLS enforcement, auth flows, or secret storage—those concerns apply to the referenced MCP servers and user/runtime configuration. No evidence of security controls like signature verification, dependency scanning, or hardened validation is provided in the README excerpt.","uptime_documented":0.0,"version_stability":30.0,"breaking_changes_history":20.0,"error_recovery":10.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["This is a registry/catalog; there is no described programmatic runtime interface for agents to call.","Downstream MCP server behavior is not controlled by this catalog; errors/retries/idempotency depend on each referenced MCP server implementation.","Transport and permissions guidance is provided, but the repo does not itself enforce these beyond validation/build steps."]}}