domeneschluse

no.domeneschlusePublished by domeneschluse.noOfficial publisherv1.1.0Updated Oct 24, 2026

Domeneshop-e-post og DNS i AI-assistenten din: søk, les, skriv, send. Gratis.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Lets an AI assistant search, read, write and send Domeneshop email and work with DNS settings.

What you can do
This remote server brings Domeneshop email and DNS functions into an AI assistant. According to the description, the assistant can search, read, write and send email, and work with DNS. The actual tool list is not provided in the available information.
When to use it
Use it when you want to handle Domeneshop email and DNS from inside an AI assistant instead of switching to the web console. Suited to routine tasks such as searching, reading, drafting or sending mail, and checking or adjusting DNS settings.
Requirements
Needs network access to the remote endpoint and OAuth authorization; a Domeneshop account is required. No environment variables or custom headers are declared.
Before you install
OAuth grants the assistant access to your Domeneshop account, which may cover email and DNS control. The assistant can write and send email and may change DNS settings, so review actions and their scope before use.

Installation

In SourceWeft

  1. Open domeneschluse in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/no.domeneschluse%2Fdomeneschluse/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "domeneschluse": {
      "type": "http",
      "url": "https://domeneschluse.no/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.