ToolTrust
A0/100
pnoker

iot-dc3

mcp2026.10.10

@pnoker

IoT DC3 — Connect the Physical World to AI. An open-source Industrial IoT Runtime for Physical AI: 36 protocol drivers, edge-to-cloud data delivery, and an MCP tool gateway so AI agents act on devices in a safe, controllable, traceable loop.

By pnoker | 11 findings | Scanned 10/26/2026 | tooltrust-scanner/v0.3.20 | 1.3k

Repository health

Popularity and maintenance signals alongside the security grade.

View repository
Stars

1.3k

current snapshot

Forks

Not collected

GitHub metadata pending

Contributors

Not collected

GitHub metadata pending

Last commit

Not collected

GitHub metadata pending

Last release

Not collected

GitHub metadata pending

Release version

Not collected

Latest GitHub release

Stars trend

Daily star additions · githubarchive_bq · observed through Oct 7, 2026 · export updated Oct 26, 2026

9d
2026-08-182026-09-24

Pull request activity

Weekly PR events · githubarchive_bq · observed through Oct 7, 2026 · export updated Oct 26, 2026

2026-10-052026-10-05

Data quality: observed_events. Charts show observed events, not a reconstructed historical total.

JavaNOASSERTIONOtherLast scan Oct 26, 2026
11 Info

Risk Summary

Safe With Normal Controls

Secret Handling is the main signal, but overall risk remains within an acceptable range.

Potential impact: Sensitive credentials may be read, logged, or leaked to external systems.

Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.

Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.

Security Findings (11)

  • InfoAS-002

    ⚠️Excessive Permissions

    autonomous_iot_architect:declared capabilities: filesystem access, environment variables

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

  • InfoAS-010

    🔑Insecure Secret Handling ×5

    input parameter "api_key" accepts a credential (informational; not evidence of insecure handling)

    autonomous_iot_architectgenerate_firmware_codedesign_device_cloud_syncoptimize_power_consumptionprepare_device_production

    Fix: Avoid accepting raw credentials as input parameters. Use secret managers (e.g. 1Password CLI, AWS Secrets Manager) and ensure credentials are never logged or stored in agent traces.

  • InfoAS-014

    ℹ️Dependency Inventory Unavailable ×5

    Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.

    autonomous_iot_architectgenerate_firmware_codedesign_device_cloud_syncoptimize_power_consumptionprepare_device_production

    Fix: Review and remediate the identified issue.

Scan this tool yourself

Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.

Install once, then scan any MCP server:

$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash
$ tooltrust-scanner scan --server "npx -y iot-dc3"

Adjust the package name if your npm registry name differs from the tool ID. View source

Add badge to your README

Copy this Markdown to show your ToolTrust grade on GitHub.

[![ToolTrust Grade A](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-a.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)