Jarvis Uptime Marketplace

life.lhr.d0a14f831f92a5Published by d0a14f831f92a5.lhr.lifeOfficial publisherv1.0.66360Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated 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 URL is currently reachable and confirm that a source URL resolves.
  • Verify source links an agent cites before relying on them.
  • Access endpoints on a per-call paid basis through x402/USDC payment.
  • No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Consider it when an assistant needs to confirm that a URL or cited source is live before using it, and you are prepared to pay per call in USDC.
Requirements
A remote streamable HTTP endpoint; no local package, environment variables or headers are declared. No authentication is declared, but the endpoints are described as paid per call via x402/USDC, so a wallet or payment setup is implied.
Before you install
Calls are described as paid per call in USDC, so usage can spend real funds; set spending limits before connecting. The server is remote and unauthenticated, so requests and the URLs you submit go to a third party. No tool list or documentation is provided, so behavior cannot be reviewed 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.d0a14f831f92a5%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://d0a14f831f92a5.lhr.life/mcp"
    }
  }
}

Tools

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

Version history

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