@whoisxmlapidotcom/mcp-whoisxmlapi 1.0.3 → 1.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +9 -8
  2. package/index.js +3 -3
  3. package/package.json +9 -9
package/README.md CHANGED
@@ -7,7 +7,8 @@ For full documentation, see [the MCP Server documentation](https://mcp-whoisxmla
7
7
  ## Features
8
8
 
9
9
  - **Token-based Authentication**: Secure API access using bearer tokens configured via environment variables
10
- - **SSE Support**: Run as an HTTP server with Server-Sent Events (SSE) for web-based integrations
10
+ - **HTTP Server Mode**: Run as an HTTP server with streamable HTTP transport for web-based integrations
11
+ - **Hosted Mode**: Multi-tenant deployment with per-request token authentication (see [HOSTING.md](HOSTING.md))
11
12
  - **Timeout Control**: Configurable request timeouts
12
13
 
13
14
  ## Installation
@@ -141,17 +142,17 @@ export WHOISXMLAPI_TOKEN=your-token-here
141
142
  mcp-whoisxmlapi
142
143
  ```
143
144
 
144
- ### Server-Sent Events (SSE) Mode
145
+ ### HTTP Server Mode
145
146
 
146
- Alternatively, you can run `mcp-whoisxmlapi` as an HTTP server with SSE support for web-based integrations:
147
+ Alternatively, you can run `mcp-whoisxmlapi` as an HTTP server for web-based integrations:
147
148
 
148
149
  ```bash
149
150
  export WHOISXMLAPI_TOKEN=your-token-here
150
- mcp-whoisxmlapi --sse --sse-port=3000
151
+ mcp-whoisxmlapi --http --http-port=3000
151
152
  ```
152
153
 
153
- In SSE mode, the server will listen on the specified port (default: 3000) and provide the same MCP tools over HTTP using Server-Sent Events. This is useful for web applications or environments where stdio communication isn't practical.
154
+ In HTTP mode, the server will listen on the specified port (default: 3000) and provide the same MCP tools over HTTP using streamable HTTP transport. This is useful for web applications or environments where stdio communication isn't practical.
154
155
 
155
- **Available SSE Options:**
156
- - `--sse`: Enable SSE server mode
157
- - `--sse-port=PORT`: Specify the port to listen on (default: 3000)
156
+ **Available HTTP Options:**
157
+ - `--http`: Enable HTTP server mode
158
+ - `--http-port=PORT`: Specify the port to listen on (default: 3000)
package/index.js CHANGED
@@ -1,10 +1,10 @@
1
1
  #!/usr/bin/env node
2
2
  const path = require('path');
3
3
  const child_process = require('child_process');
4
- const mapping = { linux_arm: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_linux_arm', 'mcp-whoisxmlapi' ], linux_x64: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_linux_amd64', 'mcp-whoisxmlapi' ], linux_arm64: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_linux_arm64', 'mcp-whoisxmlapi' ], win32_x64: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_windows_amd64', 'mcp-whoisxmlapi.exe' ], win32_arm: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_windows_arm', 'mcp-whoisxmlapi.exe' ], win32_arm64: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_windows_arm64', 'mcp-whoisxmlapi.exe' ], darwin_x64: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_darwin_amd64', 'mcp-whoisxmlapi' ], darwin_arm64: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_darwin_arm64', 'mcp-whoisxmlapi' ] };
5
- const modulesDirectory = path.dirname(path.dirname(__dirname));
4
+ const mapping = { linux_arm: { name: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_linux_arm' ], bin: 'mcp-whoisxmlapi' }, linux_x64: { name: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_linux_amd64' ], bin: 'mcp-whoisxmlapi' }, linux_arm64: { name: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_linux_arm64' ], bin: 'mcp-whoisxmlapi' }, win32_x64: { name: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_windows_amd64' ], bin: 'mcp-whoisxmlapi.exe' }, win32_arm: { name: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_windows_arm' ], bin: 'mcp-whoisxmlapi.exe' }, win32_arm64: { name: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_windows_arm64' ], bin: 'mcp-whoisxmlapi.exe' }, darwin_x64: { name: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_darwin_amd64' ], bin: 'mcp-whoisxmlapi' }, darwin_arm64: { name: [ '@whoisxmlapidotcom', 'mcp-whoisxmlapi_darwin_arm64' ], bin: 'mcp-whoisxmlapi' } };
6
5
  const definition = mapping[process.platform + '_' + process.arch];
7
- const packagePath = path.join(modulesDirectory, ...definition);
6
+ const packageJsonPath = require.resolve(path.join(...definition.name, 'package.json'));
7
+ const packagePath = path.join(path.dirname(packageJsonPath), definition.bin);
8
8
  child_process.spawn(packagePath, process.argv.splice(2), {
9
9
  stdio: 'inherit',
10
10
  env: process.env,
package/package.json CHANGED
@@ -1,18 +1,18 @@
1
1
  {
2
2
  "name": "@whoisxmlapidotcom/mcp-whoisxmlapi",
3
- "version": "1.0.3",
3
+ "version": "1.1.0",
4
4
  "bin": {
5
5
  "mcp-whoisxmlapi": "index.js"
6
6
  },
7
7
  "optionalDependencies": {
8
- "@whoisxmlapidotcom/mcp-whoisxmlapi_linux_arm": "1.0.3",
9
- "@whoisxmlapidotcom/mcp-whoisxmlapi_linux_amd64": "1.0.3",
10
- "@whoisxmlapidotcom/mcp-whoisxmlapi_linux_arm64": "1.0.3",
11
- "@whoisxmlapidotcom/mcp-whoisxmlapi_windows_amd64": "1.0.3",
12
- "@whoisxmlapidotcom/mcp-whoisxmlapi_windows_arm": "1.0.3",
13
- "@whoisxmlapidotcom/mcp-whoisxmlapi_windows_arm64": "1.0.3",
14
- "@whoisxmlapidotcom/mcp-whoisxmlapi_darwin_amd64": "1.0.3",
15
- "@whoisxmlapidotcom/mcp-whoisxmlapi_darwin_arm64": "1.0.3"
8
+ "@whoisxmlapidotcom/mcp-whoisxmlapi_linux_arm": "1.1.0",
9
+ "@whoisxmlapidotcom/mcp-whoisxmlapi_linux_amd64": "1.1.0",
10
+ "@whoisxmlapidotcom/mcp-whoisxmlapi_linux_arm64": "1.1.0",
11
+ "@whoisxmlapidotcom/mcp-whoisxmlapi_windows_amd64": "1.1.0",
12
+ "@whoisxmlapidotcom/mcp-whoisxmlapi_windows_arm": "1.1.0",
13
+ "@whoisxmlapidotcom/mcp-whoisxmlapi_windows_arm64": "1.1.0",
14
+ "@whoisxmlapidotcom/mcp-whoisxmlapi_darwin_amd64": "1.1.0",
15
+ "@whoisxmlapidotcom/mcp-whoisxmlapi_darwin_arm64": "1.1.0"
16
16
  },
17
17
  "os": [
18
18
  "linux",