Skip to content

Trickl MCP server

app.trickl/trickltrickl.appstreamable-httpv1.0.2Scanned

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

10 tools: 1 can delete or cancel things, 5 change things and 4 only read.

Tools: 1 delete, 0 irreversible, 5 write, 4 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 2
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Trickl MCP server can do

The Trickl MCP server is published by trickl.app, a domain the MCP Registry verified. It has 10 tools. It can delete or cancel things (1 tool: cancel_test_goal) and create or change data (5 tools: get_started, check_api_key, register_test_provider, create_test_goal and 1 more). 4 tools only read.

2 tools read private data (search_docs and read_doc); 2 tools can send data out of your system (register_test_provider and create_test_goal).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 1.0.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Deletes or cancels 1Claude Code: deny
  • cancel_test_goalCancels 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 fe…No findings

    Why it is in this group

    • The name "cancel_test_goal" says "cancel": a word for removing or ending something.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
Changes things 5Claude Code: ask
  • check_api_keyConfirms this connector's test key works and shows its platform, scopes and mode.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • create_test_goalCreates a goal with POST /goals/create using the test key.Can send data outNo findings

    Why it is in this group

    • The name "create_test_goal" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.callbackUrl): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
  • get_startedStart here.1 finding

    Why it is in this group

    • The name "get_started" says "get": a word for reading.
    • The description's first verb is "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "get_started" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "get_started" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • register_test_providerRegisters a seller (provider) under the test key via POST /providers/register and returns providerLinkCode (needed to create goals) and webhookSecret (to verify webhooks).Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.webhookUrl): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
  • simulate_goal_eventMoves a sandbox goal through its lifecycle instantly; each event sends the real signed webhook to the seller's webhookUrl, exactly as live would.No findings

    Why it is in this group

    • The description's first verb is "move": a word for a change.
    Description, as the server wrote it
    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 collected chunk (round-ups and/or Trickl Down, which arrive the same way), $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.

    Annotations the server declares

    • readOnlyHint: false
Only reads 4Show 4 read-only tools
  • get_goalReturns a sandbox goal's current state via GET /goals/:goalId: status, amounts saved, buyer, deadline.No findings

    Why it is in this group

    • The name "get_goal" says "get": a word for reading.
    Description, as the server wrote it
    Returns a sandbox goal's current state via GET /goals/:goalId: status, amounts saved, buyer, deadline.

    Annotations the server declares

    • readOnlyHint: true
  • list_webhook_deliveriesShows every webhook Trickl sent for a sandbox goal, newest first, with its payload and the receiver's result.No findings

    Why it is in this group

    • The name "list_webhook_deliveries" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • read_docReturns one section of the Trickl docs in full (Markdown), by id from search_docs.Reads private dataNo findings

    Why it is in this group

    • The name "read_doc" says "read": a word for reading.

    What it can reach

    • private-dataThe name "read_doc" says "read" and "doc": it reads documents.
    • private-dataThe description's first sentence says "return" and "doc": it reads documents.
    Description, as the server wrote it
    Returns one section of the Trickl docs in full (Markdown), by id from search_docs.

    Annotations the server declares

    • readOnlyHint: true
  • search_docsKeyword search over the Trickl partner docs (platform API, webhooks, embed widget).Reads private dataNo findings

    Why it is in this group

    • The name "search_docs" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_docs" says "search" and "doc": it reads documents.
    • private-dataThe description's first sentence says "doc": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:23 UTC, unchanged since Oct 23, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 destructive, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.trickl.app/mcp/dev: tools/list returned 10 tools to an anonymous client, including cancel_test_goal (destructive), get_started (write), check_api_key (write), register_test_provider (write), create_test_goal (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "get_started" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "get_started" says "get": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__trickl__search_docs",
      "mcp__trickl__read_doc",
      "mcp__trickl__get_goal",
      "mcp__trickl__list_webhook_deliveries"
    ],
    "ask": [
      "mcp__trickl__get_started",
      "mcp__trickl__check_api_key",
      "mcp__trickl__register_test_provider",
      "mcp__trickl__create_test_goal",
      "mcp__trickl__simulate_goal_event"
    ],
    "deny": [
      "mcp__trickl__cancel_test_goal"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as trickl. Review it before you use it.

Capability tags behind 4 rules
  • mcp__trickl__search_docs private-data
  • mcp__trickl__read_doc private-data
  • mcp__trickl__register_test_provider outbound
  • mcp__trickl__create_test_goal outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.trickl/trickl/verify?hash=8b6f50739c6f67713cf2a3b0131c717e9c3ed0ffed08eb72f9d008b44a07ed83" | jq -e '.changed == false'

Pinned hash 8b6f50739c6f, from Nov 17, 2026, 18:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.trickl/trickl/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.trickl/trickl
[![Anlyon Radar](https://radar.anlyon.com/badge/app.trickl/trickl.svg)](https://radar.anlyon.com/servers/app.trickl/trickl)

Source: MCP Registry · repository. Synced Nov 17, 2026, 18:17 UTC.

Trickl MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Trickl MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Trickl MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel_test_goal.

Can the Trickl MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Trickl MCP server have?

10 tools: 1 destructive, 5 write, 4 read. cancel_test_goal, get_started, check_api_key, register_test_provider, create_test_goal, simulate_goal_event, search_docs, read_doc and 2 more.

Does the Trickl MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Trickl MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): register_test_provider and create_test_goal.

Has the Trickl MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.