AssetOpsBench (IBM/AssetOpsBench) is an MCP server listed on the M8ven Trust Index. It scores 98 out of 100, grade A. It declares 73 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
A
Trusted
98/100
7 days ago

AssetOpsBench

AssetOpsBench - Industry 4.0: A unified benchmark and framework for building, orchestrating, and evaluating domain-specific AI agents for Industry 4.0 asset operations and maintenance, with 460+ scenarios, 5 specialist agents (IoT, FMSR, TSFM, Work Order,...), and multi-agent orchestration blueprints (MetaAgent, AgentHive) over MCP.

→ IBM/AssetOpsBench· listed on github_topic

Trusted. Deep verification, no outstanding findings, and an established reputation. 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

IBM

Source: github_topic

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

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

// key findings
🚨
Secret credentials may flow to a network call
10 flows detected: COUCHDB_PASSWORD. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 3 credentials: COUCHDB_PASSWORD, WATSONX_APIKEY, LITELLM_API_KEY
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.
configLOG_LEVEL
configCOUCHDB_URL
configCOUCHDB_USERNAME
🔐 secretCOUCHDB_PASSWORD
configFAILURE_MODE_DBNAME
configFMSR_MODEL_ID
configIOT_DBNAME
configASSET_DBNAME
configCATALOG_DBNAME
configWO_DBNAME
configFAILURE_CODE_DBNAME
configAOB_READONLY
🔐 secretWATSONX_APIKEY
configWATSONX_PROJECT_ID
configWATSONX_URL
🔐 secretLITELLM_API_KEY
configLITELLM_BASE_URL
configOTEL_TRACES_FILE
configOTEL_EXPORTER_OTLP_ENDPOINT
configOTEL_EXPORTER_OTLP_TRACES_ENDPOINT
configOTEL_SDK_DISABLED
configSTIRRUP_CODE_IMAGE
configVIBRATION_DBNAME
configTSFM_STORE
configTSFM_WORKDIR
// 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

73/73 tools missing one or more hints — get_failure_modes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); generate_failure_modes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); add_failure_modes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +70 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.

Secrets stay with their owner

10 secrets sent to a request target we could not resolve (COUCHDB_PASSWORD → dynamic, COUCHDB_PASSWORD → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

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/ibm/assetopsbench)](https://m8ven.ai/mcp/ibm/assetopsbench)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: aac711fe8defdbd310ca8a6bc6a21547e69036ea
code hash: e6223884c0be42b92b86ff62f9743434da060e978a32d7414a994e3af479f31d
verified: 9/3/2026, 10:49:07 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