io.github.mlartab/agentwebintel
io.github.mlartab/agentwebintel
Is the io.github.mlartab/agentwebintel MCP server down? Yes. It has given no valid answer since 2026-11-11: not found (HTTP 404).
Proxy-rotated web scraping and cross-platform intelligence for AI agents.
not found down since 2026-11-11 · probed 2026-11-14 · unchanged since 2026-11-13 · HTTP 404
Streamable HTTP error: Error POSTing to endpoint: {"status":"error","code":404,"message":"Application not found","request_id":"E1_XKWOuSOuUKasAN8N_Fg"}- Endpoint
- https://agentwebintel.up.railway.app/mcp (streamable-http)
- Host
- agentwebintel.up.railway.app
- Repository
- https://github.com/mlartab/marketplace-service-template
- Registry
- active, updated 2026-10-18 · registry entry
- Changes
- 3 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention intelligence or scraping.
- Agentic News ai.agentic-news/mcp · needs auth
- ai.agentberg/agentberg · alive
- ai.astrofabric/mcp · not MCP
- ai.bassethound/bassethound · needs auth
- Bezal — Local Business Intelligence for AI Agents ai.bezal/local-commerce · alive
- BidDeed MCP ai.biddeed/biddeed-mcp · needs auth
- Bowmark web data: LinkedIn, Amazon, YouTube, Reddit, Airbnb, Instagram ai.bowmark/bowmark · alive
- China Marketing AI Intelligence MCP ai.chinamarketing/intelligence · needs auth
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-11 11:31 | not found | ||||
| 2026-10-25 21:19 | alive | 418 ms | 2 | 353 | 186 |
| 2026-10-18 08:45 | alive | 534 ms | 2 | 186 |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-11-11, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.