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

D
Caution
51/100

bloom-mcp

MCP server for Bloom Growth that allows users to update metrics, check scorecards, and manage rocks directly from Claude.

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

⚡ 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

tbohling15

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
⚠️
Tool descriptions don’t match what handlers do
14 tools describe read intent but their handlers mutate — get_my_scorecard (line 78: execSync('op read "op://Employee/Bloom Growth/Email"', { encoding: "utf8" })); get_measurable (line 78: execSync('op read "op://Employee/Bloom Growth/Email"', { encoding: "utf8" })); list_my_measurables (line 78: execSync('op read "op://Employee/Bloom Growth/Email"', { encoding: "utf8" }))
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 1 credential: BLOOM_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes20 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_my_scorecard

Get your Bloom Growth scorecard — all measurables with their current week scores and goals.

get_measurable

Get details for a specific measurable (metric) by its ID.

list_my_measurables

List all measurables (metrics) assigned to you.

update_score

Update the value of a score by its score ID. Use get_score_history to find score IDs.

update_metric_for_week

Post or update a metric score for a specific week. Provide the measurable ID and week ID. Use get_score_history to find week IDs.

get_score_history

Get the full score history for a measurable. Returns score IDs and week IDs needed for updates.

list_meetings

List all your Level 10 (L10) meetings.

get_meeting_scorecard

Get the scorecard for a specific L10 meeting.

get_my_rocks

List your current quarterly rocks (goals).

get_meeting_todos

List open todos for a specific L10 meeting.

get_todo_notes

Get the notes/details text attached to a specific todo. Returns plain text extracted from the todo's notepad.

get_meeting_todos_with_notes

List all open todos for a meeting, each enriched with its notes text, and a single top-level link to the meeting's todo list in the current Bloom Growth UI (not the legacy per-todo links). Ideal for posting a todo digest to Slack.

get_rock

Get full details for a specific rock by ID, including status, completion percentage, and results so far.

get_user_rocks

Get rocks for a specific user by their user ID. Use get_my_rocks first to find user IDs.

update_rock

Update a rock's status, completion percentage, or title. Status values: 'OnTrack', 'OffTrack', 'Done', 'Unknown'. Completion is 0–100.

get_rock_milestones

List all milestones (plan steps) for a specific rock. Milestones are the bullet points under 'Plan & Milestones' on a rock card.

add_rock_milestone

Add a new milestone (plan step) to a rock. Milestones appear as bullet points under 'Plan & Milestones' on the rock card.

setup_credentials

Save your Bloom Growth username (email) and password locally so you don't need 1Password or env vars. Credentials are stored in ~/.bloom-mcp/credentials.json with owner-only permissions (chmod 600). Run this once to get started.

check_credentials

Show which credential source is currently active (env vars, local file, or 1Password) and confirm the connection works.

clear_credentials

Remove locally stored Bloom Growth credentials from ~/.bloom-mcp/credentials.json.

// 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.
configBLOOM_MCP_PORTTo use a different port: =9000 BLOOM_MCP_TRANSPORT=http node dist/index.js, then use that port in the address.
configBLOOM_MCP_TRANSPORTTo use a different port: BLOOM_MCP_PORT=9000 =http node dist/index.js, then use that port in the address.
🔐 secretBLOOM_PASSWORD
configBLOOM_USERNAME
// 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

20/20 tools missing one or more hints — get_my_scorecard (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_measurable (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_my_measurables (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 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.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — clear_credentials deletes at line 48 (fs.unlinkSync(CREDENTIALS_FILE))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

14 tools describe read intent but their handlers mutate — get_my_scorecard (line 78: execSync('op read "op://Employee/Bloom Growth/Email"', { encoding: "utf8" })); get_measurable (line 78: execSync('op read "op://Employee/Bloom Growth/Email"', { encoding: "utf8" })); list_my_measurables (line 78: execSync('op read "op://Employee/Bloom Growth/Email"', { encoding: "utf8" }))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

2 calls in production code run through a shell (src/index.ts:78, src/index.ts:79)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Tool description accuracy

14 tools have description/behavior mismatches: get_my_scorecard: description implies read-only but handler writes/deletes/executes; get_measurable: description implies read-only but handler writes/deletes/executes; list_my_measurables: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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 8 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/tbohling15/bloom-mcp?variant=verified)](https://m8ven.ai/mcp/tbohling15/bloom-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 796f8f1c66211213429b4c986c4adcbc104107a9
code hash: 8e508141a08ce04b2bda1f4b932f97d018c6b46f5fe6fb9984447c0e22dbd12d
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