Skip to content
ProtocolProbe
Explore

MCP servers › io.linkjolt › linkjolt

MCP server · registry snapshot 2026-11-03 · last tested 2026-11-03

io.linkjolt/linkjolt

by linkjolt.io · domain (the registry's namespace rule)Website ↗

For businesses that pay affiliates: set up and run your affiliate program from your AI assistant. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-03version 1.0.0streamable HTTP28 tools

Summary

io.linkjolt/linkjolt is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain linkjolt.io. On 2026-11-03 ProtocolProbe connected to it in read-only mode and read its inventory: 28 tools, 1 resource and 3 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
28
Last tested
2026-11-03

Tool list size

9,163 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (28 tools). Counted with Anthropic's token counter on 2026-11-03, from the tool list we read on 2026-11-03. Median across 25,738 counted servers: 2,858 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-03 (www.linkjolt.io), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 7 tools whose name or declaration suggests they change data (update_business, create_campaign, update_campaign, update_affiliate_status, create_conversion and 2 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-03.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-03
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-11-02 (registry, as of the 2026-11-03 snapshot)
First listed version
2026-11-02 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-03
Package and repository
checked 2026-11-03
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-02, listed on 2026-11-03 with version 1.0.0 (published 2026-11-02).

Source: the official MCP Registry list on 2026-11-02 and on 2026-11-03.

What it is

What does this server offer?

Observed inventory
28tools
1resources
3prompts

None of its 28 tools are described as changing anything. For 28 the reading was uncertain, so no mark is shown.

  • plan_affiliate_program

    “Plan an affiliate program for a product before launching it: a commission rate, whether to pay on renewals, and how to approve affiliates, from LinkJolt's published benchmarks of real SaaS programs, …”

    Publisher declares: read-only yes · destructive no · open-world no

    4 inputs, 1 required
    • pricenumberrequired“What a customer pays per billing period, e.g.”
    • billingstring“How the price is billed (default monthly)”
    • currencystring“Three-letter currency code of the price (default USD)”
    • commissionPercentnumber“A commission rate the person is considering, e.g.”
  • get_linkjolt_plans

    “LinkJolt's plans and prices, each plan's monthly tracked-sales limit, what this connector can do on each plan, and how the free trial works.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • switch_from_another_tool

    “How to move an affiliate program to LinkJolt from Rewardful, Tolt, FirstPromoter or Affonso, or from anything else by CSV: the page where the person pastes their old tool's API key, and what happens …”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • fromstringrequired“The affiliate tool the program runs on today; other for anything else (a CSV).”
  • get_setup_statuson 6 other servers

    “Where this LinkJolt account is in setting up its affiliate program: the business name and website, the launch steps (business details, campaign, payment connection, first affiliate, first sale) with …”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • update_businesson 1 other server

    “Set the business name and website for this LinkJolt account (the brand the connection belongs to).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    2 inputs
    • businessNamestring“The business or product name, at least 2 characters”
    • websitestring“The website, e.g.”
  • create_campaignon 26 other servers

    “Create an affiliate campaign: what affiliates earn per sale and where their links send people.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    13 inputs, 3 required
    • namestringrequired“Campaign name affiliates see, at least 2 characters”
    • commissionTypestringrequired“Percentage of the sale, or a fixed amount per sale”
    • commissionValuenumberrequired“The percent (e.g.”
    • targetUrlstring“Where affiliate links send people, usually the business's website or pricing page”
    • descriptionstring“What the program offers, shown to affiliates”
    • isPublicboolean“List the campaign in the Discovery marketplace (default true)”
    • autoApproveAffiliatesboolean“Approve affiliates who join through the join link without review (default false)”
    • enableRecurringCommissionsboolean“Also pay commission on subscription renewals (default false)”
    • recurringCommissionTypestring“Renewals pay the same rate as the first sale, or a custom rate (default same)”
    • recurringCommissionValuenumber“The renewal rate when recurringCommissionType is custom”
    • recurringCommissionModestring“Limit renewals by months since the first sale, or by number of payments (default duration)”
    • recurringCommissionDurationMonthsnumber“Months of renewals that pay commission; omit for no limit”
    • recurringCommissionCountnumber“Payments that pay commission, including the first; omit for no limit”
  • update_campaignon 16 other servers

    “Change an existing campaign: its name, description, where links send people, status (active, or inactive to pause it), the commission, whether it is listed in the Discovery marketplace, whether new a…”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    15 inputs, 1 required
    • campaignIdstringrequired“The campaign to change”
    • namestring“New campaign name, at least 2 characters”
    • descriptionstring“New description shown to affiliates”
    • targetUrlstring“Where affiliate links send people”
    • statusstring“active runs the campaign; inactive pauses it”
    • commissionTypestring“Percentage of the sale, or a fixed amount per sale”
    • commissionValuenumber“The percent (e.g.”
    • isPublicboolean“List the campaign in the Discovery marketplace”
    • autoApproveAffiliatesboolean“Approve affiliates who join through the join link without review”
    • enableRecurringCommissionsboolean“Also pay commission on subscription renewals”
    • recurringCommissionTypestring“Renewals pay the same rate as the first sale, or a custom rate”
    • recurringCommissionValuenumber“The renewal rate when recurringCommissionType is custom”
    • recurringCommissionModestring“Limit renewals by months since the first sale, or by number of payments”
    • recurringCommissionDurationMonthsnumber“Months of renewals that pay commission”
    • recurringCommissionCountnumber“Payments that pay commission, including the first”
  • invite_affiliate

    “Email one person an invitation to join a campaign as an affiliate.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world yes

    3 inputs, 2 required
    • campaignIdstringrequired“The campaign to invite them to”
    • emailstringrequired“The person's email address”
    • namestring“The person's name, used in the email greeting”
  • update_affiliate_status

    “Approve or reject an affiliate who applied to a campaign and is waiting for review (list_affiliates with status pending shows who is waiting, with each campaign they applied to).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    3 inputs, 3 required
    • affiliateIdstringrequired“The affiliate who applied”
    • campaignIdstringrequired“The campaign they applied to”
    • actionstringrequired“approve lets them in; reject turns them down”
  • get_tracking_instructions

    “The steps to track affiliate sales on one payment platform, filled in with this account's own tracking script and webhook address: the same text the Integrations page gives to AI assistants.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • platformstringrequired“Where the business takes payment.”
  • check_trackingon 2 other servers

    “Check that affiliate tracking works, after the tracking script has been added: fetches a page of the site (the business website unless url is given) and looks for this account's tag, then says whethe…”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input
    • urlstring“The page to check, e.g.”
  • list_campaignson 42 other servers

    “List the affiliate campaigns on this LinkJolt account (the brand the API key belongs to), with stats.”

    Publisher declares: read-only yes · destructive no · open-world no

    3 inputs
    • pagenumber“Page number, starting at 1 (default 1)”
    • limitnumber“Results per page, max 100 (default 25)”
    • sortstring“Sort as field:direction, e.g.”
Show 16 more tools
  • get_campaignon 27 other servers

    “Get one campaign with full detail, including affiliate count.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • campaignIdstringrequired“The campaign id”
  • list_affiliateson 1 other server

    “List affiliates across your campaigns, with earnings and click counts.”

    Publisher declares: read-only yes · destructive no · open-world no

    5 inputs
    • pagenumber“Page number, starting at 1 (default 1)”
    • limitnumber“Results per page, max 100 (default 25)”
    • campaignIdstring“Only affiliates on this campaign”
    • statusstring“Filter by status”
    • sortstring“Sort as field:direction, e.g.”
  • list_conversionson 11 other servers

    “List conversions (tracked sales) with filters for status, campaign, affiliate and date range.”

    Publisher declares: read-only yes · destructive no · open-world no

    8 inputs
    • pagenumber“Page number, starting at 1 (default 1)”
    • limitnumber“Results per page, max 100 (default 25)”
    • statusstring“Filter by payment status”
    • campaignIdstring“Only conversions for this campaign”
    • affiliateIdstring“Only conversions for this affiliate”
    • fromstring“Only conversions on or after this ISO date”
    • tostring“Only conversions on or before this ISO date”
    • sortstring“Sort as field:direction, e.g.”
  • get_statson 134 other servers

    “Get aggregate stats for the brand: revenue, commissions, conversions, clicks (optionally within a date range), with money also listed per currency in byCurrency.”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs
    • fromstring“Start of the range as an ISO date”
    • tostring“End of the range as an ISO date”
  • create_conversionon 1 other server

    “Manually record a conversion (a sale to credit to an affiliate).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    10 inputs, 3 required
    • campaignIdstringrequired“The campaign the sale belongs to”
    • affiliateIdstringrequired“The affiliate to credit”
    • amountnumberrequired“Sale amount (positive, major units, e.g.”
    • orderIdstring“Your order reference; duplicates are rejected”
    • clickIdstring“Originating click id, when known”
    • customerEmailstring“Buyer email (enables fraud checks)”
    • customerNamestring“Buyer name, shown on the commissions page”
    • conversionTypestring“Defaults to one_time”
    • parentConversionIdstring“For recurring: the original conversion id”
    • currencystring“3-letter ISO code; defaults to the campaign currency”
  • update_conversion

    “Approve or reject a pending conversion.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    3 inputs, 2 required
    • conversionIdstringrequired“The conversion id”
    • statusstringrequired“New status”
    • confirmAboveSaleboolean“Approve even though the commission is more than 5 times its sale.”
  • list_teamson 19 other servers

    “List Affiliate Teams with rosters, targets and pending awards.”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs
    • pagenumber“Page number, starting at 1 (default 1)”
    • limitnumber“Results per page, max 100 (default 25)”
  • get_teamon 27 other servers

    “Get one Affiliate Team with members, campaigns and goals.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • teamIdstringrequired“The team id”
  • list_team_goalson 1 other server

    “List a team's targets and current-period progress.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • teamIdstringrequired“The team id”
  • list_awards

    “List team bonus awards across all teams, for reconciliation.”

    Publisher declares: read-only yes · destructive no · open-world no

    6 inputs
    • pagenumber“Page number, starting at 1 (default 1)”
    • limitnumber“Results per page, max 100 (default 25)”
    • statusstring“Filter by award status”
    • periodKeystring“Filter by period, e.g.”
    • affiliateIdstring“Only awards for this affiliate”
    • teamIdstring“Only awards for this team”
  • list_couponson 12 other servers

    “List registered affiliate coupon codes.”

    Publisher declares: read-only yes · destructive no · open-world no

    6 inputs
    • pagenumber“Page number, starting at 1 (default 1)”
    • limitnumber“Results per page, max 100 (default 25)”
    • campaignIdstring“Only coupons for this campaign”
    • affiliateIdstring“Only coupons for this affiliate”
    • providerstring“Filter by provider”
    • codestring“Look up one code”
  • create_couponon 4 other servers

    “Give an affiliate a discount code so sales using it are credited to them.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world yes

    16 inputs, 3 required
    • campaignIdstringrequired“The campaign the coupon belongs to”
    • affiliateIdstringrequired“The affiliate the code is attributed to”
    • codestringrequired“The readable code, e.g.”
    • createInProviderboolean“Create the code in the brand's connected Stripe, Polar or Creem instead of registering one that already exists”
    • durationstring“With createInProvider: how long the discount lasts for a customer”
    • durationInMonthsnumber“With duration repeating: for how many months (1-36)”
    • descriptionstring“With createInProvider: the discount's name in the payment platform (default: the code)”
    • providerstring“Where the discount lives (default stripe when registering; with createInProvider, the platform the brand creates codes in)”
    • stripePromotionCodeIdstring“Registering a Stripe code: its promotion code id (promo_...).”
    • paddleDiscountIdstring“Registering a Paddle code: its discount id (dsc_...)”
    • polarDiscountIdstring“Registering a Polar code: its discount id”
    • creemDiscountIdstring“Registering a Creem code: its discount id (dis_...)”
    • appleOfferTypenumber“Apple offer type: 1 introductory, 2 promotional, 3 offer code”
    • percentOffnumber“Percent off (1-100): the real discount with createInProvider, a label when registering”
    • amountOffnumber“Fixed amount off, with currency: the real discount with createInProvider, a label when registering”
    • currencystring“3-letter ISO code for amountOff”
  • list_payoutson 4 other servers

    “List the affiliate payout queue for reconciliation.”

    Publisher declares: read-only yes · destructive no · open-world no

    7 inputs
    • pagenumber“Page number, starting at 1 (default 1)”
    • limitnumber“Results per page, max 100 (default 25)”
    • statusstring“Filter by payout status”
    • affiliateIdstring“Only payouts for this affiliate”
    • conversionIdstring“Only payouts for this conversion”
    • fromstring“Only payouts on or after this ISO date”
    • tostring“Only payouts on or before this ISO date”
  • searchon 906 other servers

    “Use this to find records in the caller's own LinkJolt affiliate program by free text: campaign names, affiliate names or emails, coupon codes, and conversion order ids or customer names.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • querystringrequired“Search text, at least 2 characters”
  • get_program_overview

    “This month's program snapshot in one call: revenue, conversions, commissions, top affiliates by commission, and the most recent conversions.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • fetchon 509 other servers

    “Use this to fetch the full record behind a search result id (campaign:<id>, affiliate:<id>, coupon:<id>, or conversion:<id>).”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • idstringrequired“A composite id returned by the search tool”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-03.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 116
Tools with a description
100% of 28
Typical description length
326 characters

The tool set

Counted from the listing

Tools
28
Size of the list
about 7,718 tokens for an agent to load (characters ÷ 4)
Naming
26 of 28 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 28 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-03 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://www.linkjolt.io/api/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "linkjolt": {
      "url": "https://www.linkjolt.io/api/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "linkjolt": {
      "type": "http",
      "url": "https://www.linkjolt.io/api/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"linkjolt","type":"http","url":"https://www.linkjolt.io/api/mcp"}'
Claude Code
claude mcp add --transport http linkjolt https://www.linkjolt.io/api/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "linkjolt": {
      "type": "streamableHttp",
      "url": "https://www.linkjolt.io/api/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "linkjolt": {
      "httpUrl": "https://www.linkjolt.io/api/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.linkjolt]
url = "https://www.linkjolt.io/api/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "linkjolt": {
      "url": "https://www.linkjolt.io/api/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://www.linkjolt.io/api/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint www.linkjolt.io/api/mcpSession openedmatchesour test · 2026-11-03
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-03

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-03. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.linkjolt/linkjolt

Answered from the data above

Who publishes io.linkjolt/linkjolt?

The registry ties the namespace io.linkjolt to the domain linkjolt.io; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does io.linkjolt/linkjolt need an API key or sign-in?

It opened a session without any credential on 2026-11-03. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.linkjolt/linkjolt been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-03
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 5
  • 1Inventory
    tool-list    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn    Checks prompts that pose as the assistant's own words.exercised
  • 18Sign-in metadata
    oauth-url-scheme    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 2
  • 14Token passthrough
    token-passthrough    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-03, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,270 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 28 tools, 1 resource, 3 prompts.
  4. 5,937 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-11-03; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
remote (hosted by the publisher)
registry · 2026-11-03
MCP capability
prompts, resources, tools, extensions
our test · 2026-11-03
Transport
streamable HTTP
registry · 2026-11-03
Required credentials
none declared
registry · 2026-11-03 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-03
Lifecycle status
active
registry · 2026-11-03
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-03

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.linkjolt/linkjolt: MCP server record.” Data checked 2026-11-03. https://protocolprobe.com/mcp/servers/io.linkjolt/linkjolt

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.linkjolt/linkjolt)](https://protocolprobe.com/mcp/servers/io.linkjolt/linkjolt)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology