docs: remove seed.json endpoint copy from readme

Author: toby

README.md

@@ -55,18 +55,6 @@ make dev-compose
 
 This will start the MCP Registry service and MongoDB with Docker, running at [`localhost:8080`](http://localhost:8080).
 
-### Registry Composability
-
-The registry supports composability through seed data import/export, allowing registry instances to share data:
-
-```bash
-# Start first registry with seed data
-MCP_REGISTRY_SEED_FILE_PATH=data/seed.json ./registry
-
-# Start second registry importing from first via HTTP
-./registry --seed-file-path=http://localhost:8080/v0/seed.json
-```
-
 ## Building
 
 If you prefer to run the service locally without Docker, you can build and run it directly:
@@ -399,53 +387,6 @@ Response example:
 }
 ```
 
-#### Export Seed Data
-
-```
-GET /v0/seed.json
-```
-
-Exports all servers in the registry in seed format for import by other registry instances.
-
-Response example:
-```json
-[
-  {
-    "id": "01129bff-3d65-4e3d-8e82-6f2f269f818c",
-    "name": "io.github.gongrzhe/redis-mcp-server",
-    "description": "A Redis MCP server implementation for interacting with Redis databases.",
-    "repository": {
-      "url": "https://github.com/GongRzhe/REDIS-MCP-Server",
-      "source": "github",
-      "id": "907849235"
-    },
-    "version_detail": {
-      "version": "0.0.1-seed",
-      "release_date": "2025-05-16T19:13:21Z",
-      "is_latest": true
-    },
-    "packages": [
-      {
-        "registry_name": "docker",
-        "name": "@gongrzhe/server-redis-mcp",
-        "version": "1.0.0",
-        "package_arguments": [
-          {
-            "description": "Docker image to run",
-            "is_required": true,
-            "format": "string",
-            "value": "mcp/redis",
-            "default": "mcp/redis",
-            "type": "positional",
-            "value_hint": "mcp/redis"
-          }
-        ]
-      }
-    ]
-  }
-]
-```
-
 ### Ping Endpoint
 
 ```
@@ -495,68 +436,26 @@ docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250806-a1b2
 
 **Configuration:** The Docker images support all environment variables listed in the [Configuration](#configuration) section. For production deployments, you'll need to configure the database connection and other settings via environment variables.
 
-### Command Line Flags
-
-Command line flags take precedence over environment variables:
-
-| Flag | Description | Environment Variable |
-|------|-------------|---------------------|
-| `--seed-file-path` | Path or URL to import seed file | `MCP_REGISTRY_SEED_FILE_PATH` |
-
-## Registry Composability
-
-The MCP Registry supports composability through seed data export/import functionality, enabling registry instances to share data with each other via HTTP endpoints.
-
-### Use Cases
-
-1. **Distributed Registries**: Set up multiple registry instances that share a common dataset
-2. **Registry Synchronization**: Import data from a central registry to local instances
-3. **Development Environments**: Import production data to development instances
-4. **Registry Migration**: Move data between different registry deployments
-
-### Export Seed Data
-
-Any registry instance can export its complete dataset:
-
-```bash
-# Export all servers in seed format
-curl http://localhost:8080/v0/seed.json > exported_data.json
-```
-
 ### Import Seed Data
 
 Registry instances can import data from:
 
 **Local files:**
 ```bash
 # Via environment variable
-MCP_REGISTRY_SEED_FILE_PATH=data/seed_2025_05_16.json ./registry
+MCP_REGISTRY_SEED_FILE_PATH=data/seed.json ./registry
 
 # Via command line flag
-./registry --seed-file-path=data/seed_2025_05_16.json
+./registry --seed-file-path=data/seed.json
 ```
 
 **HTTP endpoints:**
 ```bash
 # Via environment variable
-MCP_REGISTRY_SEED_FILE_PATH=http://localhost:8080/v0/seed.json ./registry
+MCP_REGISTRY_SEED_FILE_PATH=http://other-registry:8080 ./registry
 
 # Via command line flag
-./registry --seed-file-path=http://other-registry:8080/v0/seed.json
-```
-
-### Composability Workflow Example
-
-```bash
-# Step 1: Start primary registry with initial seed data
-MCP_REGISTRY_SEED_FILE_PATH=data/seed_2025_05_16.json ./registry
-
-# Step 2: Start secondary registry importing from primary
-./registry --seed-file-path=http://localhost:8080/v0/seed.json --server-address=:8081
-
-# Step 3: Verify both registries have the same data
-curl http://localhost:8080/v0/servers | jq '.servers | length'
-curl http://localhost:8081/v0/servers | jq '.servers | length'
+./registry --seed-file-path=http://other-registry:8080
 ```
 
 ## Testing