← Back to Check

railrouter-lite

https://railrouter-lite.sgdata.workers.dev

Scanned Apr 14, 2026

B80/100
Clarity
100
Protocol
40
Auth
0
Reliability
95
Trust
86
Safety
80
Market
55

Upgrade available

Your server uses protocol 2025-03-26. The latest version is 2025-11-25 with session management, origin validation, and notification support.

Strengths & Weaknesses

Clarity (100)Protocol (40)Auth (0)Reliability (95)Trust (86)Safety (80)Market (55)

Top Issues

9 found
HIGHProtocol Version Header

Server does not reject invalid MCP-Protocol-Version header.

HIGHJSON-RPC Transport

Server does not reject malformed JSON-RPC requests.

MEDIUMSession Management

Server did not assign a session ID. Session management may not work.

MEDIUMTransport Security

Server does not validate Origin header — potential CSRF risk.

MEDIUMJSON-RPC Transport

Server does not return 202 for JSON-RPC notifications.

MEDIUM

Custom domain: Default hosting subdomain

MEDIUM

No authentication required — server is open to anonymous access, which may be intentional for public tools

MEDIUM

Multiple similar MCP servers exist. Consider differentiating with unique features.

LOW

Unexpected response to SSE GET request: 200.

Protocol & Capabilities

Transport:Streamable HTTP✓
Protocol:2025-03-26✓
SSE Support:No○
Session ID:No○
Protocol Checks
✓
Ping

Server responded to ping

!
Session ID

No Mcp-Session-Id assigned by server

✗
Version Header Validation

Server returned 200 for invalid protocol version (expected 400)

✗
JSON-RPC Validation

Server returned 200 for malformed JSON-RPC (expected 400)

✗
Origin Header

Server returned 200 for invalid Origin (expected 403)

✓
Session Termination (DELETE)

Server accepts DELETE for session termination (200)

✗
Notification Handling (202)

Server returned 200 for notification (expected 202)

!
Server Info

Server info: name, version

Server Capabilities
✓Tools
○Resources
○Prompts
○Completions
○Tasks
○Logging

Auth

○

No OAuth? That's OK

OAuth is optional, but consider it for production deployments to protect your server from unauthorized access.

Trust

✓Latency: 11ms
✓HTTPS
○Default hosting subdomain
✓Name: railrouter-lite, Version: 1.0.0
✓Structured errors

Market

UniquenessCan it be done with an LLM alone?
5/10

No clear uniqueness signals detected

OriginalityHow many similar servers exist?
1/10

5+ similar servers — crowded space

DemandHow broad is the audience?
8/10

Domain "stripe" has broad developer audience

Competitors found

x402 is the right idea for agent payments. Here's why I still ripped it ...

I've been running an MCP server for ad campaign intelligence called Adpulse for a few months — audit tools, copy generation, ...

microchipgnu/MCPay: Open-source Infrastructure for MCP and x402

MCPay is open-source infrastructure that adds on-chain payments to any Model Context Protocol (MCP) server using the x402 "Payment Required" protocol.

Payments for MCPs Building the Future with x402 and AP2 I Luís ...

... call payments using stablecoins (e.g., USDC) without subscriptions or API keys. Developers can monetize MCP servers via SDK integration or a ...

Two New Protocols That Teach AI How to Pay - x402 & ATXP.

x402 is baked into HTTP: An MCP Server could use x402 or it could use AXTP. It helps with discovery and payment initiation for any online ...

x402 Protocol Explained: How AI Agents Pay Onchain | Support - Eco

AI agent frameworks: MCP (Model Context Protocol) servers are adding x402 support so that AI models can pay for tool calls and data access autonomously.

Tools (1 tool)

route_paymentRead60

“route_payment: 60 pts | Risk: read | Naming: 10/15, Desc: 20/20, Input: 20/20, Annot: 0/15”

!Naming:10/15
✓Description:20/20
✓Input Schema:20/20
✓Output Schema:10/10
✗Annotations:0/15
✗Error Hints:0/15

Publish on MCPize

Get OAuth, billing, and discovery for free. Your server scored B — developers are looking for this.

Get Started →
Share on TwitterShare on LinkedIn