Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"perspective": {
"url": "https://getperspective.ai/mcp",
"type": "http"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Forms are costing you business. An AI concierge turns them into conversations.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
Local-first AI memory with knowledge graphs and hybrid search. 17+ AI tools via MCP. Free.
MCP server for monday.com integration.
MCP Security Weekly
Get CVE alerts and security updates for ai.getperspective/mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Forms are costing you business. An AI concierge turns them into conversations.
MCP server for Perspective AI. An AI Concierge replaces static forms with adaptive AI conversations that understand real situations, structure key information automatically, and trigger the right next step.
Rigid forms cause drop-off, weaken qualification, and strip away context. Perspective uses adaptive AI to capture structured data and trigger automation, so you understand what truly matters to your customers and can make decisions with conviction.
Once connected, your AI assistant can design conversation agents, analyze conversations, deploy embeds, and automate follow-ups directly from Claude Desktop, Claude Code, Cursor, or any MCP-compatible client. Try prompts like:
Design a Concierge that qualifies pricing-page leads by budget and timeline.
Why are people abandoning my lead-capture concierge this week?
Whenever a conversation scores above 80 on trust, push it to HubSpot and ping #sales in Slack.
See Use cases for the full workflow and Available tools for the tool surface.
Add the MCP URL to your client and complete a one-time browser sign-in. Tokens stay out of config files; every connected app shows up under Settings → Connected Apps in your workspace, and you can revoke access anytime.
The MCP URL is the same for everyone:
https://getperspective.ai/mcp
claude mcp add --transport http perspective https://getperspective.ai/mcp
Add to your mcp.json:
{
"mcpServers": {
"perspective": {
"type": "http",
"url": "https://getperspective.ai/mcp"
}
}
}
Open the Add custom connector modal and fill:
| Field | Value |
|---|---|
| Name | Perspective AI |
| Remote MCP server URL | https://getperspective.ai/mcp |
Click Add, then complete the OAuth browser flow. (Manual path: Customize → Connectors → Add custom connector. See Anthropic's guide. Available on Free, Pro, Max, Team, and Enterprise plans.)
Stdio-only clients can use mcp-remote, which discovers OAuth metadata automatically:
{
"mcpServers": {
"perspective": {
"command": "npx",
"args": ["mcp-remote", "https://getperspective.ai/mcp"]
}
}
}
The first time you call a Perspective tool, your client opens a browser window to complete OAuth. Subsequent requests reuse the token.
If your client doesn't support OAuth or you'd rather authenticate with a long-lived token, generate one at Perspective AI Settings → MCP.

perspective.mcpbclaude mcp add perspective --transport http https://getperspective.ai/mcp --header "Authorization: Bearer YOUR_TOKEN"
Add to your mcp.json:
... [View full README on GitHub](https://github.com/Perspective-AI/mcp#readme)