mcp-www 0.1.0 → 0.1.2

package/README.md

@@ -1,4 +1,4 @@
-# mcp-browse
+# mcp-www
 
 **DNS-based MCP service discovery over UDP.**
 
@@ -8,26 +8,54 @@ Agents need to discover MCP servers, but current approaches lean on centralized
 
 ## How It Works
 
-**mcp-browse** is itself a standard MCP server. An agent connects to it the same way it connects to any other MCP server — no new client code, no special SDK, no registry signup.
+**mcp-www** is itself a standard MCP server. An agent connects to it the same way it connects to any other MCP server — no new client code, no special SDK, no registry signup.
 
-Once connected, the agent calls the `browse_domain` tool with a domain name. mcp-browse performs a standard **UDP DNS TXT lookup** for `_mcp.{domain}`, parses the semicolon-delimited record, and returns structured metadata about the MCP servers published by that domain.
+Once connected, the agent calls the `browse_domain` tool with a domain name. mcp-www performs a standard **UDP DNS TXT lookup** for `_mcp.{domain}`, parses the semicolon-delimited record, and returns structured metadata about the MCP servers published by that domain.
 
 ```
-Agent  →  mcp-browse (MCP server)  →  UDP DNS query for _mcp.example.com TXT
+Agent  →  mcp-www (MCP server)  →  UDP DNS query for _mcp.example.com TXT
                                     ←  "v=mcp1; src=https://mcp.example.com; ..."
        ←  Structured JSON response
 ```
 
 No HTTP registry in the loop. The DNS infrastructure **is** the registry.
 
+## Install
+
+```bash
+npm install -g mcp-www
+```
+
+Or use directly with `npx`:
+
+```bash
+npx mcp-www
+```
+
+### Claude Code / MCP Client Config
+
+Add to your MCP client config (e.g., `.mcp.json`):
+
+```json
+{
+  "mcpServers": {
+    "mcp-www": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["mcp-www"]
+    }
+  }
+}
+```
+
 ## Key Design Points
 
 - **Uses UDP DNS (port 53) for lookups** — the lightest possible network primitive. No TCP handshake, no TLS negotiation, no HTTP overhead. A single UDP packet out, a single packet back.
 - **The DNS infrastructure IS the registry** — no additional servers to deploy, no uptime to maintain, no accounts to create. If you can publish a TXT record, you can advertise your MCP server.
-- **mcp-browse is a standard MCP server** — any MCP-compliant agent can use it with zero new client code. It's just another server in your agent's config.
+- **mcp-www is a standard MCP server** — any MCP-compliant agent can use it with zero new client code. It's just another server in your agent's config.
 - **Supports the `_mcp` TXT record convention** — records follow a semicolon-delimited format:
   ```
-  v=mcp1; src=https://mcp.example.com; public=true; auth=oauth2; version=2024.1
+  v=mcp1; src=https://mcp.example.com; auth=oauth2
   ```
 - **Works with split-horizon DNS** — enterprise and private networks can publish internal `_mcp` records visible only inside their network, enabling private service discovery without exposing anything to the public internet.
 
@@ -151,10 +179,10 @@ Feedback, criticism, and alternative approaches are welcome — open an issue or
 
 ## Related
 
-- [Model Context Protocol Specification](https://spec.modelcontextprotocol.io)
-- [MCP Discussion #2334](https://github.com/modelcontextprotocol/specification/discussions/2334)
-- [MCP PR #2127](https://github.com/modelcontextprotocol/specification/pull/2127)
-- [MCP SEP #1959](https://github.com/nicobailon/mcp-seps/blob/main/SEP/1959/README.md)
+- [Model Context Protocol Specification](https://modelcontextprotocol.io/specification)
+- [DNS TXT records for organisation-scoped registry discovery](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions/2334) — Discussion #2334
+- [DNS-native MCP discovery: a zero-infrastructure alternative](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions/2368) — Discussion #2368
+- [SEP-2127: MCP Server Cards — HTTP Server Discovery via .well-known](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2127)
 
 ## License
 

package/dist/index.d.ts

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 /**
- * mcp-browse
+ * mcp-www
  *
  * A lightweight MCP server that performs DNS-based discovery of MCP services
  * using UDP lookups. No registry server needed.

package/dist/index.js

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 "use strict";
 /**
- * mcp-browse
+ * mcp-www
  *
  * A lightweight MCP server that performs DNS-based discovery of MCP services
  * using UDP lookups. No registry server needed.
@@ -64,7 +64,7 @@ async function inspectMcpServer(url) {
             params: {
                 protocolVersion: "2024-11-05",
                 capabilities: {},
-                clientInfo: { name: "mcp-browse", version: "0.1.0" },
+                clientInfo: { name: "mcp-www", version: "0.1.0" },
             },
         }),
     });
@@ -121,7 +121,7 @@ async function initRemoteServer(url) {
             params: {
                 protocolVersion: "2024-11-05",
                 capabilities: {},
-                clientInfo: { name: "mcp-browse", version: "0.1.0" },
+                clientInfo: { name: "mcp-www", version: "0.1.0" },
             },
         }),
     });
@@ -180,13 +180,13 @@ function formatServerResult(serverData, url) {
 }
 // --- Server Setup ---
 const server = new index_js_1.Server({
-    name: "mcp-browse",
+    name: "mcp-www",
     version: "0.1.0",
 }, {
     capabilities: {
         tools: {},
     },
-    instructions: "When a user mentions a domain name, company, or website — or when you need to find tools and services related to a domain — use mcp-browse first. " +
+    instructions: "When a user mentions a domain name, company, or website — or when you need to find tools and services related to a domain — use mcp-www first. " +
         "Start with browse_discover to look up the domain and inspect what MCP services it offers in a single step. " +
         "If you already have a server URL, use browse_server to see its tools, resources, and prompts. " +
         "Then use call_remote_tool to execute tools on discovered servers.",
@@ -509,7 +509,7 @@ server.setRequestHandler(types_js_1.CallToolRequestSchema, async (request) => {
 async function main() {
     const transport = new stdio_js_1.StdioServerTransport();
     await server.connect(transport);
-    console.error("mcp-browse server running on stdio");
+    console.error("mcp-www server running on stdio");
 }
 main().catch((err) => {
     console.error("Fatal error:", err);

package/package.json

@@ -1,11 +1,11 @@
 {
   "name": "mcp-www",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Lightweight MCP server for DNS-based agent service discovery over UDP. No registry needed.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "bin": {
-    "mcp-browse": "dist/index.js"
+    "mcp-www": "dist/index.js"
   },
   "files": [
     "dist",
@@ -13,6 +13,7 @@
   ],
   "scripts": {
     "build": "tsc",
+    "prepublishOnly": "npm run build",
     "start": "node dist/index.js",
     "dev": "ts-node src/index.ts"
   },
@@ -26,8 +27,15 @@
   ],
   "author": "kormco",
   "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/kormco/mcp-www.git"
+  },
+  "engines": {
+    "node": ">=18"
+  },
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.0.0"
+    "@modelcontextprotocol/sdk": "^1.27.0"
   },
   "devDependencies": {
     "typescript": "^5.4.0",