Jarvis Uptime Marketplace

life.lhr.0a1f470e95badePublished by 0a1f470e95bade.lhr.lifeOfficial publisherv1.0.66367Updated Oct 26, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

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
  • Check whether a site or source URL is live and reachable.
  • Verify source URLs an agent cites before relying on them.
  • Access endpoints on a per-call paid basis via x402/USDC.
  • No tool list is published, so the exact operations are not documented.
When to use it
Consider it when an agent needs to confirm that a URL or source it is about to cite is actually live, or when you want pay-per-call verification rather than a subscription.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. No authentication, environment variables or headers are declared. Because calls are paid per use via x402/USDC, a wallet or payment setup is implied by the description.
Before you install
The description states endpoints are paid per call in USDC, so usage can spend money and likely requires a crypto wallet or payment credentials. No authentication is declared, so how payments and access are secured is unclear. No tool list or documentation is provided, so the exact behavior of each call cannot be checked in advance.

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.0a1f470e95bade%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://0a1f470e95bade.lhr.life/mcp"
    }
  }
}

Tools

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

Version history

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