Emmamind MCP Server

@emmamind/emmamind-mcp npm v1.0.1

Published by @emmamind — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

EmmaMind MCP stdio adapter — maps emmamind.com REST API to MCP tools

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 98/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 2 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 55

Each tool and what it can reach — statically extracted from the published source.

  • emmamind_ai_providers_statusno sensitive capability
  • emmamind_capabilitiesno sensitive capability
  • emmamind_categories_createno sensitive capability
  • emmamind_categories_deleteno sensitive capability
  • emmamind_categories_getno sensitive capability
  • emmamind_categories_listno sensitive capability
  • emmamind_categories_updateno sensitive capability
  • emmamind_editor_images_uploadno sensitive capability
  • emmamind_healthno sensitive capability
  • emmamind_ideas_createno sensitive capability
Show 45 more tools ↓
  • emmamind_ideas_create_with_user_choiceno sensitive capability
  • emmamind_ideas_deleteno sensitive capability
  • emmamind_ideas_enrich_from_notesno sensitive capability
  • emmamind_ideas_getno sensitive capability
  • emmamind_ideas_link_duplicateno sensitive capability
  • emmamind_ideas_listno sensitive capability
  • emmamind_ideas_relations_createno sensitive capability
  • emmamind_ideas_relations_deleteno sensitive capability
  • emmamind_ideas_relations_listno sensitive capability
  • emmamind_ideas_relations_updateno sensitive capability
  • emmamind_ideas_search_similarno sensitive capability
  • emmamind_ideas_updateno sensitive capability
  • emmamind_meta_defaultsno sensitive capability
  • emmamind_meta_enumsno sensitive capability
  • emmamind_projects_createno sensitive capability
  • emmamind_projects_deleteno sensitive capability
  • emmamind_projects_getno sensitive capability
  • emmamind_projects_listno sensitive capability
  • emmamind_projects_updateno sensitive capability
  • emmamind_skill_nodes_createno sensitive capability
  • emmamind_skill_nodes_deleteno sensitive capability
  • emmamind_skill_nodes_updateno sensitive capability
  • emmamind_skill_trees_apply_draftno sensitive capability
  • emmamind_skill_trees_bulk_updateno sensitive capability
  • emmamind_skill_trees_createno sensitive capability
  • emmamind_skill_trees_deleteno sensitive capability
  • emmamind_skill_trees_expandno sensitive capability
  • emmamind_skill_trees_getno sensitive capability
  • emmamind_skill_trees_graphno sensitive capability
  • emmamind_skill_trees_importno sensitive capability
  • emmamind_skill_trees_listno sensitive capability
  • emmamind_skill_trees_planno sensitive capability
  • emmamind_skill_trees_resolve_nodeno sensitive capability
  • emmamind_skill_trees_satellite_log_createno sensitive capability
  • emmamind_skill_trees_subtree_importno sensitive capability
  • emmamind_skill_trees_updateno sensitive capability
  • emmamind_work_logs_appendno sensitive capability
  • emmamind_work_logs_attachments_addno sensitive capability
  • emmamind_work_logs_attachments_deleteno sensitive capability
  • emmamind_work_logs_content_images_addno sensitive capability
  • emmamind_work_logs_createno sensitive capability
  • emmamind_work_logs_deleteno sensitive capability
  • emmamind_work_logs_getno sensitive capability
  • emmamind_work_logs_listno sensitive capability
  • emmamind_work_logs_updateno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.1 latest A 98/100 0 1.13.0 2026-09-08

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/emmamind-emmamind-mcp/badge.svg)](https://mcptrustchecker.com/registry/emmamind-emmamind-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/emmamind-emmamind-mcp"><img src="https://mcptrustchecker.com/registry/emmamind-emmamind-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/emmamind-emmamind-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @emmamind/emmamind-mcp --online

Use the free API → How scoring works

More in Other