io.github.praneeth12098/x402-factory
REMOTE · X402-FACTORY.COM
200+ x402 paid data APIs for AI agents: prediction markets, verified weather, econ, SEC filings
Available components
Last scanned (14 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Data and Analytics
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 219 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 31891 tokens (~145/item across 219 items; 219 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 34% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "probability_evergreen_government-shutdown-this-quarter" implies "shutdown" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 219 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 219 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 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.
- 3 Nov 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.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 5 Nov 2026 · Probed https://x402-factory.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=x402-factory.com | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 19 Jul 2026 | 19 Jan 2027 | RSA 2048 | SHA256-RSA | 3308170fe02c4846c4f1c5583c0a5f6 |
| SANs: x402-factory.com | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of x402-factory.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| x402-factory.com. | No DS | 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://x402-factory.com/mcp | Verified | 200 | |
| http (plaintext) | http://x402-factory.com/mcp | HTTPS enforced | 301 | https://x402-factory.com/mcp |
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 →
weather_forecast-window_jacksonville ~168
Will it rain in Jacksonville during your event window. Event-window weather odds for Jacksonville: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the Jacksonville coordinates built in. [HTTP: GET /v1/forecast/jacksonville/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.jacksonville]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_forecast-window_las-vegas ~175
Will it rain in Las Vegas during your event window. Event-window weather odds for Las Vegas: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the Las Vegas coordinates built in. [HTTP: GET /v1/forecast/las-vegas/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.las-vegas]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_forecast-window_los-angeles ~175
Will it rain in Los Angeles during your event window. Event-window weather odds for Los Angeles: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the Los Angeles coordinates built in. [HTTP: GET /v1/forecast/los-angeles/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.los-angeles]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_forecast-window_miami ~168
Will it rain in Miami during your event window. Event-window weather odds for Miami: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the Miami coordinates built in. [HTTP: GET /v1/forecast/miami/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.miami]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_forecast-window_minneapolis ~166
Will it rain in Minneapolis during your event window. Event-window weather odds for Minneapolis: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the Minneapolis coordinates built in. [HTTP: GET /v1/forecast/minneapolis/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.minneapolis]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_forecast-window_nashville ~169
Will it rain in Nashville during your event window. Event-window weather odds for Nashville: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the Nashville coordinates built in. [HTTP: GET /v1/forecast/nashville/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.nashville]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_forecast-window_nyc ~173
Will it rain in New York City during your event window. Event-window weather odds for New York City: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the New York City coordinates built in. [HTTP: GET /v1/forecast/nyc/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.nyc]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_forecast-window_philadelphia ~169
Will it rain in Philadelphia during your event window. Event-window weather odds for Philadelphia: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the Philadelphia coordinates built in. [HTTP: GET /v1/forecast/philadelphia/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.philadelphia]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_forecast-window_phoenix ~169
Will it rain in Phoenix during your event window. Event-window weather odds for Phoenix: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the Phoenix coordinates built in. [HTTP: GET /v1/forecast/phoenix/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.phoenix]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_forecast-window_portland ~167
Will it rain in Portland during your event window. Event-window weather odds for Portland: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the Portland coordinates built in. [HTTP: GET /v1/forecast/portland/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.portland]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_forecast-window_san-antonio ~178
Will it rain in San Antonio during your event window. Event-window weather odds for San Antonio: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the San Antonio coordinates built in. [HTTP: GET /v1/forecast/san-antonio/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.san-antonio]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_forecast-window_san-diego ~175
Will it rain in San Diego during your event window. Event-window weather odds for San Diego: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the San Diego coordinates built in. [HTTP: GET /v1/forecast/san-diego/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.san-diego]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_forecast-window_san-francisco ~178
Will it rain in San Francisco during your event window. Event-window weather odds for San Francisco: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the San Francisco coordinates built in. [HTTP: GET /v1/forecast/san-francisco/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.san-francisco]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_forecast-window_san-jose ~175
Will it rain in San Jose during your event window. Event-window weather odds for San Jose: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the San Jose coordinates built in. [HTTP: GET /v1/forecast/san-jose/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.san-jose]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_forecast-window_seattle ~166
Will it rain in Seattle during your event window. Event-window weather odds for Seattle: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the Seattle coordinates built in. [HTTP: GET /v1/forecast/seattle/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.seattle]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_forecast-window_washington-dc ~181
Will it rain in Washington, DC during your event window. Event-window weather odds for Washington, DC: pass a start and end time (or omit them for the next six hours) and get rain probability and expected conditions across the window — built for scheduling decisions. Same shape as /v1/forecast/window with the Washington, DC coordinates built in. [HTTP: GET /v1/forecast/washington-dc/window · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.forecast-window.washington-dc]
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601), ≤12h after start. Default: start + 6h. |
| start | string | – | Window start (ISO-8601). Default: the top of the next hour. |
No output schema declared.
No examples provided.
weather_verification-scores ~171
Free: our forecast verification stats (MAE by variable, region, lead, segment). Transparent skill scores from stored forecast/actual pairs over a rolling 90-day window, scored against real NWS station observations and segmented by what produced each forecast (proprietary-blend temperature at covered stations vs NWS passthrough). Live-accumulated pairs are reported separately from the model's offline historical_oos fit metrics — the two are never mixed. Free forever so you can judge the model before paying for forecasts. [HTTP: GET /v1/verification/scores · price free via x402 · docs https://x402-factory.com/docs/weather.verification-scores]
| Name | Type | Req | Description |
|---|---|---|---|
| lead_hours | integer | – | – |
| region | string | – | – |
| variable | string | – | – |
No output schema declared.
No examples provided.
weather_verification-station ~167
One station's forecast-verification history: daily MAE/bias by lead and method. Single-station audit view of our forecast verification: daily MAE, signed bias, raw-NWS baseline, and sample counts for every lead time and method segment at one ICAO station, over a selectable window up to 90 days. Scored against that station's real NWS observations; model versions reported separately, never mixed. [HTTP: GET /v1/verification/station/:station · price $0.02 via x402 · docs https://x402-factory.com/docs/weather.verification-station]
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | yes | – |
| lead_hours | integer | – | – |
| station | string | yes | ICAO observation station, e.g. KNYC |
No output schema declared.
No examples provided.
weather_verification-table ~199
Full verification table: daily MAE/bias per station, lead, method, version. The audit table behind our free verification summary: every scored forecast/actual pair, aggregated at daily granularity per station × lead × method segment × model version, over a selectable window up to 90 days. Each cell carries our MAE, signed bias, the raw-NWS baseline MAE on the same rows where our forecast can differ from NWS, and sample counts. Scored against real NWS station observations; versions are never mixed. [HTTP: GET /v1/verification/table · price $0.03 via x402 · docs https://x402-factory.com/docs/weather.verification-table]
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | yes | Rolling window length in days |
| lead_hours | integer | – | – |
| segment | string | – | – |
| station | string | – | Filter to one ICAO station, e.g. KNYC |
No output schema declared.
No examples provided.
How do I install the io.github.praneeth12098/x402-factory MCP server?
io.github.praneeth12098/x402-factory is a hosted endpoint at https://x402-factory.com/mcp, 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 · x402-factory.com
claude mcp add --transport http praneeth12098-x402-factory 'https://x402-factory.com/mcp'
What is the io.github.praneeth12098/x402-factory MCP server?
io.github.praneeth12098/x402-factory is an MCP server listed in the public MCP registry as io.github.praneeth12098/x402-factory. 200+ x402 paid data APIs for AI agents: prediction markets, verified weather, econ, SEC filings. This page covers its hosted endpoint (https://x402-factory.com/mcp).
Is the io.github.praneeth12098/x402-factory MCP server safe to use?
io.github.praneeth12098/x402-factory scores 68 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 io.github.praneeth12098/x402-factory MCP server expose?
io.github.praneeth12098/x402-factory exposes 219 tools: core_ping, econ_calendar, econ_dashboard, econ_dashboard_changes, econ_dashboard_delta, and 214 more. Their descriptions and schemas cost roughly 31,891 tokens of context every time the server is loaded.
Does the io.github.praneeth12098/x402-factory MCP server require authentication?
No. We connected to io.github.praneeth12098/x402-factory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.praneeth12098/x402-factory MCP server still maintained?
io.github.praneeth12098/x402-factory is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.praneeth12098/x402-factory MCP server?
VerifyMCP ran 12 checks on io.github.praneeth12098/x402-factory, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.praneeth12098/x402-factory: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.