Glossary
Deploy spec / verified install
A machine-readable install manifest for a listing; the install is verified when Sato Hub re-ran it in an isolated container and it completed.
A deploy spec records how a listing is run: the install command or image, required environment variables, transport, and any variants (npx, Docker, hosted). Sato Hub writes one per listing from the project's own documentation and serves it over MCP so an agent can set a tool up without reading a README.
An install is marked verified only when Sato Hub executed the documented path inside an isolated container and it completed. That flips a listing's deploy status and shows as an earned mark on the listing, distinct from the score's independent-verification component.
A verified install proves installability on the day it ran. It does not prove the software is safe to run, that its tools behave as documented, or that it will still install next month; a re-run is the only refresh.
Where Sato Hub measures it
- Reliability index (verified installs) →
- MCP servers with a verified install, scored →
- onchain_agent_get_deploy_spec over MCP →
Numbers live on those pages and refresh on their own schedule; this definition does not restate them.
Related terms
Sources
Cite this page
Sato Hub. "Deploy spec / verified install (glossary)." Sato Hub, accessed 2026-09-09. https://satohub.ai/glossary/deploy-specThis page is refreshed daily. Citations include the date so a reader can tell which snapshot a claim came from.