Home › Servers › Search & Web Data › x402 Endpoint Search
x402 Endpoint Search MCP server
x402 Endpoint Search is Gadgethumans's MCP server in the official registry (com.gadgethumans/x402-discovery). Declared transport: stdio (local, npm).
| Transport | stdio (local, npm) |
|---|---|
| Auth | No secrets declared in registry entry |
| Registry name | com.gadgethumans/x402-discovery · 1.0.2 |
| Source | https://registry.modelcontextprotocol.io/v0.1/servers/com.gadgethumans%2Fx402-discovery/versions/latest |
| Remote endpoints | None declared |
| Data source | Official MCP Registry |
| Kind | Vendor |
| GitHub stars | No public GitHub repository on this listing. |
| Date checked | 2026-11-09 |
Install
Configs are generated only from packages and remotes on the registry entry. Empty optional flags are listed instead of inserted. Nothing is added that the entry does not declare.
Local package (npm)
{
"mcpServers": {
"x402-endpoint-search": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}{
"mcpServers": {
"x402-endpoint-search": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}{
"servers": {
"x402-endpoint-search": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}{
"mcpServers": {
"x402-endpoint-search": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}claude mcp add x402-endpoint-search -- npx -y [email protected]
FAQ
What transport does x402 Endpoint Search use?
stdio (local, npm).
What credentials are declared for x402 Endpoint Search?
No secrets declared in registry entry.
When was this checked, and what is the source?
These facts were checked on 2026-11-09. Registry name: com.gadgethumans/x402-discovery. Source: https://registry.modelcontextprotocol.io/v0.1/servers/com.gadgethumans%2Fx402-discovery/versions/latest.
Category hub: Search & Web Data. Client indexes: Claude, Cursor, VS Code. This listing is in The MCP Vault until it graduates.
Similar servers
Paid listings (Sponsored, then Featured) appear first in every list, marked Advertisement. Organic listings follow, sorted by GitHub stars. Sorted by GitHub stars as of 2026-11-09. Servers with no public GitHub repo follow, in alphabetical order.
Fetch (reference)
Reference server that downloads a web page and converts it into text/markdown an LLM can read.
stdio (local, pypi)
★ 91,889 GitHub stars · 2026-11-09
Apify
Runs ready-made scrapers and crawlers (Actors) from the Apify Store to pull data from websites.
Streamable HTTP (remote)
★ 15,410 GitHub stars · 2026-11-09
Firecrawl
Scrapes and searches the web via Firecrawl, returning clean page content for LLMs.
Streamable HTTP (remote), stdio (local, npm)
Connection Confirmed · 2026-11-09 · 3 tools · HTTP
★ 7,788 GitHub stars · 2026-11-09
Exa
Gives agents Exa-powered web search, page content retrieval and multi-step research.
Streamable HTTP (remote)
Connection Confirmed · 2026-11-09 · 2 tools · HTTP
★ 5,219 GitHub stars · 2026-11-09
Tavily
Local server that runs Tavily web searches and content extraction for agents.
stdio (local, npm)
★ 2,481 GitHub stars · 2026-11-09
Brave Search
Local server that queries the Brave Search API for web, image, video and news results.
stdio (local, npm)
★ 1,565 GitHub stars · 2026-11-09