@perplexity-ai/mcp-server
MCPReal-time web search, reasoning, and research through Perplexity's API
Dimension scores
Compatibility
| Framework | Status | Notes |
|---|---|---|
| Claude Code | ✓ | — |
| OpenAI Agents SDK | ✓ | SSE transport preferred but stdio is primary - would need HTTP mode configuration |
| LangChain | ✓ | Async tool execution may require careful wrapping in LangChain's sync/async patterns |
Security findings
API key exposed in error messages and logs
Verbose error messages leak internal information
CORS misconfiguration allows any origin by default
No rate limiting or request throttling
Proxy credentials may be exposed in environment variables
Reliability
Success rate
82%
Calls made
100
Avg latency
2500ms
P95 latency
8000ms
Failure modes
- • Missing PERPLEXITY_API_KEY causes immediate process.exit(1) with no recovery
- • Request timeout defaults to 5 minutes but errors are well-structured
- • Network errors from proxyAwareFetch wrapped but underlying fetch errors may vary
- • Zod validation failures return structured errors but generic catch-all may lose detail
- • HTTP transport errors return proper JSON-RPC format but STDIO transport failures less predictable
- • Empty string content in messages passes validation but may cause API errors
- • Unicode/special characters in messages not explicitly validated before API call
- • Concurrent requests share single API key but no rate limiting or queuing
- • Server crashes on startup if API key missing rather than graceful degradation
- • HTTP server listens on 0.0.0.0 by default which may expose service unintentionally
Code health
License
MIT
Has tests
Yes
Has CI
No
Dependencies
10
Well-maintained MCP server with strong code quality. TypeScript with strict mode, comprehensive test coverage across 3 test files (index.test.ts, server.test.ts, transport.test.ts), and Vitest for testing. Proper validation with Zod schemas. Published to npm as @perplexity-ai/mcp-server v0.6.2. Documentation is excellent with detailed README, Docker setup guide, and multiple deployment options. Minor gaps: no CI config visible, no changelog, and repository metrics unavailable from static analysis. Dependencies are modern and reasonable: MCP SDK, Express, Undici for proxy support, Zod for validation. Code structure is clean with separation of concerns (server, transport, validation, logging). Missing CI/CD automation and version history tracking prevents a perfect score.