MCP100 IndexFramework
WatchlistFirst-party MCP

AssetOpsBench

by IBM

Reviewed October 5, 2026

FrameworkManufacturing & Industrial

Watchlist tracking

Reviewed for relevance and future tracking value.

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Revisit the evolving industrial benchmark because domain-server tools and scenario coverage determine whether MCP workflows can be evaluated reproducibly.

Reviewed · Documentation review; complete setup workflow not independently tested

Best fit

Industrial maintenance and Industry 4.0 agent research and evaluation.

What we know

IBM's framework for developing and evaluating domain-specific agents over industrial asset operations with native MCP servers.

Maintenance / activity evidence

  • Observed (UTC)Merge pull request 601 from IBM/fix/missing-db-guard

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

  • Installation and comprehensive security have not been independently audited.
  • Depends on benchmark/backing-service configuration. Writes: Work-order create/update/approve/assign/close/cancel unless AOB_READONLY=1.
  • Authentication not yet verified.
  • Sensitive access: Industrial telemetry, Work orders
  • Industrial operations data and write-capable work-order tools require read-only configuration when mutation is not intended.
Security source · repository notice ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

2,330 repository stars

Stars observed Oct 6, 2026.

All limitations / Review context

Do scenario results remain reproducible when the sensor, failure-mode and time-series MCP tool contracts change?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

  • Industrial operations data and write-capable work-order tools require read-only configuration when mutation is not intended.
  • Depends on benchmark/backing-service configuration.
  • Industrial asset, sensor and work-order data may be processed.
  • Reviewed write actions: Work-order create/update/approve/assign/close/cancel unless AOB_READONLY=1
  • Sensitive access: Industrial telemetry, Work orders
  • Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
  • A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
  • No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
  • The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
  • Work-order writes exist unless read-only mode is enabled.
  • Research framework setup spans multiple backing services.

Original activity observations

  • 2026-10-02T15:38:16Z: Merge pull request 601 from IBM/fix/missing-db-guard
Technical identity
github.com/ibm/assetopsbench
Exact implementation source
https://github.com/ibm/assetopsbench ↗
Reviewed resource type
Framework
Repository identity
IBM/AssetOpsBench

Evidence & Sources

Evidence basis
Recorded source evidence
Setup runtime verification
Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed · Latest source observation

  • GitHub repository ↗

    ibm/assetopsbench

    Recorded repository material and project history.

    Includes references whose attribution is not established.