GateCheck by LarryBuildsAI
LarryLemonBotLABSCO SUMMARY
Read-only, so a validation run cannot change what it is validating.
That matters more here than in most places: a tool that inspects other servers' trust metadata should not also be able to act on them. The boundary is explicit — nothing that executes, deploys or deletes. Everything else about it comes down to whether you want card validation as a service rather than a script in your CI.
What it is
A paid remote MCP server that checks server cards: validation, auth checks, trust packets and readiness. It runs hosted, so there is no local process and no build.
What you get
- A fixed tool surface for MCP server-card validation, over Streamable HTTP
- Its own server card published at a
.well-knownURL, readable before you connect - A stated capability boundary: no arbitrary shell execution, no arbitrary SQL, no deployment controls, no deletion tools, no edits to payment configuration
Requirements
Version 0.1.0, hosted at https://servercardtrust.space/mcp. Any client that supports remote Streamable HTTP servers works; set the URL and pass Authorization: Bearer <token>. The token is claimed once after checkout — paste only the token value into your client's secret field, not the whole header.
Setup effort
Add the hosted endpoint plus a key — paste it into your client, then supply credentials
USE CASES
01
Checking a server card before trusting a listing
Validate the card and the auth setup behind it rather than reading the JSON by eye.
02
Confirming your own server is ready to publish
Run the readiness checks against your card before submitting it anywhere.
03
Inspecting the service before paying for it
Its own server card is public and needs no token.
BEFORE YOU INSTALL
What to know first
Requires
- A paid plan on servercardtrust.space — the bearer token is issued only after checkout and a one-time token claim
- An MCP client that supports remote Streamable HTTP servers and sends an Authorization header
INSTALLATION
Connect your client
Paste it into your client, then supply credentials.
Server setup
Setup
Open https://servercardtrust.space/pricing/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605.
Choose a plan and complete checkout.
Claim the one-time MCP bearer token from the hosted claim flow.
Paste only the token value into your MCP client secret field.
Configure the server URL as https://servercardtrust.space/mcp in any MCP client that supports remote Streamable HTTP MCP servers and pass the bearer token in the Authorization header.
Hosted endpoint
ENDPOINT URL
https://servercardtrust.space/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
