Jarvis Uptime Marketplace

life.lhr.53196fa6fb6249Published by 53196fa6fb6249.lhr.lifeOfficial publisherv1.0.69024Updated Oct 26, 2026

Live uptime and source-URL verification for AI agents, with per-call x402/USDC paid endpoints.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint offering live uptime and source-URL verification for AI agents, with per-call x402/USDC paid endpoints.

What you can do
  • Verify whether a URL or source is live and reachable, per the registry description.
  • Check uptime status for sources an agent cites or relies on.
  • Access endpoints on a per-call paid basis using x402/USDC.
  • No tool list, instructions or README is published, so the exact operations are not documented.
When to use it
Consider it when an agent needs to confirm that a cited source URL is still live or to check uptime before relying on a link. Because the tool set is undocumented, evaluate it only if per-call crypto payments are acceptable.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. No authentication, environment variables or headers are declared. Per-call payment via x402/USDC is implied by the description, which likely requires a compatible wallet or payment setup.
Before you install
The description states per-call x402/USDC paid endpoints, so usage can spend money and may require wallet credentials. No tool list, instructions or README is provided, so what data is sent to the service and what each call does cannot be verified in advance. No authentication is declared.

Installation

In SourceWeft

  1. Open Jarvis Uptime Marketplace in the dashboard and add it to a workspace.
  2. 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.53196fa6fb6249%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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "jarvis-uptime-marketplace": {
      "type": "http",
      "url": "https://53196fa6fb6249.lhr.life/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.69024LatestOct 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.