Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"world-weather-online": {
"url": "https://mcp.worldweatheronline.com/mcp?key=YOUR_API_KEY"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for World Weather Online. Lets AI assistants like Claude, Cursor, and others call WWO weather data directly as tools.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
Autonomous spec-to-product coding-agent CLI with an MCP server exposing 34 tools over stdio.
MCP Security Weekly
Get CVE alerts and security updates for Wwo Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP server for World Weather Online. Lets AI assistants like Claude, Cursor, and others call WWO weather data directly as tools.
wwo-mcp-server)git init
git add .
git commit -m "Initial commit"
git remote add origin https://github.com/YOUR_USERNAME/wwo-mcp-server.git
git push -u origin main
wwo-mcp-server repositoryYour server will be live at a URL like:
https://wwo-mcp-server-production.up.railway.app
In Railway dashboard → your project → Settings → Networking → Custom Domain
Type mcp.worldweatheronline.com and click Add
Railway shows you a CNAME value like:
wwo-mcp-server-production.up.railway.app
Go to your DNS provider and add:
| Type | Name | Value |
|---|---|---|
| CNAME | mcp | wwo-mcp-server-production.up.railway.app |
SSL certificate is provisioned automatically within minutes
Visit your health endpoint:
https://mcp.worldweatheronline.com/health
Test in MCP Inspector:
https://mcp.worldweatheronline.com/mcp?key=YOUR_WWO_API_KEY
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"world-weather-online": {
"url": "https://mcp.worldweatheronline.com/mcp?key=YOUR_API_KEY"
}
}
}
Add to .cursor/mcp.json:
{
"mcpServers": {
"world-weather-online": {
"url": "https://mcp.worldweatheronline.com/mcp?key=YOUR_API_KEY"
}
}
}
| Tool | Description |
|---|---|
get_weather | Current conditions + 14-day forecast |
get_historical_weather | Past weather from 2008 onwards |
get_marine_weather | Swell, tides, water temperature |
get_ski_weather | Top/mid/base elevation forecasts |
search_location | Location autocomplete |
get_astronomy | Sunrise, sunset, moon phase |
get_timezone | Local time + UTC offset |
get_climate_averages | Monthly 12-year climate averages |
npm install
npm run dev
Server runs at http://localhost:3000