Summary
I own the domain agentsim.dev and the server dev.agentsim/mcp (v0.3.1) is published on the registry, but I no longer have access to the Ed25519 private key that was used to originally publish it. The key was generated in a previous session and wasn't persisted.
What I need
A way to reset or re-authorize the dev.agentsim namespace so I can publish updates using a new keypair. I can prove domain ownership via DNS TXT record or HTTP challenge — the _mcp-auth TXT record on agentsim.dev is already configured and under my control.
Current state
- Server:
dev.agentsim/mcp (v0.3.1)
- Remote URL:
https://mcp.agentsim.dev/mcp
- Domain:
agentsim.dev (managed via Cloudflare, I have full DNS control)
- DNS proof:
_mcp-auth.agentsim.dev TXT record is set and resolves correctly
Goal
Set up automated CI publishing via GitHub Actions so the registry entry updates on every release. The workflow is built and tested — just need the signing key to match the namespace.
Thanks!
Summary
I own the domain
agentsim.devand the serverdev.agentsim/mcp(v0.3.1) is published on the registry, but I no longer have access to the Ed25519 private key that was used to originally publish it. The key was generated in a previous session and wasn't persisted.What I need
A way to reset or re-authorize the
dev.agentsimnamespace so I can publish updates using a new keypair. I can prove domain ownership via DNS TXT record or HTTP challenge — the_mcp-authTXT record onagentsim.devis already configured and under my control.Current state
dev.agentsim/mcp(v0.3.1)https://mcp.agentsim.dev/mcpagentsim.dev(managed via Cloudflare, I have full DNS control)_mcp-auth.agentsim.devTXT record is set and resolves correctlyGoal
Set up automated CI publishing via GitHub Actions so the registry entry updates on every release. The workflow is built and tested — just need the signing key to match the namespace.
Thanks!