Trickl
REMOTE · API.TRICKL.APP
Trickl for AI assistants: full docs, setup plans, and sandbox tools to test purchases end to end.
Available components
Last scanned (18 hours ago)
Scores higher than 57% of remote servers
Unreachable for 1 day in a row. Last reached 3 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.37 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
- Tool “cancel_test_goal” rewrote its description, which is the text the model reads security
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://api.trickl.app/mcp/dev
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.trickl.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| trickl.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.trickl.app/mcp/dev | Unreachable | ||
| http (plaintext) | http://api.trickl.app/mcp/dev | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_test_goal Cancel a sandbox goal ~78
Cancels a sandbox goal via POST /goals/:goalId/cancel, as the user's server would when a customer cancels: collected chunks (and a refundable deposit) are refunded less Trickl's fee, in the ledger only, and goal.cancelled is sent.
| Name | Type | Req | Description |
|---|---|---|---|
| goalId | string | yes | goalId from create_test_goal |
No output schema declared.
No examples provided.
check_api_key Check the API key ~48
Confirms this connector's test key works and shows its platform, scopes and mode. Run it before the other sandbox tools; if it fails, the message says what the user needs to fix.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_test_goal Create a sandbox goal ~253
Creates a goal with POST /goals/create using the test key. No money moves. Returns goalId, paymentUrl (hosted checkout) and clientSecret (embedded checkout). Amounts are integer cents, USD.
| Name | Type | Req | Description |
|---|---|---|---|
| callbackUrl | string | – | Where the buyer returns after confirming; localhost is allowed in test mode |
| cancelUrl | string | – | – |
| deadline | string | – | ISO 8601 due date, 24h to 2 years out (one-time goals only) |
| depositAmount | integer | – | Upfront card charge in cents. One-time: ≥ 50 and < targetAmount. Subscription: = targetAmount or omit |
| depositRefundable | boolean | – | – |
| description | string | yes | What the buyer is saving for, max 500 characters |
| frequency | string | – | Makes it a recurring subscription; omit for a one-time purchase |
| imageUrl | string | – | – |
| metadata | object | – | Echoed verbatim in every webhook, e.g. { orderId } |
| providerLinkCode | string | yes | From register_test_provider |
| targetAmount | integer | yes | Price in cents, e.g. 2999 = $29.99 |
No output schema declared.
No examples provided.
get_goal Get a sandbox goal ~47
Returns a sandbox goal's current state via GET /goals/:goalId: status, amounts saved, buyer, deadline.
| Name | Type | Req | Description |
|---|---|---|---|
| goalId | string | yes | goalId from create_test_goal |
No output schema declared.
No examples provided.
get_started Get a Trickl setup plan ~162
Start here. Without an integration, explains the ways to add Trickl (own business such as a SaaS, or a multi-seller platform) and how to choose. With one, returns a step-by-step plan for the coding agent: keys, exact API calls, webhook handling, what to store, and how to prove it works with this server's sandbox tools.
| Name | Type | Req | Description |
|---|---|---|---|
| integration | string | – | own_*: the user's own business gets paid (SaaS, app, course, membership); own_embedded_checkout puts checkout inside their app. platform_*: many sellers on the user's platform get paid. embedded = in… |
No output schema declared.
No examples provided.
list_webhook_deliveries List webhook deliveries ~107
Shows every webhook Trickl sent for a sandbox goal, newest first, with its payload and the receiver's result. DELIVERED = got a 2xx. FAILED = rejected, retry scheduled at nextRetryAt. EXHAUSTED = gave up. PENDING / DELIVERING = in flight; check again in a few seconds. Use lastStatusCode and lastError to debug the receiver.
| Name | Type | Req | Description |
|---|---|---|---|
| goalId | string | yes | goalId from create_test_goal |
No output schema declared.
No examples provided.
read_doc Read a docs section ~47
Returns one section of the Trickl docs in full (Markdown), by id from search_docs.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Section id, e.g. "platform-api/sandbox-test-mode" |
No output schema declared.
No examples provided.
register_test_provider Register a sandbox seller ~214
Registers a seller (provider) under the test key via POST /providers/register and returns providerLinkCode (needed to create goals) and webhookSecret (to verify webhooks). Idempotent on externalCreatorId. webhookUrl must be a public https URL that reaches the user's receiver, e.g. an ngrok or cloudflared tunnel to localhost. Sandbox webhooks are real signed HTTP requests.
| Name | Type | Req | Description |
|---|---|---|---|
| businessName | string | – | Default: Sandbox Seller |
| string | – | Must not belong to an existing Trickl provider. Default: a per-seller @example.com address | |
| externalCreatorId | string | – | The seller's id in the user's app. Default: sandbox-seller-1 |
| stripeConnectAccountId | string | – | Leave empty in sandbox: a placeholder is used, since sandbox goals never reach Stripe |
| webhookUrl | string | yes | https URL of the user's webhook receiver |
| websiteUrl | string | – | Seller site; its host is allowed for redirects and embedded checkout |
No output schema declared.
No examples provided.
search_docs Search the Trickl docs ~72
Keyword search over the Trickl partner docs (platform API, webhooks, embed widget). Returns section ids with snippets; read one with read_doc. Leave query empty for the full table of contents.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | e.g. "deadline goal", "verify signature", "REDIRECT_URL_NOT_ALLOWED" |
No output schema declared.
No examples provided.
simulate_goal_event Simulate a goal event ~261
Moves a sandbox goal through its lifecycle instantly; each event sends the real signed webhook to the seller's webhookUrl, exactly as live would. confirm: the buyer signs up and links a bank (goal.deposit_paid if there is a deposit; for subscriptions also goal.subscription_created, plus goal.cycle_paid at once if the deposit paid the first period in full). collect: one round-up chunk, $3 by default (goal.round_up_collected); fails with ALREADY_FUNDED when the current period is already paid. complete: one-time goals finish (goal.completed); subscriptions pay the current period and start the next (goal.cycle_paid; the goal stays SAVING). payment_failed: a failed chunk (goal.payment_failed), with reversal=true for the clawback path. expire: a deadline goal fell short (goal.deadline_charge_failed). Confirm first.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | – | collect / payment_failed only: cents, default 300 |
| event | string | yes | – |
| goalId | string | yes | goalId from create_test_goal |
| reason | string | – | payment_failed with reversal only |
| reversal | boolean | – | payment_failed only: true = a chunk already counted is reversed (clawback); false = a collection failed |
No output schema declared.
No examples provided.
How do I install the Trickl MCP server?
Trickl is a hosted endpoint at https://api.trickl.app/mcp/dev, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.trickl.app
claude mcp add --transport http app-trickl-trickl 'https://api.trickl.app/mcp/dev'
What is the Trickl MCP server?
Trickl is an MCP server listed in the public MCP registry as app.trickl/trickl. Trickl for AI assistants: full docs, setup plans, and sandbox tools to test purchases end to end. This page covers its hosted endpoint (https://api.trickl.app/mcp/dev).
Is the Trickl MCP server safe to use?
Trickl scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Trickl MCP server expose?
Trickl exposes 10 tools: get_started, search_docs, read_doc, check_api_key, register_test_provider, and 5 more. Their descriptions and schemas cost roughly 1,289 tokens of context every time the server is loaded.
Does the Trickl MCP server require authentication?
Its publisher declares no required credentials for Trickl. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Trickl MCP server still maintained?
Trickl is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.