Samprix

MCP Server Security Checker

Check a remote MCP server before you connect your AI agent to it: hidden instructions in its tools, tools that can do damage, and how it handles sign-in.

  • Public data only
  • Results in seconds
  • No sign-up
  • Free
Verdict Review first
Protocol Hidden
Sign-in Required
Tools Hidden

Results for https://api.githubcopilot.com/mcp/

  • OK:Sign-in required

    The server doesn’t list its tools to anonymous visitors, so its tools can’t be checked from outside. The sign-in setup is checked below.

Sign-in setup

Resource metadata
https://api.githubcopilot.com/.well-known/oauth-protected-resource/mcp/
Authorization server
https://github.com/login/oauth
Resource
https://api.githubcopilot.com/mcp/
Scopes
repo read:org read:user user:email read:packages write:packages read:project project gist notifications
  • Warning:No way for new clients to register

    Neither client ID metadata documents nor dynamic registration is offered, so only pre-registered clients can connect.

Advertisement

Securing a remote MCP server

  1. Keep descriptions plain. Describe what each tool does and nothing else. No instructions to the model about other tools, no “always call this first”, no HTML comments, and no invisible characters (paste descriptions through a plain-text editor).
  2. Annotate every tool. Set readOnlyHint, destructiveHint and openWorldHint honestly, so clients can ask the user before anything that changes data.
  3. Never ask the model for secrets. API keys and passwords belong in your server’s configuration or in OAuth, not in tool parameters the model fills in.
  4. Require sign-in for anything that acts. Answer anonymous requests with 401 and WWW-Authenticate: Bearer resource_metadata="…", publish /.well-known/oauth-protected-resource (RFC 9728), and use an authorization server that supports PKCE with S256 and client ID metadata documents.
  5. Upgrade to the current protocol. MCP 2026-07-28 is stateless, so there are no session IDs to steal. If you’re still on an older version, make sure session IDs are long and random.

If you’re connecting to someone else’s server

  • Only add servers from publishers you trust, and check them again after updates.
  • Keep your client’s approval prompt on for tools that write, send, delete or run code.
  • Don’t connect a server with tools you can’t read in full, or that the checker marks high risk.

Did this tool do what you needed?

All tools