URL risk evidence with scoped OAuth/API keys, capped prepaid costs and up to ten URLs per batch.
Connect Remote server
claude mcp add --transport http verify https://shopsafe.com.au/mcp --header "Authorization: Bearer <YOUR_API_KEY>"{
"mcpServers": {
"verify": {
"url": "https://shopsafe.com.au/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}{
"servers": {
"verify": {
"type": "http",
"url": "https://shopsafe.com.au/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}Settings > Connectors > Add custom connector
URL: https://shopsafe.com.au/mcpReplace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Bearer API key from the ShopSafe portal; OAuth clients may instead use the advertised MCP authorization flow. |
Details
| Endpoint | https://shopsafe.com.au/mcp (Streamable HTTP) |
| First published | 19 Oct 2026 |
| Last updated | 19 Oct 2026 |
| Registry name | au.com.shopsafe/verify |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.