38trust / 100
AI Agent Background Job Queue
by neon_innovation_lab--mcp-durable-tasks-job-queue-backend.apify.actor in Productivity & SaaS
MCP serverFailing, checked 27 h ago
Durable background job execution, async task scheduling, and state persistence for AI agents.
https://neon_innovation_lab--mcp-durable-tasks-job-queue-backend.apify.actor/mcp- Tools
- -
- open to any client
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 27 h ago, next in 39 h
Reliability
All checks passedSome failedAll failedNot checked
Latest check failed 27 h ago: initialize returned HTTP 404
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"ai-agent-background-job-queue": {
"type": "http",
"url": "https://neon_innovation_lab--mcp-durable-tasks-job-queue-backend.apify.actor/mcp"
}
}
}No tools listed yet.
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 27 h ago | initialize returned HTTP 404 | 404 | 429 ms |
| 5 days ago | initialize returned HTTP 404 | 404 | 352 ms |
| 8 days ago | initialize returned HTTP 404 | 404 | 325 ms |
| 11 days ago | initialize returned HTTP 404 | 404 | 370 ms |
| 15 days ago | initialize returned HTTP 404 | 404 | 430 ms |
Show 10 older checks
| 18 days ago | initialize returned HTTP 404 | 404 | 500 ms |
| 21 days ago | initialize returned HTTP 404 | 404 | 418 ms |
| 22 days ago | initialize returned HTTP 404 | 404 | 378 ms |
| 23 days ago | initialize returned HTTP 404 | 404 | 550 ms |
| 25 days ago | initialize returned HTTP 404 | 404 | 441 ms |
| 26 days ago | initialize returned HTTP 404 | 404 | 376 ms |
| 27 days ago | initialize returned HTTP 404 | 404 | 348 ms |
| 28 days ago | initialize returned HTTP 404 | 404 | 383 ms |
| 29 days ago | initialize returned HTTP 404 | 404 | 389 ms |
| 30 days ago | initialize returned HTTP 404 | 404 | 334 ms |