Back to MCP Trust Indexm8ven
C
Limited view
67/100
12 days ago

Agent_Track

A github to store my learning of Agent Workflows

→ TanSento/Agent_Track· listed on github_code

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Jupyter Notebook is partially covered.

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

TanSento

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 12 credentials: OPENAI_API_KEY, SERPER_API_KEY, PUSHOVER_TOKEN, OPENROUTER_API_KEY, GOOGLE_API_KEY, GROQ_API_KEY, ANTHROPIC_API_KEY, PUSHOVER_USER_KEY, GEMINI_API_KEY, DEEPSEEK_API_KEY, SENDGRID_API_KEY, RESEND_API_KEY
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.
configREPORT_STORAGE_DIR
🔐 secretOPENAI_API_KEY
🔐 secretSERPER_API_KEY
🔐 secretPUSHOVER_TOKEN
configPUSHOVER_USER
🔐 secretOPENROUTER_API_KEY
🔐 secretGOOGLE_API_KEY
configOPENAI_MODEL
configOPENROUTER_BASE_URL
configMODEL
configSECRET_PHARSE
🔐 secretGROQ_API_KEY
configPROFILE_DIR
configAGENT_NAME
configOPENROUTER_MODEL
configOPENROUTER_SITE_URL
configOPENROUTER_APP_NAME
🔐 secretANTHROPIC_API_KEY
configDISCORD_WEBHOOK_URL
🔐 secretPUSHOVER_USER_KEY
configOPENAI_BASE_URL
configANTHROPIC_BASE_URL
🔐 secretGEMINI_API_KEY
🔐 secretDEEPSEEK_API_KEY
configOPEN_ROUTER
configBOT_SELF_NAME
🔐 secretSENDGRID_API_KEY
configPROJECT_ENV_PATH
🔐 secretRESEND_API_KEY
configRESEND_TO_EMAIL
configDEEP_RESEARCH_QUERY
configSENDGRID_FROM_EMAIL
configSENDGRID_TO_EMAIL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

139/139 tools missing one or more hints — current_date (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); current_time (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); shift_date (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +136 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 inputs are validated

106/139 tool handlers declare input schemas (76%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 24/139 tool handlers wrap calls in try/catch (17%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 0/139 tools referenced in tests (0%)

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 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 Score](https://m8ven.ai/badge/mcp/tansento-agent-track-1whhup)](https://m8ven.ai/mcp/tansento-agent-track-1whhup)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: d3d652699e66222c384ba86318385f8d66a1e12d
code hash: 860ca5973702bb0bd3cae27c27fe32b2e228153a0ef857acb0e950726ab28f35
verified: 8/8/2026, 8:25:23 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