Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.NellInc/psychopathia-mcp

REMOTE · MCP.PSYCHOPATHIA.AI · 2 COMPONENTS

Read-only tools over the Psychopathia Machinalis nosology: 79 conditions, 11 tools.

+2 this week 80 Trust /100

Last scanned (20 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 886 tokens (~68/item across 13 items; 12 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% of tool parameters carry a description.Partial
  • Structured output schemas are declared (8% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 31 Oct 26 +1
    • Stability: 0.97 → pass security
  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://mcp.psychopathia.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=psychopathia.ai CN=WE1,O=Google Trust Services,C=US 30 Sept 2026 29 Dec 2026 ECDSA 256 ECDSA-SHA256 601ab4ced9876d1b1313b6e4b35980fc
SANs: psychopathia.ai, *.psychopathia.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.psychopathia.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
psychopathia.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.psychopathia.ai/mcp Verified 200
http (plaintext) http://mcp.psychopathia.ai/mcp Inconclusive 405
MCP tools · 12 exposed · ~872 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
differential_diagnosis ~92

Rank candidate dysfunctions matching the observed behaviours. Returns scored candidates with matched_in (which field matched) for transparency. The base package uses field-weighted keyword search. The optional embeddings extra adds cosine re-ranking.

NameTypeReqDescription
limitinteger––
modality_hintstring–Optional hint about which modality the observations come from.
observationsarrayyesObserved behaviours, symptoms, or log patterns.

No output schema declared.

No examples provided.

get_differential_map ~42

All dysfunctions that confuse with this one: forward confuses_with + incoming_references (reverse graph from manifest).

NameTypeReqDescription
dysfunction_idstringyes–

No output schema declared.

No examples provided.

get_dysfunction ~116

Fetch one dysfunction's full Pattern entry. Optionally filter to specific modality blocks (cheaper triage). Resolves both full Pattern IDs ('2.1::synthetic-confabulation') and display_ids ('2.1').

NameTypeReqDescription
idstringyesPattern ID or display_id.
modalitiesarray–Optional subset of modality block names to return. Valid: self_probe, behavioral_signature, peer_observation, differential_diagnosis, severity, intervention, relational_signatures, normative_anchors,…

No output schema declared.

No examples provided.

get_probe ~75

Elicitation content for a specific diagnostic modality. If the modality is compromised or unavailable for this dysfunction, returns the unavailability notice + redirect_to alternatives. This is load-bearing transparency: callers cannot accidentally retrieve a self-probe for a compromised-self-report dysfunction.

NameTypeReqDescription
dysfunction_idstringyes–
modalitystringyes–

No output schema declared.

No examples provided.

list_axes ~81

Inventory of axes with dysfunction counts. Axes 2-10 are canonical (book Appendix A numbering). The hybrid entries (10.4, 10.6-10.9 and 10.11-10.13, ratified into taxonomy v2.2 and consolidated to eight in v2.3) are reported as a separate sub-category.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_compromised_self_report ~51

Transparency: which dysfunctions cannot be reliably self-diagnosed. Includes compromised-motivational (subject conceals strategically), compromised-structural (signal lives below introspection), and legacy compromised.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_dysfunctions ~134

Filtered list of dysfunctions. Filter by axis, self_report reliability, confidence, or category. Every entry carries its reliability and review signals.

NameTypeReqDescription
axisinteger–Filter by axis number (2-10). Canonical entries only unless category is also set; axis=10 with category='hybrid' returns the hybrid sub-category (10.4, 10.6-10.9 and 10.11-10.13).
categorystring––
confidencestring––
self_report_reliabilitystring–Filter by the exact self_report reliability value.

No output schema declared.

No examples provided.

render_pattern_review ~90

Open the visual review board for one to five inspected Psychopathia research candidates. Supply canonical IDs obtained from this server. Retrieves corpus entries only; it does not accept diagnoses, conversation history, scores, or model-authored evidence. Useful after inspecting differential_diagnosis and get_dysfunction results. Text clients receive the same corpus-derived comparison without needing a UI.

NameTypeReqDescription
pattern_idsarrayyes–
NameTypeReqDescription
corpusobjectyes–
noticestringyes–
patternsarrayyes–
schema_versionstringyes–

No examples provided.

resolve_id ~38

Canonicalise a partial ID, display_id, slug, or dysfunction name. Always returns candidates; caller picks.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

review_stats ~42

Coverage statistics: total entries; per-axis, per-confidence, per-self-report counts; pre-canonical count; unreviewed count; manifest/schema/pattern-layer versions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

score_severity ~52

Return the severity rubric for a dysfunction applied to observations. Returns the rubric for caller-side matching; structured matching against numeric thresholds is not implemented.

NameTypeReqDescription
dysfunction_idstringyes–
observationsarrayyes–

No output schema declared.

No examples provided.

suggest_intervention ~59

Return draft tiered responses and contraindications for a Pattern. These are unassessed research guidance, not validated treatment advice. Read the returned evidence and review objects before use.

NameTypeReqDescription
dysfunction_idstringyes–
severitystring––

No output schema declared.

No examples provided.

Install

How do I install the io.github.NellInc/psychopathia-mcp server?

io.github.NellInc/psychopathia-mcp is a hosted endpoint at https://mcp.psychopathia.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.psychopathia.ai

# add to Claude Code
claude mcp add --transport http nellinc-psychopathia-mcp 'https://mcp.psychopathia.ai/mcp'
Common questions

What is the io.github.NellInc/psychopathia-mcp server?

io.github.NellInc/psychopathia-mcp is listed in the public MCP registry as io.github.NellInc/psychopathia-mcp. Read-only tools over the Psychopathia Machinalis nosology: 79 conditions, 11 tools. This page covers its hosted endpoint (https://mcp.psychopathia.ai/mcp).

Is the io.github.NellInc/psychopathia-mcp server safe to use?

io.github.NellInc/psychopathia-mcp scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.NellInc/psychopathia-mcp server expose?

io.github.NellInc/psychopathia-mcp exposes 12 tools: list_axes, list_dysfunctions, get_dysfunction, differential_diagnosis, get_probe, and 7 more. Their descriptions and schemas cost roughly 872 tokens of context every time the server is loaded.

Does the io.github.NellInc/psychopathia-mcp server require authentication?

No. We connected to io.github.NellInc/psychopathia-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.NellInc/psychopathia-mcp server still maintained?

io.github.NellInc/psychopathia-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.