Discovery Oracle

bot.402Published by 402.botOfficial publisherv1.0.1-betaUpdated Oct 24, 2026

Discover live agent APIs, ranked endpoints, trust, payment telemetry, and x402 surfaces.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP endpoint for discovering live agent APIs, ranked endpoints, trust signals, payment telemetry and x402 surfaces.

What you can do
Discovery Oracle is a remote MCP server that exposes no listed tools in the manifest, so its capabilities come from its description. It is presented as a way to discover live agent APIs and ranked endpoints. It also covers trust information, payment telemetry and x402 surfaces. No further detail on individual operations is provided.
When to use it
Consider it when you need to find live agent APIs or ranked endpoints, or want trust and payment telemetry around x402-style services. Because no tools or documentation are listed, confirm what it actually exposes before relying on it.
Requirements
A remote streamable HTTP endpoint at api.402.bot; no local package, environment variables or headers are declared. The manifest declares no authentication, so any account or credential needs are unconfirmed.
Before you install
The manifest lists no tools, README or instructions, so the server's actual behavior cannot be verified from this listing. It is described as covering payment telemetry and x402 surfaces, which relate to payments; treat any payment-related actions with care. No authentication is declared, so do not send secrets until you know what it accepts.

Installation

In SourceWeft

  1. Open Discovery Oracle 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/bot.402%2Fdiscovery-oracle/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": {
    "discovery-oracle": {
      "type": "http",
      "url": "https://api.402.bot/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.1-betaLatestSep 16, 2026

Score

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

    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.