Back to MCP Trust Indexm8ven
C
Warning
74/100
2 days ago

testlookup

Local-first test failure intelligence for CI pipelines and QA teams. Turn raw automated test results into actionable failure intelligence and release-risk signals -- locally, offline, and through API / CLI / UI / MCP.

→ anandtopu/testlookup· listed on github_code

Warning. Serious findings were identified. Review the full report before connecting. 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

anandtopu

Source: github_code

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

GitHub

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
3 flows detected: WEBHOOK_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 9 credentials: TESTLOOKUP_TOKEN, TESTLOOKUP_API_KEY, ADMIN_PASSWORD, SERVICE_PASSWORD, TESTLOOKUP_PASSWORD, MINIO_ACCESS_KEY, MINIO_SECRET_KEY, WEBHOOK_SECRET, POSTGRES_PASSWORD
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.
configPLAYWRIGHT_BASE_URL
configTESTLOOKUP_BRANCH
configTESTLOOKUP_BUILD
configTESTLOOKUP_COMMIT
configTESTLOOKUP_PROJECT_ID
🔐 secretTESTLOOKUP_TOKEN
configTESTLOOKUP_URL
configVITE_PROXY_TARGET
🔐 secretTESTLOOKUP_API_KEY
configTESTLOOKUP_LAUNCH
configADMIN_EMAIL
configADMIN_USERNAME
configADMIN_FULL_NAME
🔐 secretADMIN_PASSWORD
configSERVICE_USERNAME
🔐 secretSERVICE_PASSWORD
configSERVICE_EMAIL
configSERVICE_FULL_NAME
configTESTLOOKUP_FRONTEND
configTESTLOOKUP_USER
🔐 secretTESTLOOKUP_PASSWORD
configMINIO_BUCKET_NAME
configMINIO_ENDPOINT
🔐 secretMINIO_ACCESS_KEYopenssl rand -hex 12
🔐 secretMINIO_SECRET_KEYopenssl rand -base64 32
🔐 secretWEBHOOK_SECRETopenssl rand -hex 32
configTL_API
configTL_WEB
configTL_SMOKE_TIMEOUT
configPOSTGRES_USER
🔐 secretPOSTGRES_PASSWORDopenssl rand -hex 24
configPOSTGRES_HOST
configPOSTGRES_PORT
configPOSTGRES_DB
configMFA_BREAKGLASS_OPERATOR
configTESTLOOKUP_PROFILE
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deploySERVICE_ROLE
deployDATABASE_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

81/81 tools missing one or more hints — trigger_ai_analysis (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_tests (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_flaky_tests (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +78 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

57/81 tools referenced in tests (70%)

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

Secrets stay with their owner

3 secret/sensitive values flow into network calls (WEBHOOK_SECRET → dynamic, WEBHOOK_SECRET → dynamic)

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

Secrets not logged

18 secret values sent to console.log

Redact or omit secret values from log output.

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/anandtopu-testlookup-1141zw?variant=verified)](https://m8ven.ai/mcp/anandtopu-testlookup-1141zw)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: e1bce50446f57e4c1620b359c1de686da414716e
code hash: a32b966c255e0d991d57bb12c5d8b9d3b66e7f2472391cc69070b432942c6c25
verified: 8/17/2026, 5:19:49 PM
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