AItelier (linxuhao/AItelier) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 41 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

AItelier

AI-Atelier, the all in one personal "atelier" (means handcraft studio in french) that can adapt to your need.

→ linxuhao/AItelier· listed on github_repo_search

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

linxuhao

Source: github_repo_search

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 4 credentials: AITELIER_MCP_EXTERNAL_TOKEN, AITELIER_ADMIN_TOKEN, ZVEC_GREP_SERVER_TOKEN, AITELIER_STATE_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes41 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

get_available_models
list_providers
add_provider
update_provider
delete_provider
add_model
map_model
unmap_model
delete_model
list_pipelines
get_pipeline
list_roles
get_role
export_pipeline
import_pipeline
edit_pipeline
edit_role
list_templates
get_template
edit_template
get_tool
edit_tool
run_pipeline
answer_checkpoint
get_run_summary
get_run_status
wait_for_run
list_runs
trace_list
trace_search
trace_read
generate_pipeline
stop_pipeline
archive_pipeline
get_step_output
skillflow_docs_list
skillflow_docs_search
skillflow_docs_read
state_graph_help
state_graph_read
state_graph_write
// 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.
configAITELIER_PORT
configAITELIER_STATE_DIR
configAITELIER_SECRETS_DIR
configAITELIER_EDGE_NETWORK
configAITELIER_DEPLOY_OVERRIDE_FILE
configAITELIER_ALLOW_EXTERNAL
configAITELIER_SIGNIN_URL
configAITELIER_WEB_DIST
configAITELIER_MODE
configAITELIER_MEDIA_MCP_URL
configAITELIER_MEDIA_MCP_TIMEOUT
🔐 secretAITELIER_MCP_EXTERNAL_TOKEN
configAITELIER_MCP_ALLOWED_HOSTS
🔐 secretAITELIER_ADMIN_TOKEN
configSEARXNG_URL
configSEARXNG_TIMEOUT
configWEB_FETCH_TIMEOUT
configWEB_FETCH_MAX_CHARS
configHTTP_MAX_RETRIES
configHTTP_RETRY_BACKOFF
configGODOT_BUILDER_URL
configGODOT_VISION_ROUTE
configGODOT_VISION_CONTEXT_TOKENS
configGODOT_VISION_MAX_TOKENS
configGODOT_VISION_WIRE_COLORS
configZVEC_GREP_SERVER_URL
🔐 secretZVEC_GREP_SERVER_TOKEN
configAITELIER_STREAM_IDLE_TIMEOUT
configAITELIER_WRITERS
configAITELIER_STATE_ALLOWED_HOSTS
🔐 secretAITELIER_STATE_TOKEN; it does not import or start SkillFlow, a scheduler,
configAITELIER_HOST_AGENT_MODEL
configAITELIER_FORCE_ALL_AGENT_MODELS
configAITELIER_LLM_WALL_CAP_S
configAITELIER_LLM_STREAM
configAITELIER_CF_TEAM_DOMAIN
configAITELIER_CF_AUD
configAITELIER_HOME
configDPE_DB_PATH
configSKILLFLOW_DB_PATH
configDPE_WS_PATH
configDPE_PROJECTS_PATH
configAITELIER_GENERATED_CONFIGS_DIR
configAITELIER_ZVEC_LIFECYCLE
configAITELIER_ZVEC_PREPARE_WAIT_SECONDS
configAITELIER_MAX_STEPS_PER_RUN
configAITELIER_MAX_CLAIMS_PER_INSTANCE
configAITELIER_MAX_IDENTICAL_CLAIM_PRECONDITIONS
configAITELIER_CLAIM_CONTENTION_BACKOFF_SECONDS
configAITELIER_SCHEDULER_LOCK
configAITELIER_INSTANCE_LOCK
configAITELIER_MAX_CONCURRENT_PROJECTS
configAITELIER_LEASE_SWEEP_SECONDS
configAITELIER_ZVEC_COMMAND_TIMEOUT_SECONDS
// 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

41/41 tools missing one or more hints — get_available_models (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_providers (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); add_provider (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +38 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.

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 2 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/linxuhao/aitelier)](https://m8ven.ai/mcp/linxuhao/aitelier)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 279a7ddf5c3de60900fed8078b5b26520e6f04c7
code hash: f3944c9a2d6a9e5ae55ed05e6bf592bbc3ad15cc235f1241ae9eadfe2b5f1ba0
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