ToremLabs/heuresis-mcp (ToremLabs/heuresis-mcp) is an MCP server listed on the M8ven Trust Index. It scores 58 out of 100, grade D. It declares 44 tools. No publisher has claimed this listing.

D
Caution
58/100

ToremLabs/heuresis-mcp

Exposes a Heuresis workspace to MCP clients, enabling concept mapping, ideation, and workspace management through natural language.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

ToremLabs

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: HEURESIS_ANON_KEY, HEURESIS_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes37 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

get_workspace_summary

(Legacy snapshot mode) Counts of nodes/edges/projects/ideas + a one-line overview of each project and idea. Always start here when you don't know what's in the workspace.

list_projects

(Legacy snapshot mode) Every project in the snapshot with brief, direction, lifecycle, and member count.

search_concepts

(Legacy snapshot mode) Substring search across concept labels, descriptions, tags, and partition attributes.

get_concept

(Legacy snapshot mode) One concept by id, optionally with ancestry, children, and idea memberships.

get_subtree

(Legacy snapshot mode) A node and its descendants up to a given depth.

get_project_graph

(Legacy snapshot mode) Every node + edge inside one project. Returns a graph the agent can reason over end-to-end.

list_recent_decisions

(Legacy snapshot mode) Nodes the user has explicitly resolved (validated, starred, or archived) recently.

list_concepts

List concepts in the workspace or one project. Returns id / label / status / parentId / tags up to `limit` entries (default 500). Use BEFORE making changes to learn what already exists.

list_edges

List every edge in the workspace (or restricted to a project). Filter by kind: partition / k-ref / semantic-adjacency / derived-from / imported-from.

find_concepts

Find concepts by label/substring match. Returns up to k hits, each with id, label, status.

add_concept

Create a new concept (Node). If parentId is given, the concept becomes a CHILD of that concept and a partition edge is auto-created. If parentId is omitted, the concept attaches to the project root.

update_concept

Update an existing concept's label, description, tags, partitionAttribute, rationale, or status. Only the fields provided are changed.

link_concepts

Create an edge between two concepts. kind is one of: 'k-ref' (knowledge reference), 'derived-from' (provenance link), 'semantic-adjacency' (sibling kinship). Partition (parent/child) edges are managed via add_concept / set_parent.

add_kref

Convenience: create a k-ref (knowledge reference) edge from fromId → toId. Equivalent to link_concepts with kind=k-ref.

validate_concept

Mark a concept as validated (status=validated). Optionally also overwrite `rationale`. Idempotent on already-validated nodes.

set_standing

Set a concept's STANDING — how known / proven the idea is in the wider world. `standing` ∈ 'novel' | 'emerging' | 'established' | 'unknown'. `rationale` is a one-sentence justification (saved as `standing_rationale`). Use this when classifying / judging novelty.

archive_concept

Archive a concept (status=archived). Reversible via unarchive_concept.

unarchive_concept

Revive a previously-archived concept (status=open). Idempotent on already-open nodes.

star_concept

Toggle the starred flag on a concept (user-favorite marker).

remove_concept

Hard-delete a concept and its descendants (walks the subtree via parent_id AND partition edges). Edges and project/idea memberships cascade via FK. Refuses to delete a project root node. For many at once, use remove_concepts.

remove_concepts

Bulk hard-delete: delete many concepts in one call (each cascades its own subtree). Returns per-id results. Ids already swept up in another id's cascade come back ok:false (not-found) — expected, not fatal. Pair with find_orphans for cleanup.

find_orphans

Surface concepts no normal traversal reaches, scoped to your workspace: 'projectless' (in no project — typically left behind by delete_project) and 'danglingParent' (parent_id points at a deleted node). Read-only. Clean up with remove_concepts (delete) or set_parent (re-home).

bulk_add_concepts

Create many concepts in a single atomic transaction. `items` is an array; each item carries label / description? / parentId? / projectId? / tags?. project_id is resolved per-item (explicit > inherited from parent > workspace solo project). Returns the created ids in input order.

set_parent

Re-parent an existing concept: nodeId's parent becomes newParentId (or detached when null). Updates BOTH node.parent_id AND the partition edge so the canvas tree stays in sync.

create_idea

Create a new Idea (a named grouping of concepts) with an optional color and optional starting node membership.

rename_idea

Rename an Idea.

recolor_idea

Change an Idea's color (any CSS color string).

set_idea_members

Replace an Idea's full membership with `nodeIds`. Reconciles the junction table: inserts missing pairs, deletes pairs no longer in the set. Returns added / removed counts.

add_to_idea

Add a single concept to an existing Idea (idempotent).

delete_idea

Delete an Idea. Membership rows cascade via FK; the underlying concepts are untouched.

create_project

Create a new Project (problem-with-direction) with a name and brief. Optional `direction`.

update_project

Update a project's name / brief / direction / lifecycle. Only fields provided are changed.

delete_project

Delete a project. By default its concepts are LEFT behind as orphans (find them later with find_orphans). Pass deleteNodes:true to also hard-delete every concept in the project (each cascades its subtree) so no orphans are created.

run_operator

Run an ASIT / TRIZ / Contradiction / Free / Combine / Explore operator against one concept (the anchor). Returns CANDIDATE concepts WITHOUT committing them — call `bulk_add_concepts` (or `run_operator_and_commit`) to persist. Use this when you want the agent to vet the candidates before writing. The

run_operator_and_commit

Same as `run_operator`, but immediately writes every top-level candidate as a child of the anchor with a partition edge and a provenance row stamped origin='mcp'. Use when the agent is confident the candidates should land directly on the canvas (e.g. inside an autonomous expand loop). Children-of-ch

expand_concept

Recursive Branch — expand a concept by `breadth` children at each of `depth` levels (depth*breadth ≤ 60). Commits each level immediately so the webapp shows partial results as the run progresses. Optionally takes an `angle` hint that biases the underlying EXPLORE operator. Best when the anchor has f

get_run

Fetch an async operator run by its runId. Returns { status: "running" | "done" | "error" }; when "done", the `result` field holds the operator output (candidates / committedIds). Waits up to ~8s for completion before returning, so a simple poll loop converges fast. run_operator / run_operator_and_co

// known CVEs in dependencies3 high7 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.0.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highundici@6.25.0GHSA-vxpw-j846-p89q

undici WebSocket client vulnerable to denial of service via fragment count bypass

highws@8.18.0GHSA-96hv-2xvq-fx4p

ws: Memory exhaustion DoS from tiny fragments and data chunks

lowundici@6.25.0GHSA-35p6-xmwp-9g52

undici vulnerable to HTTP response queue poisoning via keep-alive socket reuse

lowundici@6.25.0GHSA-8xcm-r25x-g524

undici vulnerable to downstream response desynchronization via retry interceptor

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretHEURESIS_ANON_KEYsb_publishable_... # project anon/publishable key (public, not a secret)
configHEURESIS_DEVICE_BASE_URL
configHEURESIS_EMAILyou@example.com # your Heuresis account email
🔐 secretHEURESIS_PASSWORDyour-account-password # secret — store it in a secrets manager
configHEURESIS_SNAPSHOTand the env var set, the server reads a JSON
configHEURESIS_SUPABASE_URLoptional: =... # defaults to the production project
configHTTPS_PROXY
configHTTP_PROXY
confighttp_proxy
confighttps_proxy
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

44/44 tools missing one or more hints — get_workspace_summary (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_projects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_concepts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +41 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.0.0 (high), undici@6.25.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Domain consistency

npm scope @heuresis doesn't match GitHub owner toremlabs

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/toremlabs/heuresis-mcp?variant=verified)](https://m8ven.ai/mcp/toremlabs/heuresis-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 3ac8ac5b51a7e6fc4728f7092d3ac055632aee61
code hash: 2d3e6808cc80416f53bb30142a0401fa1a72dbd1460c21d7ec4db98b8e9b9548
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client