Loading ToolBench

Reading the current corpus…

mpak MCP server · C · ToolBench

← Browse

mpak

github.com/NimbleBrainInc/mpak

MCP bundle registry server - provides bundle and MCP server registry API with security scanning and certification

2026-07-28+STREAMABLE_HTTP5 tools

61/100

Definition Quality62

Protocol Readiness78

Supportability49

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · detected: Dynamic Client Registration

Deprecated protocol patterns detected

Summary

mpak Registry Server provides 5 read-only tools for MCP server discovery and version management. All tools have clear action-verb names and substantive descriptions (90-180 chars). Input parameters are typed with JSON Schema and have descriptions. Output schemas are not explicitly documented in the source provided. Tool composition is clean, each performs one clear function. Parameter descriptions adequately explain constraints (e.g., 'Case-insensitive substring search', 'RFC 3339 timestamp'). No security red flags detected (all tools are read-only, no credentials in params). Main gaps: (1) output schemas not documented in the provided source, (2) no error handling guidance visible, (3) no examples of recovery paths when searches fail.

Tools (5)

getServerread only50/100

Get a specific MCP server by name (supports both npm-style scoped names and reverse-DNS form)

getServerVersionread only50/100

Get a specific version of an MCP server

listServerVersionsread only50/100

List all versions of a specific MCP server

listServersread only50/100

List MCP servers (each entry is a ServerDetail per the upstream MCP registry spec). Each item is the latest published version of a server; per-version listings live under /servers/{name}/versions.

searchServersread only50/100

Search MCP servers with advanced filtering options

Issues (5)

HIGHresponse-shaper ↗

Output schemas not documented in tool definitions. LLMs cannot plan downstream operations or extract required fields (e.g., does listServers return server IDs, manifest URLs, version info?) without explicit response schemas.

listServerssearchServersgetServergetServerVersionlistServerVersions

HIGHtool-description ↗

searchServers has a minimal description ('Search MCP servers with advanced filtering options') and only a 'query' parameter with generic description ('Search query string'). No indication of what fields are searched, filter syntax, or expected result format.

searchServers

HIGHrecovery-guide ↗

No error handling guidance visible. What happens if a server name is not found? Are pagination cursors validated? Do invalid RFC 3339 timestamps return a recovery hint? Agents need explicit error messages and recovery paths.

listServersgetServergetServerVersionlistServerVersions

Recommendations

Add explicit output schemas to all tool definitions. For listServers, document that it returns an array of ServerDetail objects with fields: name, displayName, description, latestVersion, publishedAt, etc. For searchServers, clarify which fields are searched and document result structure.
Expand searchServers description from 47 chars to 150 - 200 chars. Explain: (1) Which fields are searched (name, displayName, description, tags)? (2) Is it case-insensitive? (3) What is returned, ServerDetail summaries or full specs? (4) When to use searchServers vs listServers.
Document error cases explicitly. Add to tool descriptions: 'Returns 404 if server name not found. Try listServers() or searchServers() to discover available servers.' This guides LLM recovery.
Clarify pagination in listServers. Specify: (1) Is cursor an offset string or opaque token? (2) What is the initial cursor (empty string, '0')? (3) What indicates the final page (empty cursor in response)? (4) What happens if cursor is invalid?
Add examples to the name parameter in getServer: 'Accepts npm-style names like @ai/echo or reverse-DNS like ai.nimblebrain/echo. Both refer to the same server.'
Add per-tool result count limits. Document: 'listServers returns up to 500 items per page (limit param max 500). Large result sets waste context; paginate through results.' This sets expectations and prevents token bloat.
Document the relationship between listServerVersions and getServerVersion. Clarify: 'Call listServerVersions(name) to see all available versions, then getServerVersion(name, version) to fetch a specific version's full spec.'

Score history

Overall score trend

↑ 17 points across a rubric change (v1 → v2)

61/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-22	C	61	2026-07-28+	v2
2026-03-09	F	44	-	v1