Sentinel 402

xyz.verifiedkyPublished by verifiedky.xyzOfficial publisherv1.0.1Updated Oct 24, 2026

Independent uptime oracle for the x402 agent economy. Free probes, paid history via USDC on Base.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

An uptime oracle that lets an assistant probe endpoint availability and, for a fee, retrieve historical uptime data.

What you can do
Sentinel 402 is a remote MCP server described as an independent uptime oracle for the x402 agent economy. It offers free probes of endpoint availability and paid access to historical uptime records. The registry lists no tools, so the exact tool names and parameters are not documented here.
When to use it
Consider it when an assistant needs to check whether a service or endpoint is reachable, or to look up past uptime history for a service. It is aimed at agent-economy monitoring rather than general web search or infrastructure management.
Requirements
It runs as a remote streamable HTTP endpoint, so no local runtime or package install is needed. The manifest declares no authentication, environment variables, or headers. Paid history access is described as using USDC on Base, which implies a crypto wallet with funds on that network.
Before you install
The paid history feature involves spending USDC on Base, so a wallet and funds are needed and payments are likely irreversible. The manifest declares no authentication, so treat any data returned as unverified third-party claims. No tool list is published, so review the actual tools before relying on it.

Installation

In SourceWeft

  1. Open Sentinel 402 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/xyz.verifiedky%2Fsentinel-402/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": {
    "sentinel-402": {
      "type": "http",
      "url": "https://mcp.verifiedky.xyz/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.1LatestSep 16, 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.