The whole point of Public Free Suffix has always been that the boring parts are already done: the console, the anycast DNS, the certificates, the anti-abuse rails. Lately we have been asking a different question: why should you be the one clicking through all of it? The answer is the thing we have been quietly shipping on the API side for a while, and as of November 22, 2026 it is ready for everyone.
PFS Free Domains MCP is our official Model Context Protocol server, listed in the MCP Registry as io.github.PublicFreeSuffix/free-domains. Connect it to the AI client you already use, and your assistant can search, register, and manage domains on PFS and SEUS the same way you do in the console. We are already running our own domains through it. Now you can too.
What it can do
The server covers the everyday work of owning a domain here:
- Availability checks: ask whether
myname.is-a.siis free before you claim it; - Registration: claim the name straight from the conversation, no console detour;
- DNS management: add, change, and remove records, all record types the console supports;
- WHOIS lookups: see who holds a name and what is registered about it;
- SSL certificates: issue and manage certificates for your names;
- SEUS free hosting: check and manage your free hosting from the same place.
Read-only questions like availability and WHOIS need nothing but a sign-in. Anything that changes state, like registering or editing records, uses the matching write permission, which keeps an innocent question from turning into an accidental change.
The address
Everything runs on one remote Streamable HTTP endpoint:
https://s.eus/api/mcp/pfs
Use the full URL exactly as written: no query string, no trailing slash. There is nothing to install locally, no package to keep updated, and no API key to babysit. Any client that speaks remote Streamable HTTP can use it.
How signing in works
Authentication is SEUS OAuth, the authorization code flow with PKCE (S256), and terminal clients can use a device-code flow instead. The first time your client calls the endpoint it gets a standard OAuth challenge, your browser opens the SEUS sign-in page, you approve the request once, and the client stores and renews the token itself. In practice you sign in once and forget about it.
Two things worth knowing:
- There is no API key and no bearer token to paste. Never put a fixed
Authorizationheader on the endpoint: it blocks the OAuth flow and sign-in will fail; - The endpoint advertises its permissions through OAuth protected resource metadata, so well-behaved clients request the right scopes automatically and you just approve them.
The scopes, in plain words
Access is split into eight scopes, four read and four write, so your client can ask for exactly what it needs:
domains:read/domains:writefor availability, WHOIS, and registration;dns:read/dns:writefor DNS records;ssl:read/ssl:writefor certificates;hosting:read/hosting:writefor SEUS free hosting.
A client that sends no scope request gets read-only access by default, and write calls answer with a clear 403 insufficient_scope instead of a surprise. Reconnecting and approving the wider scopes widens access; we recommend asking for the smallest set that does the job.
Install it in your client
Pick your client and follow its step. All of them end in the same place: the SEUS sign-in page in your browser, one approval, done.
Claude (web and Desktop): open Customize > Connectors > Add > Add custom connector, name it PFS Free Domains, enter https://s.eus/api/mcp/pfs, keep the detected OAuth settings, then Connect and sign in with SEUS. Free accounts can add one custom connector.
Claude Code:
claude mcp add --transport http pfs https://s.eus/api/mcp/pfs
Then run /mcp, select pfs, choose Authenticate, and approve the sign-in. Add --scope user if you want it available in every project.
Cursor: the one-click Cursor Plugin is the easy road (Customize > Plugins > Install from GitHub). For manual setup in ~/.cursor/mcp.json, the shared public client ID is required because SEUS does not auto-register OAuth clients:
{
"mcpServers": {
"pfs": {
"url": "https://s.eus/api/mcp/pfs",
"auth": {
"CLIENT_ID": "nsc_KY87pj5df041ShWTuuN2R_ZR"
}
}
}
}
The client ID is public by design and safe to share; it carries no secret.
VS Code (1.101+): run Chat: Open Customizations > MCP Servers > Add Server, choose HTTP, paste the URL, and the first tool call opens the browser for SEUS sign-in. Or drop this into a workspace .mcp.json:
{
"mcpServers": {
"pfs": {
"type": "http",
"url": "https://s.eus/api/mcp/pfs"
}
}
}
ChatGPT: under Plugins > + > Add custom MCP server, enter the URL, set authentication to OAuth, and Create as a plugin; mention it with @ in a conversation. Availability depends on your plan and workspace permissions.
Chinese clients we have tested: Cherry Studio and Doubao connect directly with their native OAuth loopback callback. CodeBuddy, Tongyi Lingma, Trae, and Qoder are stdio-only today, so bridge them through mcp-remote in device-code mode:
{
"mcpServers": {
"pfs": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://s.eus/api/mcp/pfs", "--device-code", "--static-oauth-client-info", "{\"client_id\":\"nsc_KY87pj5df041ShWTuuN2R_ZR\"}"]
}
}
}
Anything else: any client speaking remote Streamable HTTP works with the same URL, and stdio-only tools can bridge through plain mcp-remote the same way. The full guide has per-client steps, callback URLs, and troubleshooting.
Try it before you trust it
Once connected, start with a read-only question to see the wiring work:
Use PFS Free Domains to check whether a name is available on is-a.si.
No writes, no risk, and you will know in seconds whether the sign-in took. If tools do not appear after connecting, restart the client and start a new chat: most clients cache the tool list at startup.
Thank you
The console is not going anywhere; it remains the fastest way to register a name by hand. But a growing share of domain work happens in editors and agent sessions now, and it felt wrong to keep that world behind browser tabs. This server is how we fixed it for ourselves, and today it is yours.
Connect your client, take it for a spin, and tell us what you built with it in SEUS Community with the #PFS tag. If something fights you during setup, the troubleshooting section probably has the answer, and if it does not, we read everything. And if this project keeps being useful to you, a star on GitHub helps the next builder find us.