Add neo-x402-mcp: AI-powered web intelligence toolkit with x402 monetization

[atakanelik34]

Neo x402 MCP Server

AI-powered web intelligence toolkit with pay-per-use monetization via x402 protocol.

Tools

• web_search — Web search with AI-powered ranking
• scrape — Anti-bot web scraping with Cloudflare bypass
• pdf_analyze — PDF content analysis and summarization
• crypto_price — Real-time cryptocurrency prices
• code_review — AI-powered code review

Details

• Remote URL: https://neo.docly.work/mcp
• Transport: streamable-http
• Network: Base mainnet (eip155:8453)
• Registry: Already published to official MCP Registry (io.github.atakanelik34/neo-x402-mcp)

Repository

https://github.com/atakanelik34/neo-x402-api-server

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c2cf94c807

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Nest publisher metadata under the remote URL key

ToolHive’s extension readers expect _meta["io.modelcontextprotocol.registry/publisher-provided"]["io.github.stacklok"][<extension-key>], where for remote servers <extension-key> is remotes[0].url (see internal/serverjson/extensions.go ExtensionKey()/GetExtensions()). Here the metadata is placed directly under the namespace object, so the catalog tooling will treat this server as having no extensions (e.g., last_updated/stars won’t be read and tools/tags won’t flow through extension-aware paths).

Useful? React with 👍 / 👎.

[rdimitrov]

The feedback given by chatgpt is correct, the nesting is not what we expect, let's update and fix that 👍