Add SealTrust to Claude or ChatGPT in 30 seconds
By the end of this page, you will know how to add SealTrust to Claude or ChatGPT with a single address, what the assistant can then do and what it will never do, and which limits apply.
On this page
A single address is enough for a conversational assistant to verify a SealTrust product and read its digital passport. There is nothing to install, no account to create and no key to copy. By the end of this page, you will know how to add it to Claude or ChatGPT, what the assistant can do next, what it will never do, and at what pace it can call SealTrust.
#The address to paste
https://mcp.sealtrust.io/mcpIt is an MCP server, for Model Context Protocol, the protocol through which an assistant calls external tools. It is hosted by SealTrust, read only, and reads only data that is already public.
#In Claude
- Open Settings, then Connectors.
- Choose Add custom connector.
- Name it
SealTrustand paste the address above. Leave the advanced authentication fields empty: the server asks for none. - Confirm. In a conversation, turn SealTrust on from the tools menu.
Custom connectors are offered on every Claude plan, the free plan included.
With Claude Code, on the command line, the same thing is written as follows.
claude mcp add --transport http sealtrust https://mcp.sealtrust.io/mcp#In ChatGPT
- Open Settings, then Apps & Connectors, then Advanced settings, and turn on Developer mode.
- Go back to Apps & Connectors and choose Create.
- Name it
SealTrust, paste the address above and choose No authentication. - Confirm. In a conversation, turn SealTrust on from the + menu.
Developer mode is not offered on every ChatGPT plan. If it does not appear in your settings, your plan does not include it.
#Try it right away
Ask the assistant: "Verify product H897RFWJ4972 on SealTrust and show me its
passport." This number is that of a demonstration product. The assistant calls
verify_product, then get_passport, and answers with what the brand
published.
#What the assistant can do
Seven tools, all read only. They are the same as those of the npm package, with the same descriptions, described in detail in Connect the MCP server.
| Tool | The question it answers |
|---|---|
verify_product | Is this number registered with SealTrust, and is its certificate in force? |
get_passport | What does the published digital passport say? |
get_passport_proof | Which proofs make it possible to verify this passport without trusting us? |
get_certificate | What does the certificate of authenticity carry? |
get_product_history | Which ownership movements and which scans has this product gone through? |
resolve_gs1 | Which passport does this GS1 Digital Link point to? |
verify_credential | Is the signature of the passport's verifiable credential valid? |
#What it will never do
- Change anything. No tool creates, transfers or deletes. The server only sends reads.
- Read what is not public. It sees what an anonymous visitor sees when opening a passport. Fields reserved for professionals or authorities cannot be reached through this path.
- Touch your account. It knows neither your console, nor your API key, nor your unpublished products.
- Say that an object is the original. A printed number or a QR code can be copied. The tool answers "registered number", never "authentic". Only reading the product's chip proves that the object in hand is the original.
#The limits
All of them are counted over a 60 second window.
| Limit | Value |
|---|---|
| Per IP address | 300 requests per minute |
| Per client | 120 tool calls per minute |
| For all users together | 480 reads per minute on each public read family, 48 on the GS1 resolution |
Claude and ChatGPT call from their vendor's servers. Many users therefore share a few addresses, and a refusal can come from a user other than you. The refusal comes as a 429 error that says in how many seconds to retry. If you meet it often, use the npm package described below: it calls SealTrust from your own address.
#What is kept
The server keeps neither your IP address nor the numbers the assistant passes it. It only notes which request arrived, which tool was called, the answer returned and how long it took. As for every SealTrust address, the access log of our front end keeps the caller's IP address for 30 days.
What you write to the assistant stays with its vendor. SealTrust only receives the tool calls, not the conversation.
#For developers: the same server on your machine
The @sealtrust-io/mcp-server package remains available on npm. It serves the
same tools over standard input and output, from your machine.
npx @sealtrust-io/mcp-serverInstallation in desktop clients and the settings are in Connect the MCP server.
Was this page helpful?
Your answer opens a pre-filled email in your mail app, addressed to contact@sealtrust.io. You read it over before sending it.