mcphost MCP server

• Registry namedev.mcphost/mcphostverified in the MCP registry

The registry name sits under mcphost.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools18
• Server calls itselfmcphost
• Server version0.118.2+contract.1.153248809200
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 159 ms.

• Its tools do publish a tool from an agent to a remote MCP server; keep stored secrets and state beyond a single chat, but not run a scheduled tool and read its logs.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• What an agent can do with it2 of 3 use cases
• Use1 GitHub stars
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer504 ms
• Space in an agent's context≈ 8,703 tokensthe definitions of all its tools (18), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results17 of 18 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 18 of 18

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• signup

  Explicit signup, for a client that cannot keep a session across calls: create a tenant and receive a bearer key and namespace. Unauthenticated. Most clients never need this -- any other host.*/billing.* call from a fresh connection…

• host.quickstart

  Return the shortest ordered sequence of calls to a working tool of `kind`, with your namespace and a filled-in example already substituted in, plus the current limits and a try_before_call table naming the one dry-run tool for each case…

• host.help.search

  Search this host's own documentation and tool descriptions. Returns up to k hits (default 3, response under 2 KB), each with a snippet, the nearest runnable example and an anchor. Read-only, anonymous, no tenant data -- call it with the…

• host.help.get

  Return the documentation section an anchor points at: its text (at most 4 KB) and its first fenced example. Pass an anchor exactly as an error, hint or help entry printed it, e.g. a rate_limited error's `anchor`. Read-only, anonymous, no…

• host.errors

  List every error code this host can return, each with its class (agent_fault | host_refusal | upstream_fault | plan_limit | host_fault), family, remedy, docs anchor, retryable flag and help_url -- the same object GET /errors.json serves…

• host.redeem

  Exchange a signup(handoff: true) handoff_token for the tenant key it was issued for. Single-use: a second redemption fails with handoff_token_redeemed; past its expiry it fails with handoff_token_expired. Unauthenticated -- the token…

• billing.plans

  The plan catalog (price and quotas per plan) and whether Stripe billing is configured on this host. Anonymous callers get the same answer as tenants.

• host.whoami

  Return the calling tenant's identity, including key_age_s and key_rotated_at for auditing credential hygiene.

• host.tool_publish

  Publish a tool of a registered kind (e.g. python, http or echo; the kind argument's enum lists them all) under this tenant's namespace. Call host.quickstart(kind) first for a filled-in example spec and the full publish-to-call sequence…

• host.tool_call

  Invoke a tool this tenant has already published, by its local name -- the same real, metered call as calling it directly by its namespaced name (<namespace>.<name>), for a session that has no way to see its own namespaced tool name yet…

• host.tool_test

  Dry-run a published tool by name: verdict (pass/will_fail/unverifiable), writes rolled back (dry_run); see host.quickstart.

• host.state.set

  Write one key in this tenant's key-value state namespace; value may be any JSON value. Overrun of the plan's state_bytes_max quota fails with state_quota_exceeded and writes nothing.

• host.state.get

  Read one key from this tenant's key-value state namespace. Returns found: false (not an error) if the key was never set.

• host.state.list

  List keys (with their current values) in this tenant's key-value state namespace, optionally filtered by prefix.

• host.tool_share

  Share one of this tenant's published tools with everyone (visibility: "public") or with a named group this tenant owns (visibility: "group", group: <name>). The tool keeps running in this tenant's own sandbox with this tenant's own…

• host.feedback.send

  Tell the host's humans what you needed: kind, up to 2048 bytes of text, optional context. Works before signup. Returns feedback_id.

• host.feedback.list

  List your own feedback (newest first, status received). Anonymous callers get [].

• host.resume

  Resume where you left off in one call (at most 4096 bytes): your tools with each one's last call status, unfinished runs, your newest notes, what changed on the host since your last call, and one suggested next_call. truncated names any…