mcphost

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 creates a tenant implicitly and returns its own /u//mcp URL in the response's onboarding field. Recommended here: pass handoff: true to receive a short-lived, single-use handoff_token instead of the raw key -- redeem it once with host.redeem to get the key, so a transcript of this call and the redeem call, if it leaks, carries a dead credential. The raw-key path (handoff omitted) stays fully supported.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "signup"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	display name
`source`	No	Optional attribution tag for this signup (1-64 chars matching the pattern), e.g. "plugin", "www", "cli", "hn"; omit for none. Stored as the tenant's signup_source and counted in the signup-source funnel. Attribution only: whether a signup is real or synthetic is decided by the harness header and fleet IP, never by this value. "synthorg" is reserved for the discovery-chain harness.
`handoff`	No	Recommended: true to receive a handoff_token (redeem via host.redeem) instead of the raw key. Default false (raw key, unchanged).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / source

Added value: +{
+  "description": "Optional attribution tag for this signup (1-64 chars matching the pattern), e.g. \"plugin\", \"www\", \"cli\", \"hn\"; omit for none. Stored as the tenant's signup_source and counted in the signup-source funnel. Attribution only: whether a signup is real or synthetic is decided by the harness header and fleet IP, never by this value. \"synthorg\" is reserved for the discovery-chain harness.",
+  "pattern": "^[a-z0-9][a-z0-9._-]{0,63}$",
+  "type": "string"
+}

Changed1 schema field changedOct 3, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed1 schema field changedSep 13, 2026

addedInput schema / properties / handoff

Added value: +{
+  "description": "Recommended: true to receive a handoff_token (redeem via host.redeem) instead of the raw key. Default false (raw key, unchanged).",
+  "type": "boolean"
+}

First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does well: it declares the call unauthenticated, explains that handoff_token is short-lived and single-use, and gives the security rationale (a leaked transcript carries a dead credential). It does not mention rate limits, tenant quotas, or what happens on duplicate names, so it is strong but not exhaustive for an unannotated mutating tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and the primary caveat in the first sentence, with no filler. The final sentence about the raw-key path staying supported is a useful but slightly padded reassurance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must describe returns, and it does: a bearer key plus namespace, or a handoff_token, plus the mention of the onboarding field on implicit creation. An agent has enough to call correctly and to decide between handoff modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning to handoff: why it is recommended, that the token is single-use, and that it must be redeemed via host.redeem. The name and source parameters are left to the schema, which already documents them thoroughly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('create a tenant') plus what is returned ('bearer key and namespace'), and pins down the exact audience: a client that cannot keep a session across calls. It is clearly distinguished from the implicit-tenant behavior of sibling host.*/billing.* calls.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says most clients never need this and names the alternative path (any fresh host.*/billing.* call creates a tenant implicitly and returns /u/<secret>/mcp in the onboarding field). It also recommends the handoff:true variant and names host.redeem as the redemption step.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcphost tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.