# Trickl (remote · api.trickl.app)

Trickl for AI assistants: full docs, setup plans, and sandbox tools to test purchases end to end.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.trickl.app`: 71/100 (this document), [markdown](https://verifymcp.io/servers/app-trickl-trickl/mcp-dev.md), [page](https://verifymcp.io/servers/app-trickl-trickl/mcp-dev)

## Channel facts

- Endpoint: `https://api.trickl.app/mcp/dev`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http app-trickl-trickl 'https://api.trickl.app/mcp/dev'
```

### Cursor

```json
{
  "mcpServers": {
    "app-trickl-trickl": {
      "url": "https://api.trickl.app/mcp/dev"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-trickl-trickl": {
      "type": "http",
      "url": "https://api.trickl.app/mcp/dev"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-trickl-trickl]
url = "https://api.trickl.app/mcp/dev"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-trickl-trickl": {
      "type": "remote",
      "url": "https://api.trickl.app/mcp/dev",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-trickl-trickl --url 'https://api.trickl.app/mcp/dev' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-trickl-trickl:
    url: "https://api.trickl.app/mcp/dev"
```

### Netclaw

```json
{
  "McpServers": {
    "app-trickl-trickl": {
      "Transport": "http",
      "Url": "https://api.trickl.app/mcp/dev"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-trickl-trickl -t streamable-http -u 'https://api.trickl.app/mcp/dev'
```

### Other

```json
{
  "mcpServers": {
    "app-trickl-trickl": {
      "type": "http",
      "url": "https://api.trickl.app/mcp/dev"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 71, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.37 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-03 (score 71, +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.

### 2026-11-01 (score 70, +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.

### 2026-10-30 (score 69, +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.

### 2026-10-28 (score 68, +1)

- [security] Tool “cancel_test_goal” rewrote its description, which is the text the model reads

### 2026-10-26 (score 67, +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.

### 2026-10-24 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 65)

First indexed and scored.

## MCP tools (10)

### `get_started` (~162 tokens)

Get a Trickl setup plan

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.

Input parameters:

- `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…

### `search_docs` (~72 tokens)

Search the Trickl docs

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.

Input parameters:

- `query` (string): e.g. "deadline goal", "verify signature", "REDIRECT_URL_NOT_ALLOWED"

### `read_doc` (~47 tokens)

Read a docs section

Returns one section of the Trickl docs in full (Markdown), by id from search_docs.

Input parameters:

- `id` (string, required): Section id, e.g. "platform-api/sandbox-test-mode"

### `check_api_key` (~48 tokens)

Check the API key

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.

### `register_test_provider` (~214 tokens)

Register a sandbox seller

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.

Input parameters:

- `businessName` (string): Default: Sandbox Seller
- `email` (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, required): https URL of the user's webhook receiver
- `websiteUrl` (string): Seller site; its host is allowed for redirects and embedded checkout

### `create_test_goal` (~253 tokens)

Create a sandbox goal

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.

Input parameters:

- `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, required): 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, required): From register_test_provider
- `targetAmount` (integer, required): Price in cents, e.g. 2999 = $29.99

### `get_goal` (~47 tokens)

Get a sandbox goal

Returns a sandbox goal's current state via GET /goals/:goalId: status, amounts saved, buyer, deadline.

Input parameters:

- `goalId` (string, required): goalId from create_test_goal

### `simulate_goal_event` (~261 tokens)

Simulate a goal event

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.

Input parameters:

- `amount` (integer): collect / payment_failed only: cents, default 300
- `event` (string, required)
- `goalId` (string, required): 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

### `cancel_test_goal` (~78 tokens)

Cancel a sandbox goal

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.

Input parameters:

- `goalId` (string, required): goalId from create_test_goal

### `list_webhook_deliveries` (~107 tokens)

List webhook deliveries

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.

Input parameters:

- `goalId` (string, required): goalId from create_test_goal

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-trickl-trickl/mcp-dev#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 69
- 2026-10-30: 69
- 2026-10-29: 68
- 2026-10-28: 68
- 2026-10-27: 67
- 2026-10-26: 67
- 2026-10-25: 66
- 2026-10-24: 66
- 2026-10-23: 65

## Common questions

### 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.

## Links

- Remote endpoint: https://api.trickl.app/mcp/dev
- Website: https://trickl.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-trickl-trickl/mcp-dev.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-trickl-trickl/mcp-dev.json
- HTML version of this page: https://verifymcp.io/servers/app-trickl-trickl/mcp-dev
