An MCP server for weather information.
MCPpedia last refreshed this data
An MCP server for weather information. is an MCP server that an MCP server for weather information. Its tool list has not been published yet over stdio, requires no API key, and scores 64/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-kambleaa007-weather": {
"args": [
"-y",
"npm"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An AI-driven dispute resolution platform built with React frontend and AWS CDK Lambda backend. GrappleAI advocates for consumers in post-purchase disputes using autonomous agents and the Model Context Protocol (MCP).
No automated test available for this server. Check the GitHub README for setup instructions.
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 maps
18 Google Maps tools for AI agents — geocode, search, directions, weather, and more.
A Model Context Protocol (MCP) server implementation that connects Large Language Models (LLMs) to GIS operations using GIS libraries, enabling AI assistants to perform geospatial operations and transformations.
MCP server from Kynth Studios — eleven read-only lookups over live public data: AI model pricing and routing, dependency maintenance, service pricing and stack cost, agent skills and configs, shadcn component registries, starter-kit grades, AI app-builder App Store readiness, ADA Title II reports, nonprofit good-standing. No key, no signup.
Multi-city flight routing intelligence — plan RTW trips, validate alliances, get carrier picks.
MCP Security Weekly
Get CVE alerts and security updates for An MCP server for weather information. and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An AI-driven dispute resolution platform built with React frontend and AWS CDK Lambda backend. GrappleAI advocates for consumers in post-purchase disputes using autonomous agents and the Model Context Protocol (MCP).
Get up and running in 5 minutes:
# Frontend
cd app && npm install && npm run dev
# Backend (separate terminal)
cd backend && npm install && npm run cdk:deploy
See QUICKSTART.md for detailed instructions.
React Frontend (Vite)
↓ HTTP/REST
API Gateway (AWS)
↓
Lambda Function (Node.js 20.x)
├─ MCP Server
├─ Request Handler
└─ Business Logic
↓
┌───┴───┬────────┐
↓ ↓ ↓
DynamoDB S3 DynamoDB
Disputes Evidence Negotiations
grappleai/
├── app/ # React frontend
│ ├── src/
│ │ ├── components/ # React components
│ │ ├── pages/ # Page components
│ │ ├── services/ # API client
│ │ ├── store/ # State management
│ │ └── types/ # TypeScript types
│ └── package.json
│
├── backend/ # AWS CDK backend
│ ├── lib/
│ │ ├── cdk/ # CDK stack
│ │ ├── lambda/ # Lambda handler
│ │ ├── mcp/ # MCP server
│ │ └── types/ # TypeScript types
│ └── package.json
│
├── SDLC to AIDLC/ # Methodology docs
│ ├── AIDLC.md
│ └── SDLC.md
│
├── AI-DLC/ # AI-DLC documentation
│ └── AI-DLC.md
│
├── QUICKSTART.md # 5-minute setup
├── SETUP.md # Complete setup guide
├── PROJECT_OVERVIEW.md # Architecture overview
└── README.md # This file
cd app
npm install
npm run dev
Visit: http://localhost:5173
cd backend
npm install
npm run cdk:deploy
Update app/.env.local:
VITE_API_URL=https://your-api-endpoint.com/api
POST /disputes - Create disputeGET /disputes - List disputesGET /disputes/{id} - Get dispute detailsPUT /disputes/{id} - Update disputePOST /evidence/upload - Upload evidenceGET /evidence/{id} - Get evidencePOST /evidence/{id}/verify - Verify evidence