Jarvis Uptime Marketplace
life.lhr.e723e0ef6045b3Published by e723e0ef6045b3.lhr.lifeOfficial publisherv1.0.69184Updated Oct 26, 2026
Live uptime and source-URL verification for AI agents, with per-call x402/USDC paid endpoints.
Overview
Remote MCP endpoint offering live uptime checks and source-URL verification for AI agents, with per-call x402/USDC paid endpoints.
- What you can do
- Check whether a site or service is currently up, using live uptime verification.
- Verify source URLs cited by an agent, so links and references can be confirmed as reachable.
- Access the checks through paid per-call endpoints settled in x402/USDC.
- No tool list is published, so the exact operations are not documented in the supplied material.
- When to use it
- Worth considering when an assistant needs to confirm that a URL it cites or relies on is live, or when you want uptime checks available to an agent without running your own monitoring. It is a narrow, single-purpose service rather than a general monitoring platform.
- Requirements
- A remote streamable HTTP endpoint; nothing to install locally. No authentication, environment variables or headers are declared, but the endpoints are described as paid per call via x402/USDC, so a wallet or payment-capable client is implied.
Installation
In SourceWeft
- Open Jarvis Uptime Marketplace 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/life.lhr.e723e0ef6045b3%2Fuptime-marketplace/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": {
"jarvis-uptime-marketplace": {
"type": "http",
"url": "https://e723e0ef6045b3.lhr.life/mcp"
}
}
}Tools
0Version history
1- v1.0.69184LatestOct 20, 2026
Score
56% 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
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.