mcp-registry/com.tryperspect/perspect · v1.0.0
As of 2026-10-26 23:13 UTC, the Tryperspect Perspect MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 4 minutes.
Convene a panel of expert AI personas to debate any decision from every side.
Point your MCP client at this streamable-http endpoint: https://perspect-ai-backend.onrender.com/mcp
2 of 2 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.tryperspect%2Fperspect/fixes
{
"name": "list_personas",
"description": "List the expert personas available to sit on a Perspect AI panel (id, name, discipline).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "run_debate",
"description": "Convene a panel of expert personas to debate a topic, idea, or decision from conflicting angles, then return the debate, a contradiction map (where the experts disagree), and a synthesized briefing. Optionally pass specific persona ids (see list_personas); omit to auto-select a fitting panel. Takes ~30-60s.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"topic"
],
"properties": {
"topic": {
"type": "string",
"description": "The topic, question, idea, or decision to explore."
},
"personas": {
"type": "array",
"items": {
"type": "string"
},
"description": "Optional persona ids to use (2 to 5). Omit to auto-select."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.tryperspect/perspect"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.tryperspect/perspect"}) over MCP.
run_debate ~192 tokenslist_personas ~64 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.tryperspect%2Fperspect?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.tryperspect%2Fperspect?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.tryperspect%2Fperspect.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.tryperspect%2Fperspect.svg :target: https://glimind.com/server/mcp-registry%2Fcom.tryperspect%2Fperspect?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f86a3680b3591401…, first seen 2026-10-17, included at leaf 11499 of 76,031. Version history · verify what your client received.
Compare: most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 23:13 UTC, the Tryperspect Perspect MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 4 minutes.
Tryperspect Perspect MCP server advertises 2 tools, including list_personas, run_debate.
Point your MCP client at this streamable-http endpoint: https://perspect-ai-backend.onrender.com/mcp
Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.