Server data from the Official MCP Registry
Carry your Phaedo cognitive fingerprint into any MCP client: injection, consults, escalation.
Carry your Phaedo cognitive fingerprint into any MCP client: injection, consults, escalation.
The MCP server implements a cognitive fingerprint protocol with reasonable security architecture. Authentication is absent by design (it operates over stdio and relies on process-level isolation), which is appropriate for an MCP server. The main concerns are moderate-severity code quality issues around input validation and error handling, combined with the sensitive nature of the data being processed (personal behavioral profiles). The server appropriately avoids exfiltration and unsafe operations, but input validation could be more comprehensive. Supply chain analysis found 1 known vulnerability in dependencies (0 critical, 1 high severity). Package verification found 1 issue.
3 files analyzed · 9 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-phaedo-labs-phaedo-mcp": {
"args": [
"-y",
"phaedo-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
Phaedo learns how you think — communication style, working style, decision pattern — into a portable, user-owned cognitive fingerprint, and carries it to any AI tool. This repo is the open half of that system:
spec/ — Anamnesis (formerly "Phaedo Protocol"), the open
cognitive-fingerprint standard: machine-readable JSON Schemas (fingerprint
layers, consultation request/response, deference policies, receipts) + the
conformance suite.docs/protocol/ — the Anamnesis spec (v0.1), the MCP binding, and accepted
proposals.mcp/ — the reference MCP server (phaedo-mcp on npm): injects your
fingerprint at session start and answers agent consultations — an agent at a
decision point can ask "would my human proceed here?" and get a calibrated
proceed / clarify / escalate / decline signal (or an honest abstain), gated by
user-authored deference policies, with an encrypted on-device audit trail. On a
blocking signal it can escalate to your paired phone in real time for a live
approve / deny / modify, and your overrides teach the act-as-me channel —
how you want delegated work handled, not just how you work yourself.npx phaedo-mcp # run the server over stdio
Or wire it into Claude Desktop / Cursor / Claude Code automatically:
npm install -g phaedo-mcp
cd "$(npm root -g)/phaedo-mcp" && npm run setup
Out of the box it serves a sample fingerprint, so every tool works immediately.
Your real fingerprint comes from the Phaedo app — currently in private beta
(phaedo.so) — learned on-device from your actual
usage; pair with npm run pair. See
mcp/README.md for the full guide (pairing, policies, receipts,
the agreement metric).
insufficient_signal, not a confident guess.The learning pipeline that builds fingerprints (conversation capture, on-device extraction models) is Phaedo's proprietary side. This repo is everything a client, agent, or independent producer needs to consume and interoperate: the spec, the schemas, and a complete reference server.
Apache-2.0. The Phaedo name and logo are trademarks; see phaedo.so.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.