
SteadyFetch
io.github.carsonroell-debugPublished by GitHub account carsonroell-debugv0.1.1Updated Oct 24, 2026
Reliable web fetching for AI agents with retry, circuit breaker, caching, and anti-bot bypass
The publisher's own server: Steady
Overview
SteadyFetch is a web fetching server for AI assistants that adds retries, a circuit breaker, caching and anti-bot bypass to page retrieval.
- What you can do
- Fetch web pages on the assistant's behalf with built-in reliability handling, including retries when a request fails and a circuit breaker to stop repeated failing calls. Cache fetched content so repeated requests can be served without refetching. Attempt to get past anti-bot protections on sites that block automated access. No individual tools are listed in the manifest, so exact operations are not documented.
- When to use it
- Useful when an assistant needs to retrieve web content and plain fetching is unreliable, rate-limited or blocked by bot protection, and you want retries and caching handled for you.
- Requirements
- Runs either as a remote endpoint over streamable HTTP or as a local process from the steadyfetch PyPI package over stdio, which needs a Python environment. No authentication, environment variables or headers are declared. Network access is required to reach target sites.
Installation
In SourceWeft
- Open SteadyFetch in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.carsonroell-debug%2Fsteadyfetch/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"steadyfetch": {
"type": "http",
"url": "https://steadyfetch-production.up.railway.app/mcp"
}
}
}Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.
Other Steady integrations
Steady
space.steadyOfficial publisher
Steady is a remote MCP endpoint that lets an assistant keep teams and agents coordinated automatically.

Steady API Scrapers
Published by GitHub account steadyapi
Apify-hosted scrapers that let an assistant pull YouTube transcripts, Google Hotels prices, Google Ads Transparency data, Google Trends and Threads posts as…