A registry and search service for MCP (Model Context Protocol) servers. Provides API endpoints to search, list, and discover MCP server tools and metadata.
Agentalog exposes 3 read-only tools via HTTP. All tools have basic descriptions (50-80 chars), but parameter descriptions are missing entirely. Input schemas are visible but lack parameter-level descriptions required by the rubric. No output schemas documented. Tools follow verb_noun naming (search_, get_, list_) but lack the depth needed for production LLM agents. Error handling and recovery guidance absent.
Get counts and facets by kind, provenance, category and repository state
Get subregistry in the Official MCP Registry format (v0.1)
Search the MCP server registry by query string, with optional sorting and limit parameters
Parameter descriptions missing entirely. 'q', 'sort', 'limit' in search_listings have no descriptions explaining valid values, constraints, or format. LLMs cannot infer that 'sort' accepts 'stars' or that 'limit' has bounds.
Output schemas not documented. No specification of what search_listings, get_facets, or list_servers return. LLMs cannot plan downstream operations or extract required fields without seeing response structure.
get_facets accepts no parameters but description does not explain what facets are returned or when to call it. Discovery tools must state what structure they reveal.
No error handling or recovery guidance. If search_listings returns no results or an invalid sort parameter is passed, there is no indication of what the LLM should do next.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | 2026-07-28+ | v2 |
Parameter constraints not specified. 'limit' has no documented min/max; 'sort' has no enum of valid values. LLMs will hallucinate invalid values.