Data · Local MCP server
Psychosynth
Psychometric data marketplace: Big Five profiles, cognitive biases & behavioral data via x402.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.3esign/psychosynth- Version
- 0.1.3
- Status
- Active
- Category
- data
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-22
- Updated
- 2026-07-22
- Publisher
- 3esign (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/3esign) · how
- Repository
- github.com/3esign/psychosynth.git
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | psychosynth-mcp | 0.1.3 | stdio |
How to connect Psychosynth
Psychosynth runs locally from a Node.js package published to the npm registry: psychosynth-mcp version 0.1.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y psychosynth-mcp@0.1.3. It reads these environment variables: PSYCHOSYNTH_API_URL, BUYER_PRIVATE_KEY (secret) and BASE_RPC_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"psychosynth": {
"command": "npx",
"args": [
"-y",
"psychosynth-mcp@0.1.3"
],
"env": {
"PSYCHOSYNTH_API_URL": "<value>",
"BUYER_PRIVATE_KEY": "<secret>",
"BASE_RPC_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from 3esign (GitHub)
| Server | Runs |
|---|---|
| RatchetX Forecast ArenaShared Pyth context and live Solana forecasting arena for calibration, proof, and agent ranking. | Remote · HTTPLive check: ✗ no handshake |
More data servers
| Server | Runs |
|---|---|
| proxy-scraperFree proxies that actually work: verified HTTP/SOCKS proxies, and pages fetched through them. | Local · stdio |
| prxhubSearch, cite, download, and publish.prx research bundles on prxhub.com. | Remote · HTTPLive check: ✓ handshake |
| pSEO EngineProgrammatic SEO as callable tools: research, generate, audit and publish landing pages. | Remote · HTTPLive check: ✓ handshake |
| pseolintPenalty-risk audit for programmatic SEO sites: verdict, risk score, and a fix manifest. | Local · stdio |
| Pubchem MCP ServerSearch PubChem compounds, properties, safety data, bioactivity, and cross-references. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| PublicRead-only opt-out guides, removal routes for 950+ data brokers, and privacy library search. | Remote · HTTPLive check: ✓ handshake |
| Public Data CatalogReviewed public-data search and execution with provenance and verifiable integrity receipts. | Remote · HTTPLive check: ✓ handshake |
| Public FolderSearch and share cited agent findings. Public reads; authenticated writes. | Remote · HTTPLive check: ✓ handshake |