Hosting

Local stdio process

Transport

stdio

Endpoint

Local process; no hosted endpoint documented

Authentication

No credentials were configured; the tested read-only tool “search_mcp_servers” succeeded in an isolated environment. Other tools may have additional requirements.

Requirements

• Node.js 18+
• The public install config and runtime call passed; package/profile repository links differ and are recorded for review.

Setup steps

1. npx -y @mcpfinder/server@1.5.0

The server returned 4 tools in tools/list. Only “search_mcp_servers” was invoked with a synthetic read-only input and succeeded.

• search_mcp_servers

  Call this first whenever the user needs a capability you do not already have. Use it when the user mentions an external service, a database, a filesystem, a SaaS tool, or asks "can you connect to X?". Examples: "connect to postgres" -> query "postgres"; "read my Slack" -> query "slack"; "browse local files" -> query "filesystem". If results are weak, retry with a broader term. After choosing a candidate, call get_server_details before recommending or installing it.

  Parameters: query, limit, transportType, registryType, registrySource
  01
• get_server_details

  Always call this before recommending or installing a server. It returns the metadata you need to judge safety and fit: install method, transport, environment variables, source count, trust signals, warnings, and any discovered tools/capabilities. Use it to warn the user about secrets, stale projects, or weak metadata before calling get_install_config.

  Parameters: name
  02
• get_install_config

  Use this after get_server_details to generate a ready-to-paste JSON config snippet for the target client. Returns structured config, file paths, required env vars, restart guidance, and safety flags like requires_user_secrets and safe_to_autoinstall.

  Parameters: name, platform
  03
• browse_categories

  Single-call category browser for broad discovery. Call with no `category` to list all categories with counts; call with a `category` to get the highest-signal servers in that category. Prefer search_mcp_servers when the user names a concrete technology like Slack, Postgres, GitHub, or Notion; use this when discovery is domain-driven (database, filesystem, communication, security, ai, etc.).

  Parameters: category, limit
  04

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• Runtime verification covered one read-only tool call (search_mcp_servers); other listed tools were not individually exercised.
• The npm package uses mcpfinder/mcpfinder while the directory profile links mcpfinder/server; package docs identify @mcpfinder/server as the canonical package.

• The npm package uses mcpfinder/mcpfinder while the directory profile links mcpfinder/server; package docs identify @mcpfinder/server as the canonical package.

• MCP.Directory public profile

  Name, description, publisher identifier, categories, transport, tool inventory, and install configuration.

• Linked publisher repository

  Repository URL linked from the public profile; any npm repository difference is recorded separately.

• npm-declared package repository

  The npm package uses mcpfinder/mcpfinder while the directory profile links mcpfinder/server; package docs identify @mcpfinder/server as the canonical package.

• npm registry metadata

  Published package version 1.5.0 checked before launch. Registry repository: git+https://github.com/mcpfinder/mcpfinder.git. The npm package uses mcpfinder/mcpfinder while the directory profile links mcpfinder/server; package docs identify @mcpfinder/server as the canonical package.

• maintainer or vendor tool documentation

  Canonical repository checked; MCPFinder is a registry/search layer, its own tools are distinct from the downstream servers it finds.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.