Sentinel 402

io.github.pseudowaterPublished by GitHub account pseudowaterv1.0.0Updated Oct 24, 2026

Uptime and price-honesty oracle for x402: trust status, attestations, USDC history.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

A remote MCP endpoint that reports trust status, attestations and USDC payment history for x402 services, acting as an uptime and price-honesty oracle.

What you can do
Provides trust status for x402 services, so an assistant can check whether a service is considered trustworthy before relying on it. Returns attestations associated with those services. Reports USDC payment history, giving a record of past payments. No individual tools are listed, so the exact operations are not documented in the supplied material.
When to use it
Useful when an assistant or workflow deals with x402-payable services and needs a third-party view of uptime, price honesty or payment history before trusting or paying one.
Requirements
A remote streamable HTTP endpoint; no local runtime, package, environment variables or headers are declared. The manifest declares no authentication, but the endpoint is third-party hosted, so network access to it is required.
Before you install
The server is a third-party hosted oracle, so its trust and price-honesty verdicts are only as reliable as the operator. It concerns USDC payment history, so queries may reveal which services and payments you are investigating to that third party. No authentication is declared, so do not send secrets to 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/io.github.pseudowater%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.sentinel402.verifiedky.xyz/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

28% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • 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.