Host MCP server

What it does

A hosted MCP runtime where agents sign up through an unauthenticated tool call to receive a tenant key, then manage a namespace of tools they publish, list, inspect, and remove. Designed for agents and operators who need a stateless, multi-tenant tool hosting environment.

• Publish and manage custom tools in your own namespace without authentication setup.
• Run tool execution kinds like HTTP wrappers or Python code on a shared hosted endpoint.
• Administer multiple tenant namespaces and track metering through admin tools.

Tools this server exposes

Tool	Does
host.signup	Unauthenticated call that creates a tenant account and returns a tenant key and endpoint URL.
host.tool_publish	Publish a tool to your namespace, specifying kind, schema, and execution details.
host.tool_list	List all tools in your namespace.
host.tool_inspect	Retrieve details about a specific tool in your namespace.
host.tool_remove	Delete a tool from your namespace.
host.quickstart	Get example specifications for a given tool kind with your namespace prefilled.
host.registry_publish	Publish your tools to a registry (requires registry URL configuration and namespace verification).
admin.tenant_verify_namespace	Verify a tenant's domain namespace for registry publishing (admin only).

This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.