One central harness, six LLM providers, thirty-six MCP servers and six machines in a single headscale mesh, two of them switched off at survey time. Every service carries the machine that runs it and the one it drives, including when that machine is not mine. Internal addresses and ports are deliberately omitted: this page is public.
surveyed 18 November 2026 on tower · NixOS 26.05
6machines
36MCP servers
34MCP processes on tower
4providers as third-party APIs
62 GBtower RAM
1single GPU (laptop)
Harness
Hermes Agent 2026.9.24, default profile on tower
3 profiles: default, discord-bridge, pocket
Skills, memory, cron, delegate, webhooks
Claude Code CLI for code delegation
LLM providers
deepseek by default, 1M context, vision
2 providers executed on the laptop
4 providers as third-party APIs (deepseek, openrouter, moonshot, anthropic)
the client is always the harness, on tower
MCP
36 servers configured, 6 families
34 processes on tower, 1 on the laptop, 1 on the Mac
8 infra, 6 money, 7 self-hosted
2 media, 8 personal / OSINT, 5 third-party APIs
Cluster
5 mesh hosts + 1 Mac off the mesh
tower runs the services, no GPU
laptop is the only CUDA node
anywhere carries public entry, auth and mail
1LLM providers: who actually runs the model
The harness runs on tower in all six cases. What changes is the machine executing the model: four providers are third-party APIs, two run on the laptop.
provider
what it serves
client
model executed on
owner
deepseek
default · deepseek-flash · ctx 1M · vision
tower
API DeepSeek
third party
openrouter
fallback · deepseek-v4.1-flash · nemotron-3-ultra
tower
OpenRouter
third party
kimi-k3-global
auxiliary vision · kimi-k3
tower
API Moonshot
third party
laptop-llama
llama-swap · qwen3.5-4b / 2b · ornith-9b
tower
laptop
mine
laptop-abl
qwen3.5-4b-abl · ctx 131k
tower
laptop
mine
claude
direct subscription · opus
tower
API Anthropic
third party
2MCP servers: the process and its target
An MCP server is a local process that drives something. The "runs on" column says where the process lives, the "target" column says which service it talks to: mine, a device, or an API that is not mine.
mcp server
runs on
target
target owner
nixos
tower
local nix + search.nixos.org
mine + third party
hermes-tools
tower
mcp-host on tower
tower
app-publish
tower
App Store Connect · Google Play
third party
github
tower
github.com
third party
codeberg
tower
codeberg.org
third party
gitea
tower
Gitea on tower
tower
share
tower
droplify on anywhere + Nextcloud on tower
anywhere
taskq
tower
taskq queue (retired)
tower
bank
tower
local banking API on tower
tower
wise
tower
API Wise
third party
simplefin
tower
SimpleFIN Bridge
third party
gocardless
tower
GoCardless Bank Account Data
third party
enable-banking
tower
Enable Banking
third party
stripe
tower
mcp.stripe.com
third party
nextcloud
tower
Nextcloud on tower
tower
arrmcp
tower
*arr on tower
tower
qbittorrent
tower
qBittorrent on tower
tower
garage
tower
Garage (S3) on tower
tower
anki
tower
Anki + sync on tower
tower
vaultwarden
tower
Vaultwarden on anywhere
anywhere
zitadel
tower
production ZITADEL (anywhere)
anywhere
roku
tower
3 TCL TVs on the LAN
my devices
firefox
tower
local Firefox on tower
tower
firefox-mac
tower
Firefox on the Mac
mac
username-recon
tower
sherlock / maigret across third-party sites
third party
phonerep
tower
SpamCalls · Robokiller · WhoCallsMe
third party
iprep
tower
AbuseIPDB · GreyNoise · Spamhaus
third party
hinge
tower
Hinge app on the phone
phone
stalwart
tower
Stalwart on anywhere
anywhere
beeper
tower
Beeper (service stopped)
third party
amazon
tower
amazon.com
third party
arena-elo
tower
arena datasets on Hugging Face
third party
openrouter
tower
openrouter.ai
third party
shlink
tower
Shlink on tower
tower
tts
laptop
TTS engine on laptop
laptop
chrome-mac
mac
Chrome on the Mac
mac
3Self-hosted services, machine by machine
What I actually operate, grouped by machine. Mesh hosts carry the infrastructure; devices only carry their own client.
tower
main host
Hermes harness · gateway · backend · mobile · webui
off at survey time: Chrome and Firefox driven remotely
deck
mesh node
offloaded rebuilds
Steam client
phone
nix-on-droid
ssh client (jumps through anywhere)
Hinge app driven by the hinge MCP
4What is not mine
None of these lines runs on my machines. They are listed because the harness depends on them, and because an honest infra page separates what you host from what you rent.