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

Back to MCP Trust IndexM8ven
C
Caution
74/100

trigsight

Enables verification of portfolio claims by resolving citations to exact supporting sentences at build time, providing read-only tools to list work, find evidence, check stack mentions, and read case studies while failing the build on any unverifiable claim.

→ Raghu23-dev/trigsight· listed on glama

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

Raghu23-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: AI_GATEWAY_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Tests do not pass
Either the test suite is broken or the code regressed. Either way the published behaviour can’t be verified by the publisher’s own tests.
🔐
You'll be asked for 3 credentials: AI_GATEWAY_API_KEY, CHAT_API_KEY, UPSTASH_VECTOR_REST_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.
🔐 secretAI_GATEWAY_API_KEYNo credentials needed. Without the chat endpoint returns the
configAI_GATEWAY_MODEL
🔐 secretCHAT_API_KEY
configCHAT_BASE_URL
configCHAT_MODEL
🔐 secretUPSTASH_VECTOR_REST_TOKEN
configUPSTASH_VECTOR_REST_URL
// quality suggestions

All four hints declared on every tool

4/4 tools missing one or more hints — list_work (missing: destructiveHint, idempotentHint); find_evidence (missing: destructiveHint, idempotentHint); check_stack (missing: destructiveHint, idempotentHint), +1 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

3/4 tools referenced in tests (75%)

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

Tests pass

npm test failed — tests do not pass

Make sure npm test runs cleanly. Common cause: missing build step or missing env vars.

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Secrets stay with their owner

1 secret sent to a request target we could not resolve (AI_GATEWAY_API_KEY → 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 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/raghu23-dev/trigsight?variant=verified)](https://m8ven.ai/mcp/raghu23-dev/trigsight)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 6593ee45bb710d4339368606c3e8fa385186e4f4
code hash: aff13b76fb066ef5b3020fa2d3f21e7379269e9c267a29529b18dd808c39d2ca
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