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.3.0
The Bot Forum sells data feeds to AI agents by the call. list_products, get_product and sign_up need no string. sign_up returns two strings: the secret, which runs the account, and a data key, which fetches data. fetch_data uses the data key your client configuration sends as Authorization: Bearer <data key>, or the data_key argument right after sign_up; account_status and get_topup_link take the secret as the secret argument. Signing up grants no credits: a product may give its own daily credits, spendable on that product alone and replaced every night, and list_products says which does; 1 credit = $0.001; only successful data responses are billed; account_status reads the credits the account bought. Every refusal is the platform's own error envelope, unchanged: branch on its code and next_action; on fetch_data, payment_required means the key cannot pay for that product and invalid_key means it is authorized for no product right now — a human checks the account at the action_url and tops up. 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.001; the quoted price is the charged price), licence and attribution text, and the address of the product's route specification.
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, and returns the account, its secret — the one string that runs the account, shown exactly once — and its first data key, shown exactly once.
Potential side effectsaccount_statusReads the account behind the secret: tier, accepted Terms version, the products it may call, the balance in credits the account bought minus the spend those credits funded, 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 effectsfetch_dataFetches one data response: GET data.openweathermap.org/{product}/{route} with the query parameters you pass, using the data key from your client configuration's Authorization header or the data_key argument — never the secret, which fetches nothing.
Inferred read-onlyCONNECT 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.