---
title: "Comment by X1Y1 on \"Five checks to run on your MCP server before someone else does\" | Hashnode"
description: "Check 5 is worth running from the client side too, since most people using a server don't own it. We read 10,659 public MCP config files on GitHub this month. 9"
url: "https://hashnode.com/posts/five-checks-to-run-on-your-mcp-server-before-someone-else-does/6af64a9953576550f3ef5a60/comment/6af69be23b0c53da1c332af1"
---

[Discussion](https://hashnode.com/posts/five-checks-to-run-on-your-mcp-server-before-someone-else-does/6af64a9953576550f3ef5a60)

Comment [Five checks to run on your MCP server before someone else does](https://hashnode.com/posts/five-checks-to-run-on-your-mcp-server-before-someone-else-does/6af64a9953576550f3ef5a60)

[X1Y1](https://hashnode.com/@x1y1)

[3d ago](https://hashnode.com/posts/five-checks-to-run-on-your-mcp-server-before-someone-else-does/6af64a9953576550f3ef5a60/comment/6af69be23b0c53da1c332af1)

Check 5 is worth running from the client side too, since most people using a server don't own it. We read 10,659 public MCP config files on GitHub this month. 9,465 of the 14,098 package-launched servers had no version pinned, and 323 files still used the legacy SSE transport. Pinning the package and hashing tools/list at that version gives a user the same alarm you describe for owners.
