TappsMCP (wtthornton/TappsMCP) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 1 tool. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

TappsMCP

→ wtthornton/TappsMCP· 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

⚡ 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

wtthornton

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

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
✅
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 5 credentials: TAPPS_MCP_CONTEXT7_API_KEY, CONTEXT7_API_KEY, ANTHROPIC_AUTH_TOKEN, ANTHROPIC_API_KEY, TAPPS_MCP_MEMORY_BRAIN_AUTH_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.
🔐 secretTAPPS_MCP_CONTEXT7_API_KEYUp-to-date library docs via Context7 (when TAPPS_MCP_CONTEXT7_API_KEY is set) and LlmsTxt (always available as fallback). Fuzzy matching, local cache.
🔐 secretCONTEXT7_API_KEY
configTAPPS_OTEL_TRACE_ID
configTAPPS_OTEL_SPAN_ID
configCLAUDE_AGENT_NAME
configTAPPS_MCP_PROJECT_ROOTRestrict file operations to this directory (recommended for security). If unset, current working directory is used.
configTAPPS_MCP_MEMORY_BRAIN_HTTP_URL
configTOOL_BUDGET_BYPASS
configTAPPS_MCP_HEAVY_CPU_LIMIT
configTAPPS_FLEET_ROOTS
configTAPPS_MCP_DOCS_VIA_BRAIN
configTAPPS_LINEAR_SKIP_CACHE_GATE
configTAPPS_WRITE_MODE
configTAPPS_MCP_SESSION_STALE_S
configTAPPS_MCP_COMPACTION_REHYDRATE
configCLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS
🔐 secretANTHROPIC_AUTH_TOKENworkflow exposes it as , which the anthropic
🔐 secretANTHROPIC_API_KEYSDK (a dev dep). Needs . Rate-limit-immune.
configCLAUDE_AGENT_ID
configTAPPS_BRAIN_PROFILE
configTAPPS_BRAIN_DATABASE_URL
configTAPPS_BRAIN_PROJECT
configTAPPS_BRAIN_PG_POOL_MAX_WAITING
configTAPPS_BRAIN_PG_POOL_MAX_LIFETIME_SECONDS
🔐 secretTAPPS_MCP_MEMORY_BRAIN_AUTH_TOKEN
configTAPPS_MCP_MEMORY_BRAIN_PROJECT_ID
configTAPPS_PROJECT_ROOT
// 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

1/1 tools missing one or more hints — tapps_session_start (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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.

Shell command execution

12 calls in production code run through a shell (npm/bin/tapps-mcp.js:16, npm/bin/tapps-mcp.js:31, npm/bin/tapps-mcp.js:37)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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/wtthornton/tappsmcp)](https://m8ven.ai/mcp/wtthornton/tappsmcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 15367f1183eaad78b931bbe9a05b98639f2b24f8
code hash: b2496bcef62e393690b0217e7dbb116fd09b47e2144809ac654ca28e7ee25baa
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