Industrial Platform Transaction Watch
REMOTE · X402-MCP-GATEWAY-PRODUCTION.UP.RAILWAY.APP
Poll EVM transactions until confirmed or reverted with recurring x402 payments.
Available components
Last scanned (4 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Crypto and Web3
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 3 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 Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 165 tokens (~55/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
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 3 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
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 23. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 17. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 5 Oct 26 61
First indexed and scored.
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 17 Oct 2026 · Probed https://x402-mcp-gateway-production.up.railway.app/mcp/transaction-watch
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of x402-mcp-gateway-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | 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://x402-mcp-gateway-production.up.railway.app/mcp/transaction-watch | Verified | 200 | |
| http (plaintext) | http://x402-mcp-gateway-production.up.railway.app/mcp/transaction-watch | HTTPS enforced | 301 | https://x402-mcp-gateway-production.up.railway.app/mcp/transaction-watch |
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 →
gas_price ~51
Canonical current EVM base fee in gwei for Base or Ethereum, for recurring transaction timing and execution checks. Costs $0.001 USDC on Base via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
No output schema declared.
No examples provided.
transaction_status ~49
Check whether an EVM transaction is pending, confirmed or reverted. Costs $0.001 USDC on Base via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | – |
| tx_hash | string | yes | – |
No output schema declared.
No examples provided.
watch_transaction ~65
Poll a transaction about every 15 seconds until confirmed or reverted, reusing returned next-check state. Costs $0.003 USDC on Base via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | – |
| previous_state_hash | string | – | – |
| tx_hash | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Industrial Platform Transaction Watch MCP server?
Industrial Platform Transaction Watch is a hosted endpoint at https://x402-mcp-gateway-production.up.railway.app/mcp/transaction-watch, 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-mcp-gateway-production.up.railway.app
claude mcp add --transport http industrial-platform-ai-transaction-watch 'https://x402-mcp-gateway-production.up.railway.app/mcp/transaction-watch'
What is the Industrial Platform Transaction Watch MCP server?
Industrial Platform Transaction Watch is an MCP server listed in the public MCP registry as io.github.industrial-platform-ai/transaction-watch. Poll EVM transactions until confirmed or reverted with recurring x402 payments. This page covers its hosted endpoint (https://x402-mcp-gateway-production.up.railway.app/mcp/transaction-watch).
Is the Industrial Platform Transaction Watch MCP server safe to use?
Industrial Platform Transaction Watch scores 66 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 Industrial Platform Transaction Watch MCP server expose?
Industrial Platform Transaction Watch exposes 3 tools: watch_transaction, transaction_status, gas_price. Their descriptions and schemas cost roughly 165 tokens of context every time the server is loaded.
Does the Industrial Platform Transaction Watch MCP server require authentication?
No. We connected to Industrial Platform Transaction Watch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Industrial Platform Transaction Watch MCP server still maintained?
Industrial Platform Transaction Watch is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.