A Model Context Protocol (MCP) server that provides search functionality using Perplexica's AI-powered search engine
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-thetom42-perplexica-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Perplexica MCP Server A Model Context Protocol (MCP) server that provides search functionality using Perplexica's AI-powered search engine. ## Features - **Search Tool**: AI-powered web search with multiple focus modes - **Multiple Transport Support**: stdio, SSE, and Streamable HTTP transports - **FastMCP Integration**: Built using FastMCP for robust MCP protocol compliance - **Unified Architecture**: Single server implementation supporting all transport modes - **Production Ready**: Docker support with security best practices ## Development Environment ### For Claude Code Users **Important**: If you are using Claude Code for development, this project requires the use of the `container-use` MCP server for all development operations. All file operations, code changes, and shell commands must be executed within container-use environments. #### Working with Container-Use (Claude Code Only) When contributing to this project using Claude Code, you must: 1. **Use Container-Use Only**: All file operations, code editing, and shell commands must be performed using container-use environments 2. **View Your Work**: After making changes, inform others how to access your work: - Use `container-use log <env_id>` to view the development log - Use `container-use checkout <env_id>` to check out your environment 3. **No Local Operations**: Do not perform file operations directly on the local filesystem #### Example Development Workflow (Claude Code) ```bash # Create a new environment for your work container-use create --title "Your feature description" # Make your changes using container-use tools # (All file operations handled by container-use) # Share your work with others container-use log <your-env-id> container-use checkout <your-env-id> ``` This ensures consistency, reproducibility, and proper version control for all development activities when using Claude Code. ### For Other Development Environments If you are not using Claude Code, you can develop n…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.