에이전트 강화
게시자의 자체 URL입니다. PlugMCP 엔드포인트가 아닙니다.
Host a copy with our keys and logs.
https://agenthost.eu/mcp위의 Claude 버튼을 누르면 이름과 URL이 채워진 상태로 Claude가 열립니다. 확인은 Claude에서 직접 해야 합니다.
claude mcp add --transport http eu.agenthost-agenthost https://agenthost.eu/mcpRun in a terminal.
{ "mcpServers": { "eu.agenthost-agenthost": { "command": "npx", "args": [ "-y", "mcp-remote", "https://agenthost.eu/mcp" ] } }}claude_desktop_config.json
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행게시자 제공
agenthost is agent-first web hosting, driven entirely
through an MCP server. This repository holds the MCP Registry
listing for it — server.json — and the workflow that publishes
that listing.
Agent-first web hosting: deploy sites, apps, databases and domains over MCP.
agenthost is a remote MCP server: it is hosted by agenthost and reachable over
Streamable HTTP
at https://agenthost.eu/mcp. There is nothing to install locally.
eu.agenthost/agenthosthttps://agenthost.eu/mcp (Streamable HTTP)The server code itself lives in agenthost's private control-panel repository; this repository only carries the public registry metadata.
Point any MCP client that speaks Streamable HTTP at https://agenthost.eu/mcp.
Authentication is handled by the client's OAuth flow — you sign in (or sign up) at
agenthost in your browser, so there is no token to paste. For unattended clients
that cannot open a browser, agenthost can mint a long-lived API token to send as a
Bearer header.
Example client configuration:
{
"mcpServers": {
"agenthost": {
"type": "streamable-http",
"url": "https://agenthost.eu/mcp"
}
}
}
Publishing is automated with GitHub Actions (.github/workflows/publish-mcp.yml).
The registry entry is namespaced under eu.agenthost — the reverse-DNS form of
agenthost.eu — and ownership is proven with DNS authentication: a TXT record
on the apex of agenthost.eu holds the public half of an Ed25519 signing key, and
the workflow signs with the private half stored in the MCP_PRIVATE_KEY secret.
server.json against the official
schema (mcp-publisher validate) — no secret required.v* tag (or running the workflow manually) publishes to the
registry. On a tag, the published version is taken from the tag, so the git tag
is the single source of truth for the registry version.To cut a release:
git tag v0.1.0
git push origin v0.1.0
Verify afterwards:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=eu.agenthost/agenthost"
Generate the signing key on a trusted machine (needs OpenSSL 3+), so the private key never leaves your control:
# 1. Generate an Ed25519 key pair
openssl genpkey -algorithm Ed25519 -out key.pem
# 2. Build the DNS TXT record (public key)
PUBLIC_KEY="$(openssl pkey -in key.pem -pubout -outform DER | tail -c 32 | base64)"
echo "agenthost.eu. IN TXT \"v=MCPv1; k=ed25519; p=${PUBLIC_KEY}\""
# 3. Extract the private key for the GitHub secret
openssl pkey -in key.pem -noout -text | grep -A3 'priv:' | tail -n +2 | tr -d ' :\n'; echo
Then:
agenthost.eu
(agenthost.eu, not a _mcp-auth subdomain). Wait for it to propagate.MCP_PRIVATE_KEY (Settings → Secrets and variables → Actions). For stronger
protection, store it instead on a GitHub Environment named mcp-registry-publish
and restrict that environment to the default branch and release tags — the
workflow already references that environment.key.pem once the secret is stored.If you rotate the key, remove the old TXT record from the apex — a stale record is tried first and will fail verification.
server.jsonserver.json follows the MCP Registry
server.schema.json
(the $schema field pins the exact version). Keep the remotes[].url in sync with
the production endpoint, and keep description within the schema's 100-character
limit. CI validates every change, so a malformed edit fails in review.
Agent-first web hosting: deploy sites, apps, databases and domains over MCP.
{ "mcpServers": { "eu.agenthost-agenthost": { "url": "https://agenthost.eu/mcp", "headers": {} } }}도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 http 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
이 레코드에는 필수 환경 변수가 등록되어 있지 않습니다.
Agenthost에는 HTTP로 연결합니다.
마지막 확인: 2026-11-08. Agent-first web hosting: deploy sites, apps, databases and domains over MCP.