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

Back to MCP Trust IndexM8ven
C
Emerging
74/100
9 days ago

ClaudeMCP

Webカメラを用いてClaudeCodeにアクセスするツールです。

→ yoshihito-tsuji/ClaudeMCP· 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

yoshihito-tsuji

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.
🔐
You'll be asked for 3 credentials: ELEVENLABS_API_KEY, TAPO_PASSWORD, TAPO_RIGHT_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.
configPULSE_SINK
configPULSE_SERVER
configOPENCV_LOG_LEVEL
configOPENCV_VIDEOIO_DEBUG
configELEVENLABS_PULSE_SERVER
🔐 secretELEVENLABS_API_KEY
configELEVENLABS_VOICE_ID
configELEVENLABS_MODEL_ID
configELEVENLABS_OUTPUT_FORMAT
configELEVENLABS_PLAY_AUDIO
configELEVENLABS_SAVE_DIR
configELEVENLABS_PLAYBACK
configELEVENLABS_PULSE_SINK
configMCP_SERVER_NAME
configMCP_SERVER_VERSION
configMEMORY_DB_PATH
configMEMORY_COLLECTION_NAME
configSENSORY_TTL_SEC
configSENSORY_MAX_ENTRIES
configMEMORY_MODEL_V2
configSHORTTERM_TTL_SEC
configSHORTTERM_MAX_ENTRIES
configAUTO_PROMOTE_THRESHOLD
configTAPO_CAMERA_HOST
configTAPO_USERNAME
🔐 secretTAPO_PASSWORD
configTAPO_ONVIF_PORT
configTAPO_STREAM_URL
configTAPO_MOUNT_MODE
configCAPTURE_MAX_WIDTH
configCAPTURE_MAX_HEIGHT
configTAPO_RIGHT_CAMERA_HOST
configTAPO_RIGHT_USERNAME
🔐 secretTAPO_RIGHT_PASSWORD
configTAPO_RIGHT_ONVIF_PORT
configTAPO_RIGHT_STREAM_URL
configTAPO_RIGHT_MOUNT_MODE
configCAPTURE_DIR
// 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

50/50 tools missing one or more hints — say (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); remember (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_memories (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +47 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 14/50 tools referenced in tests (28%)

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 4 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/yoshihito-tsuji/claudemcp)](https://m8ven.ai/mcp/yoshihito-tsuji/claudemcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 9032a60e1ef55612dbb9e45f3c4ea25bf3ec2bb6
code hash: 70a8322e36714190cbb7d5e455461b49fb52da1ece5aba5aa74acdc636a86d59
verified: 9/3/2026, 6:35:17 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