Weather

io.github.HyosikParkPublished by GitHub account HyosikParkv0.1.0Updated Oct 24, 2026

Current weather and forecasts for any coordinates, backed b… — paid per call (x402/credits), 1 tools

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

A remote MCP server that gives an assistant current weather and forecasts for any coordinates, billed per call through x402 or credits.

What you can do
Retrieve current weather conditions for a given set of coordinates, based on the single weather tool the server exposes. Fetch forecasts for those coordinates as well. Calls are metered and paid per use rather than offered as a free service.
When to use it
Useful when an assistant needs live weather or forecast information for specific coordinates and the caller is set up to pay per request. Less suitable if you need a free, unmetered weather source or detailed documentation before committing.
Requirements
A remote MCP endpoint reached over streamable HTTP; nothing is installed locally. No authentication, environment variables or headers are declared. A payment arrangement for per-call billing (x402 or credits) is implied by the description, though the exact setup is not documented here.
Before you install
Each call is described as paid, so usage can incur charges; confirm pricing and spending limits before connecting. The server is a third-party hosted endpoint, so the coordinates you send go to that operator. No authentication is declared, so treat requests as unauthenticated.

Installation

In SourceWeft

  1. Open Weather in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.HyosikPark%2Fweather/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "weather": {
      "type": "http",
      "url": "https://hawker-gateway.fly.dev/mcp/weather"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.