Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/jonmikeli/ai-iot-tools-and-resourcesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/jonmikeli/ai-iot-tools-and-resources/iot-developer-plugin-iot-simulator-mcp)<a href="https://agentmods.dev/mcp/jonmikeli/ai-iot-tools-and-resources/iot-developer-plugin-iot-simulator-mcp"><img src="https://agentmods.dev/badge/mcp/jonmikeli/ai-iot-tools-and-resources/iot-developer-plugin-iot-simulator-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/jonmikeli/ai-iot-tools-and-resources/iot-developer-plugin-iot-simulator-mcp"><img src="https://agentmods.dev/badge/mcp/jonmikeli/ai-iot-tools-and-resources/iot-developer-plugin-iot-simulator-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
iot-simulator-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"iot-simulator-mcp": {
"type": "stdio",
"command": "C:\\Users\\<you>\\.mcp\\servers\\iot-simulator-mcp\\server\\JMI.AI.MCP.IoTSimulator.exe",
"args": [
"--McpSettings:Transport",
"Stdio"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 10 lines scan A 3205d1e488c9
iot-simulator-mcp is an MCP server published in the GitHub repository jonmikeli/ai-iot-tools-and-resources (1 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
azure
Azure MCP Server - Model Context Protocol implementation for Azure. Runs locally from the @azure/mcp npm package.
dbgprobe-mcp-server
Debug probe Model Context Protocol server for AI agents and developer tooling. Runs locally from the dbgprobe-mcp-server Python package. Needs 9 environment variables to run.
mcp-code-mode
MCP server "mcp-code-mode" as configured in Jame0077/mcp-code-mode. Runs locally from the mcp-code-mode Python package.
operandi
MCP server — let any LLM agent identify an appliance and pull its grounded, safety-checked, robot-executable operation package from OPERANDI. Runs locally from the operandi-mcp Python package. Needs 2 environment variables to run.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.