3tears (pacepace/3tears) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 73 tools. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
12 days ago

3tears

3tears for all the things that prevent your python app from scaling horizontally, being easy to use with ai, and being fully observable.

→ pacepace/3tears· listed on github_code

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

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

pacepace

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
✅
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 1 credential: THREETEARS_NATS_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.
configTHREETEARS_NATS_USER
🔐 secretTHREETEARS_NATS_PASSWORD
configTHREETEARS_REGISTRY_HEALTH_PORT
configTHREETEARS_REGISTRY_POD_AUTHENTICATOR_FACTORY
configTHREETEARS_REGISTRY_LIMIT_GUARD_FACTORY
configTHREETEARS_REGISTRY_USAGE_EMITTER_FACTORY
configTHREETEARS_MCP_TIMEOUT
configCHROMIUM_PATH
configEGRESS_PROXY
configEGRESS_NAME
configDISPLAY_NUM
configUI_SCALE
configTHREETEARS_TOOL_SERVER_HEALTH_PORT
configFOURTEENAIBOTS_NATS_USER_JWT_TTL_SECONDS
configTHREETEARS_SEARXNG_URL
configTHREETEARS_TOOL_POD_IDENTITY_SIGNING_KEY_REF
configTHREETEARS_NATS_URL
configTHREETEARS_NATS_SUBJECT_NAMESPACE
configTHREETEARS_TOOL_POD_ID
configTHREETEARS_TOOL_POD_CONNECT_ISSUER
configTHREETEARS_TOOL_POD_CUSTOMER_ID
configHITL_MAX_SLOTS
configHITL_SESSION_TTL_SECONDS
configHITL_REAPER_INTERVAL_SECONDS
// 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

73/73 tools missing one or more hints — _call_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dynamic_tool_145 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_conversations (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +70 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

45/73 tools referenced in tests (62%)

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

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 3 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/pacepace-3tears-f8uv2l)](https://m8ven.ai/mcp/pacepace-3tears-f8uv2l)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 02a53628bb7c1cb889285e18093b430655375acb
code hash: 12718c5d59bc420bbf6b73d1f1aa7e09623999e41a5967b6662616d8d5f8314c
verified: 8/13/2026, 7:52:31 AM
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