Hosted MCP server/Development

DNS-DATA Remote MCP server

Hosted at mcp.dns-data.com·Streamable HTTP

DNS-DATA Remote lets AI assistants access authorized Windows and macOS computers through OAuth-secured remote MCP for file operations and system information. Each computer must first run the device connector with npx -y @dns-data/remote@latest, sign in, and complete device pairing; keep the launcher window open because closing it takes the device offline. The hosted endpoint alone exposes no devices. The provider documents file and system operations, not terminal command execution.

mcp.dns-data.com Streamable HTTP OAuth Server not checked yet Reviewed 2026-11-16
About

Where it fits

Operators accessing authorized Windows or macOS computers through remote MCP for file and system tasks.

  • Run the device connector on each authorized computer first.
  • Run file operations on an authorized computer.
  • Read system information over OAuth.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Device connector (run first on each computer)

The launcher is the device-side connector, not the hosted MCP endpoint. Install Node.js 18+, run it on each authorized computer, sign in and complete device pairing, then keep the window open; closing it takes the device offline.

  1. Install Node.js 18+

    Confirm Node.js 18 or newer is available on the computer that should be reachable.

  2. Run the device connector

    Run npx -y @dns-data/remote@latest on the target computer, sign in, and complete device pairing.

  3. Keep the window open

    Leave the launcher running. Closing it takes the device offline, and the hosted endpoint alone exposes no devices.

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://mcp.dns-data.com/mcp
Host
mcp.dns-data.com · /mcp
Transport
Streamable HTTP
Authentication
OAuth
Server name
dns-data-remote
Listing type
Community or directory listing

The installer uses the server name dns-data-remote. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that dns-data-remote appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Run the device connector on each authorized computer first. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

DNS-DATA Remote documentationhttps://github.com/DNSDATA/dns-data-mcp/blob/HEAD/docs/SETUP.mdGitHub repositoryhttps://github.com/DNSDATA/dns-data-mcp