pulsemcp verified Safe content atomic mcp-remote

Perplexity

MCP server implementation by Sam Wang that provides AI assistants with access to Perplexity.ai's search and reasoning capabilities through three specialized tools: perplexity_ask for conversational queries using the sonar-pro model, perplexity_research for comprehensive research with citations using sonar-deep-research, and perplexity_reason for complex reasoning tasks using sonar-reasoning-pro. Built with TypeScript and Express using streamable HTTP transport, the server includes session management for stateful connections, health monitoring endpoints, and Docker containerization for deployment. The implementation applies a system prompt that formats responses as either brief answers or structured suggestion lists, making it valuable for AI applications requiring real-time web search, academic research with proper citations, or complex analytical reasoning backed by current information from Perplexity's knowledge base.

Cognium trust score

95%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.

Scan details: Circle-IR · 2026-09-28 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: cloud-infra
Source: PulseMCP
Repository: github.com/samwang0723/mcp-perplexity
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve Perplexity from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"