ivedaai-mcp-server (WillORepO/ivedaAI-mcp-server) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

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

ivedaai-mcp-server

An MCP server for the IvedaAI video analytics API, enabling natural language control of footage search, camera and alert management, analysis jobs, and watchlists.

→ WillORepO/ivedaAI-mcp-server· listed on glama

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

WillORepO

Source: Glama

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

Glama

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

// key findings
✅
3 tools verified — handlers match their declared behaviour
1 read-only tool verified — handlers contain no write/delete/exec
✅
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 2 credentials: IVEDAAI_CLIENT_SECRET, IVEDAAI_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.
configIVEDAAI_ALLOW_INSECURE_TLS
configIVEDAAI_ALLOW_LOSSY_UPDATEfalse true disables the [lossy-update guard](docs/DESIGN.md#the-lossy-update-guard). Intended for the maintainers' CRUD probe; leave it unset.
configIVEDAAI_BASE_URL"": "https://ivedaai.example.com",
configIVEDAAI_CLIENT_ID/ IVEDAAI_CLIENT_SECRET — Sent as HTTP Basic auth on the token request, if your deployment requires client credentials.
🔐 secretIVEDAAI_CLIENT_SECRETIVEDAAI_CLIENT_ID / — Sent as HTTP Basic auth on the token request, if your deployment requires client credentials.
🔐 secretIVEDAAI_PASSWORD"": "your-password"
configIVEDAAI_REDACT_SECRETStrue Masks credential-shaped fields (keys, secrets, passphrases) in responses. false disables it.
configIVEDAAI_SWAGGER_PATHbundled Path to an alternate OpenAPI 3 document, if your deployment's API differs from the bundled one.
configIVEDAAI_USERNAME"": "your-username",
// quality suggestions

All four hints declared on every tool

3/3 tools missing one or more hints — ivedaai_get_schema (missing: idempotentHint); ivedaai_alert_integration (missing: idempotentHint); ivedaai_add_camera (missing: idempotentHint). 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.

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 1 concrete improvement 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/willorepo-ivedaai-mcp-server-nkosag)](https://m8ven.ai/mcp/willorepo-ivedaai-mcp-server-nkosag)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: bc9ad073b866c1bc697f2be6d806c49a85308149
code hash: e8e189f7e3b833efc9e5365c1d4fa29efba8805801f254f65acbd87da815430b
verified: 8/13/2026, 7:42:43 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