ustore-backoffice-mcp (tkuan/uStoreBackoffice-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

Emerging

74/100

8 days ago

ustore-backoffice-mcp

Item: ustore-backoffice-mcp
Rating: 74
Author: M8ven

Enables natural language interaction with the XMPie uStore BackOffice REST API, providing tools to list, search, describe, and execute API endpoints with server-side authentication, read-only by default.

→ tkuan/uStoreBackoffice-mcp · 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 push why connect →

Who stands behind it

tkuan

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

✅

No credential exfiltration, no sensitive file access, no obfuscation

Static analysis found nothing flowing your secrets to unexpected places.

🔐

You'll be asked for 4 credentials: MCP_BEARER_TOKEN, USTORE_API_KEY, USTORE_PASSWORD, USTORE_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.

🔐 secretMCP_BEARER_TOKENif you want the server itself to check a shared secret rather

configMCP_HOST

configMCP_PORT

configMCP_TRANSPORT"env": { "": "stdio" }

configUSTORE_ALLOW_PATHSis a regex allowlist. Setting it narrows the server to

configUSTORE_ALLOW_WRITEStrue is set on the server process.

🔐 secretUSTORE_API_KEY

configUSTORE_AUTH_HEADER

configUSTORE_AUTH_MODE

configUSTORE_AUTH_SCHEME

configUSTORE_BASE_URL

configUSTORE_CA_FILE

configUSTORE_DENY_PATHS

configUSTORE_LOGIN_BODY

configUSTORE_LOGIN_METHOD

configUSTORE_LOGIN_PATH

configUSTORE_MAX_RESPONSE_CHARS

🔐 secretUSTORE_PASSWORD

configUSTORE_SPEC_CANDIDATES

configUSTORE_SPEC_REFRESH_MS

configUSTORE_SPEC_URL

configUSTORE_TIMEOUT_MS

configUSTORE_TLS_INSECURE

🔐 secretUSTORE_TOKEN

configUSTORE_TOKEN_PATH

configUSTORE_TOKEN_TTL_SECONDS

configUSTORE_USERNAME

// 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

5/5 tools missing one or more hints — ustore_list_tags (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ustore_list_endpoints (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ustore_describe_endpoint (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +2 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

4/5 tool handlers declare input schemas (80%)

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

License file

No license file

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

Tests exist

No test files found

Add tests that exercise each declared tool.

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/tkuan-ustorebackoffice-mcp-zrdnb3)](https://m8ven.ai/mcp/tkuan-ustorebackoffice-mcp-zrdnb3)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: d29d44d796406b922c6a672462cc1a4b2ec8f7ed

code hash: 25b7a8128368fe19f5a1a41fab4ab06e355280202467fdc0bf9b092147339c17

verified: 8/19/2026, 9:18:24 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