Smarter Weather Developer Onboarding
REMOTE · MCP.DEVELOPERS.SMARTERWEATHER.COM · 2 COMPONENTS · SCANNED SEP 21
Agent-first onboarding to Smarter Weather: plans, docs, signup, API keys, MCP config, billing.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 230 tokens (~57/item across 4 items; 3 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
How do I install the Smarter Weather Developer Onboarding MCP server?
Smarter Weather Developer Onboarding is a hosted endpoint at https://mcp.developers.smarterweather.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.developers.smarterweather.com
claude mcp add --transport http smarterweather-onboarding 'https://mcp.developers.smarterweather.com/'
{
"mcpServers": {
"smarterweather-onboarding": {
"url": "https://mcp.developers.smarterweather.com/"
}
}
} {
"servers": {
"smarterweather-onboarding": {
"type": "http",
"url": "https://mcp.developers.smarterweather.com/"
}
}
} [mcp_servers.smarterweather-onboarding] url = "https://mcp.developers.smarterweather.com/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"smarterweather-onboarding": {
"type": "remote",
"url": "https://mcp.developers.smarterweather.com/",
"enabled": true
}
}
} openclaw mcp add smarterweather-onboarding --url 'https://mcp.developers.smarterweather.com/' --transport streamable-http
mcp_servers:
smarterweather-onboarding:
url: "https://mcp.developers.smarterweather.com/" {
"McpServers": {
"smarterweather-onboarding": {
"Transport": "http",
"Url": "https://mcp.developers.smarterweather.com/"
}
}
} assistant mcp add smarterweather-onboarding -t streamable-http -u 'https://mcp.developers.smarterweather.com/'
{
"mcpServers": {
"smarterweather-onboarding": {
"type": "http",
"url": "https://mcp.developers.smarterweather.com/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
- Server version: 0.0.0.31 → 0.0.0.32 functional
- 16 Sept 26 0
- Server version: 0.0.0.30 → 0.0.0.31 functional
- 15 Sept 26 +1
- Server version: 0.0.0.29 → 0.0.0.30 functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 0
- Server version: 0.0.0.28 → 0.0.0.29 functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://mcp.developers.smarterweather.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.developers.smarterweather.com | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 25 Aug 2026 | 10 Mar 2027 | RSA 2048 | SHA256-RSA | f827eea3b7bac506030cc5ed54bac20 |
| SANs: mcp.developers.smarterweather.com | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.developers.smarterweather.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| smarterweather.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.developers.smarterweather.com | Verified | 200 | |
| http (plaintext) | http://mcp.developers.smarterweather.com | HTTPS enforced | 301 | https://mcp.developers.smarterweather.com/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_documentation Search Smarter Weather documentation ~84
Search the Smarter Weather developer documentation index (quickstart, REST API, MCP server, errors, rate limits, SDKs, pricing, API keys). Returns up to 5 matching entries with title, URL, and an actionable summary. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search terms, e.g. "authenticate rest api" (max 200 chars) |
No output schema declared.
No examples provided.
get_plans Get Smarter Weather developer plans ~51
Current developer-platform plans and pricing: Free, Developer, and Professional tiers with monthly price, included API-call allowance, and overage rates. One metered allowance spans REST and MCP usage. No authentication required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sign_up Get the Smarter Weather sign-up URL ~70
Returns the Smarter Weather developer sign-up URL (with MCP referral attribution). Present the URL so the user can create a free account in a browser (Clerk, no credit card). After they finish, reconnect this MCP server with OAuth and call create_api_key, then configure_mcp. No authentication required.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| instructions | string | yes | – |
| signupUrl | string | yes | – |
| widget | object | – | sw-ui-spec widget block rendered by the MCP Apps onboarding widget (ui://onboarding-widget/v1/index.html). Additive; safe to ignore. |
No examples provided.
What is the Smarter Weather Developer Onboarding MCP server?
Smarter Weather Developer Onboarding is an MCP server listed in the public MCP registry as io.github.smarterweather/onboarding. Agent-first onboarding to Smarter Weather: plans, docs, signup, API keys, MCP config, billing. This page covers its hosted endpoint (https://mcp.developers.smarterweather.com).
Is the Smarter Weather Developer Onboarding MCP server safe to use?
Smarter Weather Developer Onboarding scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Smarter Weather Developer Onboarding MCP server expose?
Smarter Weather Developer Onboarding exposes 3 tools: get_plans, get_documentation, sign_up. Their descriptions and schemas cost roughly 205 tokens of context every time the server is loaded.
Does the Smarter Weather Developer Onboarding MCP server require authentication?
No. We connected to Smarter Weather Developer Onboarding without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Smarter Weather Developer Onboarding MCP server still maintained?
Smarter Weather Developer Onboarding is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.