X402 Osint

io.github.JienWengPublished by GitHub account JienWengv1.0.0Updated Oct 27, 2026

Pay-per-call OSINT for AI agents: username + email recon in USDC on Base via x402.

The publisher's own server: osint.foundation

Overview

AI-generated overview

Remote MCP endpoint offering pay-per-call OSINT lookups — username and email reconnaissance — paid in USDC on Base via x402.

What you can do
  • Run username reconnaissance lookups
  • Run email reconnaissance lookups
  • Each call is billed individually through the x402 payment protocol in USDC on the Base network
  • No tool list is published, so the exact lookup options are not documented in the registry entry
When to use it
Useful when an assistant needs on-demand open-source intelligence on a username or email address and you are willing to pay per query in crypto rather than hold a subscription or API key.
Requirements
A remote MCP client that can connect over SSE to the provider's endpoint, with network access to it. No authentication, environment variables or headers are declared. A crypto wallet able to pay USDC on Base through x402 is implied by the description, though the payment setup is not documented here.
Before you install
Every call is paid in USDC on Base, so usage spends real money and costs should be checked before letting an assistant call it freely. The server performs reconnaissance on usernames and email addresses, which raises privacy and lawful-use concerns; queries and the identifiers you submit go to a third-party operator. Payment details, pricing and data handling are not documented in the registry entry.

Installation

In SourceWeft

  1. Open X402 Osint in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. 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.JienWeng%2Fx402-osint/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": {
    "x402-osint": {
      "type": "sse",
      "url": "https://x402-osint.tail66f665.ts.net:8443/sse"
    }
  }
}

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.

Other Osint integrations