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/ucl-sbde/tacit-mcpWrote 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/ucl-sbde/tacit-mcp/mcp-server)<a href="https://agentmods.dev/mcp/ucl-sbde/tacit-mcp/mcp-server"><img src="https://agentmods.dev/badge/mcp/ucl-sbde/tacit-mcp/mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-server 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 6d 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
{ "mcp-server": { "command": "npx", "args": [ "-y", "@tacit/mcp-server" ] } }
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.
- 6d ago First seen · 9 lines scan A 3a6a412885db
mcp-server is an MCP server published in the GitHub repository ucl-sbde/tacit-mcp (0 stars, last pushed 1mo 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
zigbee2mqtt-mcp
Administer a Zigbee2MQTT estate: health, mesh diagnostics, OTA, pairing, device management. Runs locally from the zigbee2mqtt-mcp npm package. Needs 5 environment variables to run.
arduino-mcp-server
Arduino MCP server for CLI setup, board detection, compile/upload, serial monitoring, and pin refs. Runs locally from the arduino-mcp-server npm package. Needs 2 environment variables to run.
ccu-mcp
MCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API. Runs locally from the ccu-mcp npm package. Needs 20 environment variables to run.
larnitech-mcp
MCP server for Larnitech smart-home controllers over API2. Runs locally from the larnitech-mcp Python package.
nomos-mcp-bridge
MCP proxy bridge for managing multiple nomos system controllers. Runs locally from the nomos-mcp-bridge npm package.
mqtt-mcp-server
MQTT Model Context Protocol Server for AI-powered smart home control. Runs locally from the mqtt-mcp-server Python package.