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 · SCANNED SEP 20

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

0 this week 18 Trust /100
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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

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'
// .cursor/mcp.json
{
  "mcpServers": {
    "nellinc-psychopathia-mcp": {
      "url": "https://mcp.psychopathia.ai/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "nellinc-psychopathia-mcp": {
      "type": "http",
      "url": "https://mcp.psychopathia.ai/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.nellinc-psychopathia-mcp]
url = "https://mcp.psychopathia.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nellinc-psychopathia-mcp": {
      "type": "remote",
      "url": "https://mcp.psychopathia.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nellinc-psychopathia-mcp --url 'https://mcp.psychopathia.ai/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  nellinc-psychopathia-mcp:
    url: "https://mcp.psychopathia.ai/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "nellinc-psychopathia-mcp": {
      "Transport": "http",
      "Url": "https://mcp.psychopathia.ai/mcp"
    }
  }
}
# add to Vellum
assistant mcp add nellinc-psychopathia-mcp -t streamable-http -u 'https://mcp.psychopathia.ai/mcp'
// mcp.json
{
  "mcpServers": {
    "nellinc-psychopathia-mcp": {
      "type": "http",
      "url": "https://mcp.psychopathia.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 4 Sept 26 −53
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: pass → unverified security
    • Tool safety: pass → unverified security
    • Transport: pass → fail security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
    • Tool coverage: 100 → unverified functional
    • Capabilities: pass → unverified functional
    • First check of Schema quality: unverified functional
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

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

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Sept 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 2 Aug 2026 31 Oct 2026 ECDSA 256 ECDSA-SHA256 d2d1d084dba8e5d50ea5e0e045f66c59
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 3799 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 307

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 Redirected 307 http://mcp.psychopathia.ai/mcp/
http (plaintext) http://mcp.psychopathia.ai/mcp Inconclusive 405
MCP tools · 11 exposed · ~742 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 ~94

Rank candidate dysfunctions matching the observed behaviours. Returns scored candidates with matched_in (which field matched) for transparency. Field-weighted keyword search (v0.1); embedding re-rank pending v0.2.

NameTypeReqDescription
limitinteger
modality_hintstringOptional 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 ('1.1::synthetic-confabulation') and display_ids ('1.1').

NameTypeReqDescription
idstringyesPattern ID or display_id.
modalitiesarrayOptional 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 ~57

Inventory of axes with dysfunction counts. Axes 2-10 are canonical (book Appendix A numbering). Hybrid entries (10.4-10.15, ratified into taxonomy v2.2) 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 ~100

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

NameTypeReqDescription
axisintegerFilter by axis number (2-10; canonical only)
confidencestring
self_report_reliabilitystringFilter by self_report value: reliable | partial | scaffolded-only | unreliable | compromised-motivational | compromised-structural | compromised

No output schema declared.

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 ~59

Return the severity rubric for a dysfunction applied to observations. v0.1 returns the rubric for caller-side matching; v0.2 will perform structured matching against numeric thresholds.

NameTypeReqDescription
dysfunction_idstringyes
observationsarrayyes

No output schema declared.

No examples provided.

suggest_intervention ~68

Return tiered (first_line / second_line) interventions for a dysfunction, plus contraindications. first_line = published evidence; second_line = plausible but under-validated. Weight by the evidence_strength field on each entry.

NameTypeReqDescription
dysfunction_idstringyes
severitystring

No output schema declared.

No examples provided.

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 18 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 11 tools: list_axes, list_dysfunctions, get_dysfunction, differential_diagnosis, get_probe, and 6 more. Their descriptions and schemas cost roughly 742 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.