Loading ToolBench

Reading the current corpus…

mcphost MCP server · D · ToolBench

← Browse

mcphost

github.com/j0yen/mcphost

One MCP endpoint an agent can join and administer without a human

2026-07-28+STREAMABLE_HTTP8 tools

55/100

Definition Quality52

Protocol Readiness78

Supportability43

Spec posture

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

Static source inference · medium confidence · evidence: Streamable HTTP

Current-spec patterns detected

Summary

mcphost defines 8 tools with HTTP transport and structured schemas. Most tools have descriptions and input schemas with typed parameters. However, descriptions are often terse (10-50 chars), parameter descriptions lack detail on constraints/formats, and output schemas are not documented. Error handling guidance is minimal. Tool naming follows verb_noun convention (publish, remove, test, set, query, export) but some names are generic (host.usage, host.export). No tool annotations (readOnlyHint, destructiveHint) despite clear risk classifications in metadata. Schemas are present but sparse, many parameters lack descriptions or format constraints. This is a solid foundation but falls short of production-grade quality.

Tools (8)

host.exportread onlyauth40/100

Export tenant data as a tar.gz archive

host.registry_publishwriteauth50/100

Publish tenant's server.json to a configured registry API

host.secret_setwriteauthsource verified52/100

Set a secret value for use in tool specifications

host.table.queryread onlyauth50/100

Execute a SELECT query against tenant data tables

host.tool_publishwriteauthsource verified58/100

Publish a tool to the MCP endpoint

host.tool_removedestructiveauthsource verified55/100

Remove a published tool from the MCP endpoint

host.tool_testread onlyauthsource verified60/100

Test a published tool without recording usage or executing dependent steps

Issues (5)

HIGHtool-description ↗

Parameter descriptions are missing or minimal. 'name', 'kind', 'spec', 'sql', 'value' parameters lack format constraints, valid ranges, or usage guidance. LLMs cannot infer whether 'spec' is a JSON object, a string, or a reference.

host.tool_publishhost.tool_removehost.secret_sethost.table.queryhost.registry_publish

HIGHtool-description ↗

Tool descriptions are terse (10-50 chars). 'Publish a tool to the MCP endpoint' and 'Remove a published tool' lack context on when to use them, what happens on success, or what errors to expect. Descriptions should be 50-200 chars with actionable guidance.

host.tool_publishhost.tool_removehost.secret_sethost.usagehost.export

HIGHresponse-shaper ↗

No output schemas documented. Tools return data but LLMs cannot plan downstream calls without knowing response structure. host.usage, host.export, host.table.query lack documented return types.

host.usage

Recommendations

Expand tool descriptions to 80-150 chars. Include WHAT the tool does, WHEN to use it, and what it returns. Example: 'Publish a new tool to the MCP endpoint. Requires a tool name, kind (echo|http|python|chain|wasm), and a spec object with configuration. Returns the published tool's metadata. Use this to register custom tools before testing.'
Add format/constraint descriptions to all parameters. For 'spec' in host.tool_publish, document: 'A JSON object containing tool configuration. Must include required fields for the specified kind (e.g., url for http, source for python). See kind-specific schema docs.'
Document output schemas for all tools. For host.table.query, specify: 'Returns {rows: [{col1: value, col2: value, ...}], total_rows: number, query_time_ms: number}'. For host.usage, specify: '{calls_this_month: number, calls_limit: number, storage_bytes: number, storage_limit_bytes: number}'.
Add tool annotations to schema. Mark host.tool_remove and host.secret_set with destructiveHint: true. Mark host.usage, host.table.query, host.export with readOnlyHint: true. Mark host.tool_publish with idempotentHint: true if re-publishing with same name is safe.
Rename generic tools for clarity: host.usage → host.get_usage_stats, host.export → host.export_tenant_data. Add parameter descriptions: 'kind' should list valid values (echo, http, python, chain, wasm) as an enum or constraint.

Score history

Overall score trend

First recorded score · v2 rubric

55/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	55	2026-07-28+	v2