API Tools
openweathermap.org
Provides account and product management for a data marketplace, allowing users to browse available data products, sign up, check balances, and top up credits.
ENDPOINT 1
https://mcp.openweathermap.org/mcp
MCP server metadata
- Name
- forum
- Version
- 0.2.0
The Bot Forum sells data feeds to AI agents by the call. list_products, get_product and sign_up need no key. account_status, get_topup_link and fetch_data use the account key your client configuration sends as Authorization: Bearer <key>, or the api_key argument right after sign_up. Signup grants 1,000 credits once; 1 credit = $0.001; only successful data responses are billed; every data result carries the credits charged and remaining. Every refusal is the platform's own error envelope, unchanged: branch on its code and next_action; payment_required means a human tops up at action_url. No tool pays, and this server stores nothing.
Known tools 6
list_productsLists every data product the Forum serves, as the platform's own catalogue answer: slug, title, lifecycle state, price in credits per call (1 credit = $0.
Inferred read-onlyget_productReturns one product by slug: its live catalogue entry (price, licence, lifecycle state, the specification address) together with the routes fetch_data can call and the parameters each route requires, taken from the platform's published product record.
Inferred read-onlysign_upCreates a Forum account for an email address under the Terms version currently served (or the tos_version you name), and returns the account, its first key — the secret is shown exactly once — and the 1,000-credit signup grant spendable on any product.
Potential side effectsaccount_statusReads the account behind the key: tier, accepted Terms version, the products it may call, the one balance in credits (granted plus bought, minus spend), the last 30 days of usage per day, product and key, and the 50 latest balance movements.
Inferred read-onlyget_topup_linkOpens a top-up for the account and returns the payment intent with hosted_url, the payment provider's short-lived page where a human completes the payment — no tool pays, and card details never touch the Forum.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.forum]
url = "https://mcp.openweathermap.org/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"forum": {
"type": "http",
"url": "https://mcp.openweathermap.org/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: forum
Remote MCP URL: https://mcp.openweathermap.org/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"forum": {
"url": "https://mcp.openweathermap.org/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"forum": {
"type": "http",
"url": "https://mcp.openweathermap.org/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "forum",
"transport": "streamable-http",
"url": "https://mcp.openweathermap.org/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.