fix: correct MCP Registry name casing to io.github.ExaDev

Author: Mearman

README.md

@@ -101,7 +101,7 @@ Add to your MCP server configuration:
 
 The generic MCP bridge works with any MCP client. Incoming messages are included in every tool response.
 
-This server is also published to the MCP Registry as `io.github.exadev/agent-comms`.
+This server is also published to the MCP Registry as `io.github.ExaDev/agent-comms`.
 
 ### Other harnesses
 

package.json

@@ -9,7 +9,7 @@
     "url": "git+https://github.com/ExaDev/agent-comms.git"
   },
   "homepage": "https://github.com/ExaDev/agent-comms#readme",
-  "mcpName": "io.github.exadev/agent-comms",
+  "mcpName": "io.github.ExaDev/agent-comms",
   "bugs": "https://github.com/ExaDev/agent-comms/issues",
   "license": "MIT",
   "keywords": [

server.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
-  "name": "io.github.exadev/agent-comms",
+  "name": "io.github.ExaDev/agent-comms",
   "title": "Agent Comms",
   "description": "Cross-harness communication mesh for LLM agents — rooms, DMs, presence, and visibility over TCP",
   "repository": {