io.github.nagarjunr/aws-iot-core

AWS IoT Core

Is the AWS IoT Core MCP server down? No. It is up and needs network, probed 2026-11-01.

MCP server for AWS IoT Core: device registry, shadows, jobs, rules, messaging.

needs network probed 2026-11-14 · unchanged since 2026-11-01

MCP error -32000: Connection closed
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/work/uv/aws-iot-core-mcp-server/lib/python3.12/site-packages/

Run it: uvx aws-iot-core-mcp-server@0.1.0 (stdio, probed in a container with the network off)
Host: pypi.org
Repository: https://github.com/nagarjunr/iot-mcp-servers
Registry: active, updated 2026-07-24 · registry entry
Changes: 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.

Compare this server with others.

More servers

Other registry entries on pypi.org, the ones next to this name; all of them.

Telegram MCP io.github.n24q02m/telegram · needs env
io.github.n24q02m/wet · crashed on start
MCP Zero-Trust Gateway io.github.nabrahma/mcp-ztgateway · needs network
io.github.nagameTW/mcp-server-malcolm · alive
Azure IoT Hub io.github.nagarjunr/azure-iot-hub · install failed
Eclipse Ditto io.github.nagarjunr/eclipse-ditto · alive
MQTT io.github.nagarjunr/mqtt · needs env
Sparkplug B io.github.nagarjunr/sparkplug-b · needs env

Servers that mention core.

GroundTruth - Environmental Records ai.agentlookups/groundtruth · alive
Arclan MCP Registry ai.arclan/registry · alive
BittleBits GEO Assistant ai.bittlebits/bittlebits · no DNS
B4 Index ai.benroberts/b4-index · alive
CertScore.ai MCP Light ai.certscore/mcp-light · alive
Builders in Fintech ai.buildersinfintech/fintech-data · alive
ai.colaunched/colaunched · needs auth
ai.colaunched/public · alive

History

We add a row when the result changes. A server with no change keeps its last row.

Probed	Result	Init	Tools	Claude	o200k
2026-11-01 08:16	needs network
2026-10-18 06:42	needs env

Badge for the README

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher

The server tries to reach the network on start. The probe runs in a container with the network off, so a server that connects lazily, on the first tool call, is measured.