DollhouseMCP
A Free, Open Source MCP server for dynamic custom persona management with public a GitHub collection of personas, skills, templates, and other elements for AI models.
Is DollhouseMCP safe? Strong public trust posture, backed by multiple independent signals.
Compare DollhouseMCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: DollhouseMCP scores 77.4/100 (Grade B), ranked #182 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.4/10; 16% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How DollhouseMCP compares in MCP Servers
- #100 MCP Youtube 77.7 +0.3
- #101 Music Studio 77.6 +0.2
- #102 DollhouseMCP 77.4 this agent
- #103 Sec Edgar MCP 77.3 −0.1
- #104 Livetennisapi MCP 77.1 −0.3
Bars show each HVTrust score; the tick marks DollhouseMCP’s 77.4.
Where the 77.4 comes from
HVTrust dimensions vs the MCP Servers average
77.4 / 100 · 100.0% confidenceDollhouseMCP MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
59.8 / 100Supply Chain Trust
Common questions about DollhouseMCP
Does DollhouseMCP publish package provenance?
Does DollhouseMCP have an OpenSSF Scorecard?
Is DollhouseMCP actively maintained?
What license does DollhouseMCP use?
Are DollhouseMCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to DollhouseMCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain DollhouseMCP?
For maintainers
HVTrust scores DollhouseMCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/dollhousemcp)
<a href="https://hvtracker.net/agents/dollhousemcp"><img src="https://hvtracker.net/badge/dollhousemcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON