SteadyFetch

REMOTE · STEADYFETCH-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED AUG 3

Reliable web fetching for AI agents with retry, circuit breaker, caching, and anti-bot bypass

Available components

remote · steadyfetch-production.up.railway.app 63 pypi · steadyfetch 11

+5 this week 63 63 Trust /100

Trust breakdown (6 categories)

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 →

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 5 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 Usability71

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 501 tokens (~100/item across 5 items; 5 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage71

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
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · steadyfetch-production.up.railway.app

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http carsonroell-debug-steadyfetch https://steadyfetch-production.up.railway.app/mcp

# ~/.codex/config.toml

[mcp_servers.carsonroell-debug-steadyfetch]
url = "https://steadyfetch-production.up.railway.app/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "carsonroell-debug-steadyfetch": {
      "type": "remote",
      "url": "https://steadyfetch-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add carsonroell-debug-steadyfetch --url https://steadyfetch-production.up.railway.app/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  carsonroell-debug-steadyfetch:
    url: "https://steadyfetch-production.up.railway.app/mcp"

// mcp.json

{
  "mcpServers": {
    "carsonroell-debug-steadyfetch": {
      "type": "http",
      "url": "https://steadyfetch-production.up.railway.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 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.
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 58

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Probed https://steadyfetch-production.up.railway.app/mcp

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=YE1,O=Let's Encrypt,C=US	29 Jul 2026	27 Oct 2026	ECDSA 256	ECDSA-SHA384	6da79bb561da3efeb0e751ca21abd3999fe
SANs: *.up.railway.app, up.railway.app
CN=YE1,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	5ddd70dd31f801c85c186a7a04b80afe
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

DNSSEC insecure

Validation of steadyfetch-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

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://steadyfetch-production.up.railway.app/mcp	Verified	200
http (plaintext)	http://steadyfetch-production.up.railway.app/mcp	HTTPS enforced	301	https://steadyfetch-production.up.railway.app/mcp

MCP tools — 5 exposed · ~440 tokens

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.

Tool Tokens

cache_stats ~30

Get cache statistics — size and item count. Useful for monitoring cache utilization and deciding when to clear.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
result	string	yes	—

No examples provided.

check_domain ~89

Check the health status of a domain. Returns the circuit breaker state: 'closed' (healthy), 'open' (failing), or 'half_open' (testing recovery). Use this before batch operations to avoid wasting time on domains that are down. Args: domain: The domain to check (e.g., 'example.com')

Input Output Examples

Name	Type	Req	Description
domain	string	yes	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

clear_cache ~31

Clear the entire fetch cache. Use when you need fresh data and don't want to rely on cached results.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
result	string	yes	—

No examples provided.

fetch_markdown ~124

Fetch a URL and return clean markdown text optimized for LLM consumption. Same reliability as fetch_url but returns only the markdown content, stripping HTML, scripts, and noise. Best for when you need the page content for analysis, summarization, or data extraction. Args: url: The URL to fetch use_cache: Whether to use cached results (default: true) wait_for: CSS selector to wait for before capturing

Input Output Examples

Name	Type	Req	Description
url	string	yes	—
use_cache	boolean	—	—
wait_for	—	—	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

fetch_url ~166

Fetch a URL with full reliability — retry, circuit breaker, cache, and anti-bot bypass. Returns both raw HTML and clean markdown. Automatically retries on failure with exponential backoff, falls back to plain HTTP if browser fetch fails, and circuit-breaks domains that are consistently down. Args: url: The URL to fetch use_cache: Whether to use cached results (default: true, TTL 1 hour) js_render: Whether to render JavaScript (default: true, disable for speed) wait_for: CSS selector to wait for before capturing (e.g., '.results-loaded')

Input Output Examples

Name	Type	Req	Description
js_render	boolean	—	—
url	string	yes	—
use_cache	boolean	—	—
wait_for	—	—	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	58
27 Jul	58
28 Jul	59
29 Jul	60
30 Jul	60
31 Jul	62
1 Aug	62
2 Aug	63
3 Aug	63