nestr-dev/nestr-mcp (nestr-dev/nestr-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 106 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

nestr-dev/nestr-mcp

MCP server that connects AI assistants like Claude to your Nestr workspace, enabling task, project, role management, and organizational insights through natural language.

→ nestr-dev/nestr-mcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

nestr-dev

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

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
🚨
Secret credentials may flow to a network call
1 flow detected: GA4_API_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 6 credentials: GA4_API_SECRET, NESTR_API_KEY, NESTR_OAUTH_CLIENT_SECRET, NESTR_OAUTH_TOKEN, OAUTH_ENCRYPTION_KEY, OPENAI_CHALLENGE_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
🔐 secretGA4_API_SECRETMeasurement Protocol API secret
configGA4_DEBUGSet to true to validate events without recording
configGA4_MEASUREMENT_IDGA4 Measurement ID (e.g., G-XXXXXXXXXX)
configGTM_IDGoogle Tag Manager container ID for landing page -
configMCPCAT_ENABLE_REPLAYEnable session replay (default: false)
configMCPCAT_PROJECT_IDMCPcat project ID (from [mcpcat.io](https://mcpcat.io))
configMCP_RESOURCE_URL
configNESTR_API_BASEhttps://app.nestr.io/api
🔐 secretNESTR_API_KEYNestr API key (full workspace access)
configNESTR_GTM_ID
configNESTR_OAUTH_CLIENT_IDOAuth client ID for hosted OAuth flow -
🔐 secretNESTR_OAUTH_CLIENT_SECRETOAuth client secret -
🔐 secretNESTR_OAUTH_TOKENOAuth token (respects user permissions)
🔐 secretOAUTH_ENCRYPTION_KEY32-byte base64 key for encrypting OAuth sessions at rest -
configOAUTH_STORAGE_DIR
🔐 secretOPENAI_CHALLENGE_TOKEN
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
deployREDIS_URL
// 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

106/106 tools missing one or more hints — nestr_help (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); nestr_diagnose (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); nestr_list_workspaces (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +103 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.

Tool test coverage

51/106 tools referenced in tests (48%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets stay with their owner

1 secret sent to a request target we could not resolve (GA4_API_SECRET → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

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 4 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 Score](https://m8ven.ai/badge/mcp/nestr-dev/nestr-mcp)](https://m8ven.ai/mcp/nestr-dev/nestr-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: fefce905000855a0d442cd463f23888be6174dd8
code hash: 0cc7c5df6db78c598191d84585dbbd544a280086f458d69c74c287ce9d64b876
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