Use TickClip from your AI client
Connect Codex, Claude Code, OpenCode, Hermes, or Pi to TickClip's public shopping verdicts. Your client can find recent decisions, open the evidence behind a verdict, and check public brand signals.
Access tokens
Create one token for each client. You can rotate or revoke one connection without interrupting the others.
- Copy each token when you create it. TickClip stores only a hash.
- Save the token in
TICKCLIP_MCP_TOKENand keep it out of repositories and shared configuration.
Checking your account
Sign in to generate and manage your TickClip tokens.What MCP does
Model Context Protocol lets an AI client discover and call tools from another service. After you connect TickClip, your client reads the tool definitions and chooses one when your request needs public verdict data. TickClip returns structured results instead of a scraped web page.
- 1Connect
- Your client opens TickClip's remote HTTPS endpoint.
- 2Authenticate
- It sends TICKCLIP_MCP_TOKEN as a bearer token.
- 3Discover
- The client loads the three available tools and their inputs.
- 4Call
- The model chooses a tool when your request needs TickClip data.
What TickClip returns
- Verdict decisions
- Tick, Clip, or Skip, plus the score, confidence, reason, and update time.
- Price evidence
- Current price, 30-day and 90-day averages, tracked-low status, and price change.
- Product evidence
- The bottom line, reasons to buy, reasons to pause, and the canonical verdict link.
- Brand signals
- Verdict mix, clean-signal rate, and a capped count of active deals.
Connect a client
codex mcp add tickclip \
--url "https://site.tickclip.ai/mcp" \
--bearer-token-env-var TICKCLIP_MCP_TOKENAfter you connect
Confirm the connection
Run
codex mcp list, or open/mcpin the Codex TUI.tickclipappears enabled in the server list.Confirm the tools
verdict_getverdicts_listbrand_summary_getRun a read-only check
List the 10 latest Tick verdicts.TickClip returns a bounded list of canonical public verdicts without changing data.
Available tools
TickClip exposes three query tools. None of them can publish, edit account data, or read private conversations.
| Tool | Access | Returns |
|---|---|---|
verdict_get | Read | Get one canonical public decision dossier by public ID, canonical verdict slug, or Amazon ASIN. |
verdicts_list | Read | List the newest canonical public verdicts, optionally filtered by Tick, Clip, or Skip. |
brand_summary_get | Read | Get a public brand summary with verdict mix, clean-signal rate, and a capped active-deal count. |
Keep context focused
- TickClip exposes three read-only tools on purpose.
- Some clients add enabled tool names and schemas to the model's context.
- Enable TickClip when a task needs public shopping verdicts or brand signals. Disable it for unrelated work if your client keeps MCP servers active across sessions.
How a request works
Find verdicts
Ask for recent verdicts, with an optional action filter.
Open the evidence
Use a returned ID or slug to retrieve the full dossier.
Keep the source
Use canonicalPath when you cite or share the result.
Prompts to try
Show the price evidence for verdict [slug].List the 10 latest Tick verdicts.Summarize the public verdict signals for [brand].
Security and limits
- Tokens only carry the mcp:verdicts:read scope.
- Only canonical public verdict data is available.
- Each account can keep five active tokens.
- Tokens expire after 90 days.
- A rotated token remains valid for five minutes.
- Revocation takes effect immediately.
Troubleshooting
Unauthorized
Confirm the token is active and carries
mcp:verdicts:read. UseAuthorization: Bearer <token>with one space between Bearer and the token.Tools are missing
Reconnect or restart the client, then confirm the new session loaded
verdict_get,verdicts_list, andbrand_summary_get.Endpoint not found
Use
https://site.tickclip.ai/mcpexactly. Check the path before changing transport or authentication settings.Connected, but no results
Remove filters or try a known public verdict. An empty
verdicts_list.itemsarray or anullverdict is a valid no-match result; authentication and server failures return errors.Too many requests
Wait for the
Retry-Afterdelay, then retry with fewer calls. TickClip currently returnsRetry-After: 60with HTTP 429.Token expired or revoked
Generate a replacement, update
TICKCLIP_MCP_TOKEN, and reconnect the client. A revoked token cannot be restored.Wrong client scope
Confirm the running session reads the scope where you saved TickClip. Use project scope for one workspace or user scope across workspaces, then reconnect.