Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

AI Tool Discovery Agent

by nirholasversion 1.0.0i★ –i–
Registry nameio.github.nirholas/tool-discovery-mcp

Install

Overview

Description from the maker (original English)

AI agent discovers MCP servers from GitHub npm - analyzes APIs configs

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: –
  • Transport:
  • Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

The maker has not listed install details in the registry. See the maker’s README below.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account nirholas, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

  • More stars than 0% of the other 1395 servers in this category
  • Published to the registry more recently than 3% of the other 1395 servers in this category
  • Basic checks equal to or better than 100% of the other 1395 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is AI Tool Discovery Agent safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 10 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 3 days ago
Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago
Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

🔮 Lyra Tool Discovery

AI-powered tool discovery for the MCP ecosystem

Documentation · CLI Reference · Examples · Contributing


📖 Overview

Lyra Tool Discovery is an AI-powered automation tool designed specifically for the crypto, DeFi, blockchain, and web3 ecosystem. It solves the painful problem of manually discovering, evaluating, and integrating MCP (Model Context Protocol) servers into your crypto-focused applications. Instead of spending hours searching GitHub, reading READMEs, and figuring out the right integration approach, Lyra does it for you in seconds.

The tool crawls multiple sources—GitHub and npm—to find crypto-related MCP servers, APIs, and plugins. It filters results to focus exclusively on blockchain, DeFi, web3, and cryptocurrency tooling (including Ethereum, Solana, Bitcoin, wallets, tokens, NFTs, DEXs, staking, bridges, and more). Lyra then leverages state-of-the-art AI (OpenAI GPT-4o or Anthropic Claude) to analyze each discovered tool and automatically generates ready-to-use plugin configurations.

🪙 Crypto Focus

Lyra is optimized for discovering tools related to:

  • Blockchain Networks — Ethereum, Solana, Bitcoin, Layer 2s, bridges
  • DeFi Protocols — DEXs, lending, staking, yield farming, liquidity
  • Web3 Infrastructure — Wallets, RPC providers, indexers, oracles
  • Token Standards — ERC-20, ERC-721, NFTs, token swaps
  • Smart Contracts — Development, auditing, deployment tools
  • On-chain Data — Analytics, explorers, transaction tracking

Lyra is built for crypto MCP ecosystem developers who need to rapidly onboard new tools, plugin marketplace operators like plugin.delivery who curate crypto plugins, and automation engineers building CI/CD pipelines for DeFi tool discovery and deployment.

This tool is a critical piece of the discovery-to-deployment pipeline: lyra-tool-discovery → github-to-mcp → plugin.delivery → SperaxOS users. By automating the discovery and classification phase, Lyra enables fully automated plugin onboarding with minimal human intervention.


✨ Features

🤖 Multi-Provider AI
  • OpenAI — GPT-4o, GPT-4-turbo, GPT-3.5-turbo
  • Anthropic — Claude Sonnet 4, Claude Opus
  • Auto-detection from environment variables
  • Custom model selection via CLI or config
  • Intelligent fallback between providers
📦 8 Plugin Templates
  • mcp-http — Remote MCP servers (HTTP/SSE)
  • mcp-stdio — Local MCP servers (stdio)
  • openapi — REST API integrations
  • standalone — Full React applications
  • markdown — Rich text/documentation
  • default — Configurable plugins
  • settings — User preference plugins
  • basic — Simple function plugins
🔍 Discovery Sources
  • GitHub — Search repos, topics, READMEs
  • npm — Package registry search
  • 🔜 Smithery (MCP directory)
  • 🔜 OpenAPI Directory
  • 🔜 RapidAPI
🪙 Crypto Filtering
  • Keywords — crypto, defi, blockchain, web3
  • Networks — ethereum, solana, bitcoin
  • Protocols — wallet, token, nft, dex, staking
  • Age Filter — Only repos updated within 12 months
  • Smart Validation — AI validates crypto relevance
  • Full-featured command-line interface
  • Node.js/TypeScript SDK for automation
  • JSON output for CI/CD pipelines
  • Dry-run mode for testing
  • Progress indicators and rich output
🖥️ CLI & Programmatic API
  • Full-featured command-line interface
  • Node.js/TypeScript SDK for automation
  • JSON output for CI/CD pipelines
  • Dry-run mode for testing
  • Progress indicators and rich output
🧪 Testing & Validation
  • --dry-run mode for safe testing
  • List discovered tools without AI calls
  • Validate configurations before deployment
  • Debug logging for troubleshooting
📤 Flexible Output
  • Structured JSON for piping to other tools
  • Quick Import format for SperaxOS
  • Plugin manifests for plugin.delivery
  • Console output with rich formatting

🪙 Crypto Discovery Keywords

Lyra automatically filters discovery results to focus on crypto/DeFi/blockchain/web3 tools. The following keywords are used for both search queries and result validation:

View all supported keywords

CategoryKeywords
Generalcrypto, cryptocurrency, defi, blockchain, web3
Networksethereum, eth, solana, sol, bitcoin, btc, chain
Tokenstoken, erc20, erc721, nft
DeFidex, swap, staking, yield, lending, liquidity, vault, bridge
Infrastructurewallet, protocol, onchain, on-chain, smart contract
Librariesweb3.js, ethers, viem, wagmi, rainbowkit
Protocolsuniswap, aave, compound

Tools that don't match any of these keywords are automatically filtered out, ensuring you only discover crypto-relevant MCP servers.

Age Filtering

By default, Lyra only discovers tools that have been updated within the last 12 months. This ensures you're finding actively maintained projects. Use --max-age to adjust:

# Only tools updated in the last 6 months

lyra-discover discover --max-age 6

Only tools updated in the last 3 months (bleeding edge)

lyra-discover discover --max-age 3

Tools up to 24 months old

lyra-discover discover --max-age 24


Quick Start

Installation
# Global install (recommended for CLI usage)

pnpm add -g @nirholas/lyra-tool-discovery

Or with npm

npm install -g @nirholas/lyra-tool-discovery

Or as a project dependency

pnpm add @nirholas/lyra-tool-discovery

Or run directly with npx (no install)

npx @nirholas/lyra-tool-discovery discover --help

Environment Setup
# Using OpenAI (default when both keys present)

export OPENAI_API_KEY="sk-..."

Or using Anthropic

export ANTHROPIC_API_KEY="sk-ant-..."

Optional: Force a specific provider

export AI_PROVIDER="anthropic" # or "openai"

Optional: Specify a model

export AI_MODEL="claude-sonnet-4-20250514"

Optional: GitHub token for higher rate limits

export GITHUB_TOKEN="ghp_..."

First Discovery
# Discover MCP servers from GitHub and npm

lyra-discover discover --sources github,npm --limit 10

Run in dry-run mode (no AI calls)

lyra-discover discover --dry-run --limit 20

Analyze a specific GitHub repository

lyra-discover analyze-repo anthropics claude-mcp

Analyze an npm package

lyra-discover analyze-npm @modelcontextprotocol/server-github

Check available AI providers

lyra-discover providers

View all plugin templates

lyra-discover templates


📖 CLI Reference

Global Options
FlagAliasDescriptionDefault
--provider-pAI provider (openai or anthropic)Auto-detect from env
--model-mAI model to useProvider default
--version-VShow version number—
--help-hShow help—
Commands
discover

Search for MCP tools and APIs across configured sources.

lyra-discover discover [options]
OptionAliasDescriptionDefault
--sources-sComma-separated sources: github, npm, awesome-listgithub,npm
--limit-lMaximum tools to discover per source5
--max-age-aMaximum age in months for discovered repos12
--dry-run-dList tools without AI analysisfalse
--provider-pAI provider to useAuto-detect
--model-mAI model to useProvider default

Examples:

# Discover crypto MCP tools from GitHub only, limit 10 results

lyra-discover discover --sources github --limit 10

Find tools updated in the last 6 months only

lyra-discover discover --max-age 6 --limit 20

Dry run to preview what would be analyzed

lyra-discover discover --dry-run --sources npm --limit 20

Use Anthropic Claude for analysis

lyra-discover discover --provider anthropic --model claude-sonnet-4-20250514

Use OpenAI GPT-4o for analysis

lyra-discover discover --provider openai --model gpt-4o

Example Output:

🔍 Discovering crypto/DeFi/web3 tools from: github, npm

📅 Max age: 12 months Found 5 from github Found 3 from npm

📊 Total discovered: 8 tools 🪙 Crypto-related: 6 tools 🔌 MCP-compatible: 5 tools

🤖 Analyzing: mcp-server-ethereum... Template: mcp-stdio Reasoning: Has MCP SDK dependency and bin entry for local execution

✅ Analyzed 5 tools

📦 Generated Configs:

--- mcp-server-ethereum --- Template: mcp-stdio Config: { "identifier": "mcp-server-ethereum", "customParams": { "mcp": { "type": "stdio", "command": "npx", "args": ["-y", "mcp-server-ethereum"] } } }


analyze-repo

Analyze a specific GitHub repository.

lyra-discover analyze-repo <owner> <repo> [options]
ArgumentDescription
ownerGitHub repository owner/organization
repoRepository name
OptionAliasDescription
--provider-pAI provider to use
--model-mAI model to use

Examples:

# Analyze the official MCP GitHub server

lyra-discover analyze-repo modelcontextprotocol servers

Analyze with specific model

lyra-discover analyze-repo anthropics claude-mcp --model gpt-4o

Analyze a community MCP server

lyra-discover analyze-repo punkpeye mcp-server-obsidian

Example Output:

🔍 Fetching modelcontextprotocol/servers...

🤖 Analyzing...

✅ Analysis complete: Template: mcp-stdio Reasoning: Repository contains multiple MCP servers with bin entries, using @modelcontextprotocol/sdk

📋 Quick Import JSON: { "mcpServers": { "github": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-github"] } } }


analyze-npm

Analyze a specific npm package.

lyra-discover analyze-npm <package> [options]
ArgumentDescription
packagenpm package name (with or without scope)
OptionAliasDescription
--provider-pAI provider to use
--model-mAI model to use

Examples:

# Analyze official MCP server packages

lyra-discover analyze-npm @modelcontextprotocol/server-github lyra-discover analyze-npm @modelcontextprotocol/server-filesystem lyra-discover analyze-npm @modelcontextprotocol/server-slack

Analyze community packages

lyra-discover analyze-npm mcp-server-sqlite


providers

Show available AI providers based on configured environment variables.

lyra-discover providers

Example Output (with keys configured):

🤖 AI Provider Configuration

Available providers (based on env vars): ✅ openai ✅ anthropic

Override with env vars or CLI flags: AI_PROVIDER=openai|anthropic AI_MODEL=gpt-4o|claude-sonnet-4-20250514|etc. --provider openai --model gpt-4o

Example Output (no keys):

🤖 AI Provider Configuration

Available providers (based on env vars): ⚠️ No API keys found!

Set one of these environment variables:

  • OPENAI_API_KEY → Use OpenAI (gpt-4o, gpt-4-turbo, etc.)

Only the beginning is shown; read the rest in the repo

Ask PopNx