MCP servers › io.github.CordilleraSarl › clearotron

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.CordilleraSarl/clearotron

Clearotron — trademark clearance that shows its work — the publisher's description

9 of 9 record checks metRead-only · tools listed 2026-10-23Topic: commerce-and-marketing · AI-classifiedversion 0.4.1JavaScriptAGPL-3.0-onlystandard input/output32 tools

Summary

io.github.CordilleraSarl/clearotron is a local MCP server listed in the official MCP registry at version 0.4.1. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 32 tools, 14 resources and 0 prompts.

Record checks

9 of 9 record checks met

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

#385 of 15,112 packages by monthly downloads
Not ranked by stars: 2 stars (ranked from 10)
#72 of 1,074 packages meeting all 9 record checks, by downloads

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: npm · listed version current
License: AGPL-3.0-only
Dependencies: no known high or critical advisories
Repository: public
Tools: 32
Described as changing data: 6 of 32 toolsAI-classified
Topic: commerce-and-marketingAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

6 tools are described as changing something (what_if_run, start_run, stop_run, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

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

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.4.1 (published 2026-10-18).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

32tools

14resources

0prompts

6 of 32 tools are described as changing something (creating, editing, deleting, sending or running).

briefon 10 other serversreads or searches
“START HERE for any 'what do you have on X / what did the search find' question — ONE plain-language briefing of a run, in the client-voiced wording (which search product this run was, overall risk in…”
Publisher declares: read-only yes
1 input, 1 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
list_runson 26 other serversreads or searches
“List the searches this session can see (in progress and finished), newest first.”
Publisher declares: read-only yes
6 inputs
- agentstring
- statestring
- markstring“Find a search by NAME: the mark it cleared, the client it was run for, the project it was run under, or the identifier — case-insensitively, on part of the wor…”
- slugstring“EXACT identifier match, for a caller that already holds one.”
- sendPendingboolean“true = only searches still owed a delivery notification; false = only already-settled ones.”
- limitnumber
list_profileson 48 other serversreads or searches
“List the customer ACCOUNTS the firm runs clearotron clearances for (key + name + industry + their PROJECTS) — the roster the intake step resolves a job's profileKey (and optional projectKey) against.”
Publisher declares: read-only yes
Takes no inputs.
get_runon 21 other serversreads or searches
“ENGINEERING/AUDIT view — full run mechanics: status, every pipeline stage (trigger/outcome), failover facts, artifact validity, and a coverage summary.”
Publisher declares: read-only yes
1 input, 1 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
read_artifacton 3 other serversreads or searches
“Read a run artifact's raw text (or one '# Section', or its front-matter).”
Publisher declares: read-only yes
4 inputs, 2 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
- namestringrequired
- sectionstring“Return only this '# Section'.”
- frontMatterOnlyboolean
list_evidenceon 1 other serverreads or searches
“The records this search considered — every register and common-law entry, including ones the report does not name individually.”
Publisher declares: read-only yes
2 inputs, 1 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
- layerstring
list_searcheson 2 other serversreads or searches
“What the search looked for and where — the searches that came back empty as well as the ones that surfaced something.”
Publisher declares: read-only yes
2 inputs, 1 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
- outcomestring
get_search_coveragereads or searches
“What the search covered and what is still open, in the report's own words — each area with its state (Searched — clean / Partially covered / Open item / Not run this run).”
Publisher declares: read-only yes
1 input, 1 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
list_findingson 14 other serversreads or searches
“Structured findings from the deterministic audit.”
Publisher declares: read-only yes
4 inputs, 1 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
- kindstring
- sourceLayerstring
- groupstring
get_findingon 12 other serversreads or searches
“One finding/negative/audit-trail record by id (F#, NR#, AT#).”
Publisher declares: read-only yes
2 inputs, 2 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
- idstringrequired
traceon 10 other serversreads or searches
“ENGINEERING/AUDIT view — HOW a conclusion was reached; use only when the user asks how/why, not for briefing findings.”
Publisher declares: read-only yes
4 inputs, 2 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
- targetstringrequired“stage | artifact | finding id (F#/NR#/AT#) | 'verdict' | a mark/owner substring”
- depthnumber“upstream recursion depth (default 2)”
- shallowboolean“Fast skeleton: lineage + verdict only, skipping the slow enrichments.”
get_telemetryon 3 other serversreads or searches
“ENGINEERING/AUDIT view — per-run + per-stage execution telemetry (models, tokens, wall, failovers, fail reasons) from run.jsonl + the per-attempt logs.”
Publisher declares: read-only yes
3 inputs, 1 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
- stagestring
- axisstring

Show 20 more tools

get_provider_usagereads or searches
“ENGINEERING/AUDIT view — billed register-search provider call counts for the run, RECOMPUTED live from the ledger (more correct than the cached value) with a drift/low-confidence flag.”
Publisher declares: read-only yes
1 input, 1 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
get_coverageon 45 other serversreads or searches
“What was searched vs what's a gap: per-register-axis presence/validity, the coverage-ledger marker, negative-results count, and per-artifact validity.”
Publisher declares: read-only yes
1 input, 1 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
searchon 763 other serversreads or searches
“Keyword search across one run's artifacts (single-run scope), ranked.”
Publisher declares: read-only yes
5 inputs, 2 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
- querystringrequired
- kindstring
- modestring
- limitnumber
decision_timelineon 1 other serverreads or searches
“ENGINEERING/AUDIT view — the run's DECISION timeline: an ordered milestone list projected from the event log — stages (with trigger and a 'changedFromPrevious' marker when a stage was recomputed), sk…”
Publisher declares: read-only yes
1 input, 1 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
run_changesreads or searches
“Change-feed for monitoring a live run: the timeline events since a timestamp, plus a cursor to poll with.”
Publisher declares: read-only yes
3 inputs, 1 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
- sincestring“Poll cursor — a stable sequence number from a prior call's `cursor` (preferred), OR an ISO timestamp for the first call.”
- kindsarray“Optional event-kind filter.”
diff_artifactreads or searches
“Diff two versions of an artifact (what actually changed between them).”
Publisher declares: read-only yes
5 inputs, 2 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
- namestringrequired“Artifact: registerFindings, narrative, report, placement, a register axis (e.g.”
- astring“ref for THIS run: canonical | _history/<dir> | _experiments/<dir> (must be a real snapshot of this artifact; absolute/`..` paths are rejected).”
- bstring“ref (same grammar as a).”
- axisstring“Required (and validated against the known axes) only if name is a bare 'register-unit'.”
search_runson 1 other serverreads or searches
“Cross-run search across ALL runs (in-flight + archived) — e.g.”
Publisher declares: read-only yes
8 inputs, 1 required
- querystringrequired
- modestring
- scopestring
- agentstring
- statestring
- slugstring
- maxRunsnumber
- limitnumber
what_if_plan
“DRY-RUN a what-if (no spend), in one of two kinds.”
Publisher declares: read-only yes
6 inputs, 1 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
- kindstring“'stage' (default) re-runs one stage of a live run; 'memo' reasons over a delivered run's archived evidence.”
- stagestring“Required for kind 'stage'.”
- axisstring
- instructionsstring“For kind 'memo' this is REQUIRED and is the assumption to apply, in the reader's own words.”
- modelstring
what_if_rundescribed as changing data
“EXECUTE a planned what-if (SPENDS tokens / maybe billed calls): re-runs ONE stage in a sandbox (original untouched) and diffs it.”
Publisher declares: read-only no
2 inputs, 1 required
- confirmationTokenstringrequired
- runIdstring“The run's full runId (slug-date-codename) OR just its codename.”
what_if_resultreads or searches
“Collect a QUEUED what-if: its state (queued | running | done | failed) and, once done, the diff against the canonical run.”
Publisher declares: read-only yes
2 inputs, 1 required
- runIdstringrequired“The run's full runId (slug-date-codename) OR just its codename.”
- experimentIdstring
describe_optionson 1 other serverreads or searches
“START HERE before composing a search — the option space, for free.”
Publisher declares: read-only yes
1 input
- profileKeystring“OPTIONAL: the customer ACCOUNT key to describe.”
plan_runreads or searches
“FREE PREVIEW — resolve what a search WOULD do and return it, spending nothing and queueing nothing.”
Publisher declares: read-only yes
23 inputs, 1 required
- markNamestring“The mark (single-mark form).”
- marksarray
- classesarray
- goodsstring
- jurisdictionsarray“WHERE the search points — and, for a clearance, WHICH search it is: one country is a full-country-search, a region or two-or-more countries a multi-country-foc…”
- platformsarray
- customerstring
- profileKeystring“The customer ACCOUNT key (see list_profiles).”
- projectKeystring
- forwarderstringrequired“Requester/reply-routing key — same as start_run, so the preview describes the job that would actually be built.”
- forwarderEmailstring
- refstring
- productstring“WHICH of the four searches.”
- nativeLanguageboolean“OPTIONAL, and only on a multi-country-focus-search: the native-language investigation.”
- worldwideboolean“Search EVERYWHERE, and refuse to be narrowed by the account's own default territories.”
- recipeKeystring
- upfrontInstructionsstring
- deadlinestring
- deliveryRoutestring“OPTIONAL: how the delivered packet leaves — email (default).”
- commercialFlexibilitystring
- priorUsestring
- campaignShapestring“Campaign-shape FACTS from the request/client — how the mark will be deployed: standalone brand vs flavour/sub-brand under a NAMED house mark; seasonal/limited …”
- customerUnknownboolean
start_runon 6 other serversdescribed as changing data
“OPS-ONLY.”
Publisher declares: read-only no
35 inputs, 1 required
- agentstring“Which agent workspace's queue.”
- markNamestring“The mark (single-mark form).”
- marksarray“Batch form: EVERY name of the batch in ONE job.”
- classesarray“Nice classes — whole numbers 1–45 (1–34 goods, 35–45 services).”
- goodsstring
- jurisdictionsarray“WHERE the search points — and, for a clearance, WHICH search it is: one country is a full-country-search, a region or two-or-more countries a multi-country-foc…”
- platformsarray“OPTIONAL per-run SCOPE: extra marketplaces to sweep, as bare store domains e.g.”
- customerstring
- profileKeystring“The customer ACCOUNT key (see list_profiles) whose profile rates this run; omit for the neutral generic profile — that is how a clearance for a NEW client runs…”
- forwarderstringrequired“Requester/reply-routing key — rides the delivery packet so the integrator knows who gets the report (docs/DELIVERY.md).”
- forwarderEmailstring
- refstring
- providerstring
- briefstring
- upfrontInstructionsstring
- projectKeystring“OPTIONAL (spec 62): the PROJECT/engagement key UNDER profileKey (see that customer's projects[] in list_profiles) whose overlay rates this run; omit to run on …”
- productstring“WHICH of the four searches.”
- nativeLanguageboolean“OPTIONAL, and only on a multi-country-focus-search: the native-language investigation.”
- worldwideboolean“Search EVERYWHERE, and refuse to be narrowed by the account's own default territories.”
- recipeKeystring“OPTIONAL alternative selector: a saved search (recipe) slug for this customer.”
- deliveryRoutestring“OPTIONAL: how the delivered packet leaves — email (default).”
- parentRunIdstring“OPTIONAL escalation lineage: the runId this run escalates from (e.g.”
- deliverableSpecstring
- commercialFlexibilitystring
- priorUsestring
and 10 more not listed here.
stop_rundescribed as changing data
“OPS-ONLY.”
Publisher declares: read-only no
5 inputs
- agentstring
- idstring“A queued job id (from start_run) — dequeues before the runner claims it.”
- runIdstring“A started run's runId — files a cancel sentinel.”
- immediateboolean“Stop NOW instead of at the next step boundary.”
- onBehalfOfstring“The identifier of a human this caller has itself verified.”
server_infoon 30 other serversreads or searches
“The AGPL §13 source offer: this server's name, version, licence, source repository and the COMMIT IT IS RUNNING.”
Publisher declares: read-only yes
Takes no inputs.
list_outbox_eventsreads or searches
“Integrator discovery read (docs/DELIVERY.md): every pending outbox event — delivered markers plus the self-contained run-failed / intake-rejected / duplicate-skipped / late-bind-ack packets.”
Publisher declares: read-only yes
Takes no inputs.
get_delivery_packetreads or searches
“The run's send payload: _driver/delivery.json (subject, recipient routing, verbatim emailBodyHtml, whatsapp line) and/or failure.json, plus sendPending/.sent state.”
Publisher declares: read-only yes
1 input, 1 required
- runIdstringrequired
ack_eventdoes something elsedescribed as changing data
“OPS-ONLY.”
Publisher declares: read-only no
1 input, 1 required
- filestringrequired
mark_sentdoes something elsedescribed as changing data
“OPS-ONLY.”
Publisher declares: read-only no
3 inputs, 1 required
- runIdstringrequired
- messageIdstring“The sent email's messageId — the send receipt.”
- attestationstring“Out-of-band evidence when there is no messageId: an explicit statement of how the packet actually reached the reader (channel + when), recorded VERBATIM in .se…”
feed_contextdescribed as changing data
“OPS-ONLY.”
Publisher declares: read-only no
3 inputs, 1 required
- runIdstringrequired
- customerstring
- exclusionsarray

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-10-23.

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

Says what the tool does: 100% of 32 tools
Says what it returns: 100% of 28 tools
States limits, defaults or errors: 14% of 29 tools
Says when to use it: 100% of 32 tools
Items covered per tool: 3.2 of 4 on average

Counted from the listing

Parameters with a description: 51% of 136
Tools with a description: 100% of 32
Typical description length: 414 characters

The tool set

Counted from the listing

Tools: 32
Size of the list: about 9,541 tokens for an agent to load (characters ÷ 4)
Naming: 29 of 32 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 32 of 32 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 npm package clearotron

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "clearotron": {
      "command": "npx",
      "args": [
        "-y",
        "clearotron@0.4.1",
        "mcp"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "clearotron": {
      "command": "npx",
      "args": [
        "-y",
        "clearotron@0.4.1",
        "mcp"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "clearotron": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "clearotron@0.4.1",
        "mcp"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"clearotron","type":"stdio","command":"npx","args":["-y","clearotron@0.4.1","mcp"]}'

Claude Code

claude mcp add --transport stdio clearotron -- npx -y clearotron@0.4.1 mcp

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- npx -y clearotron@0.4.1 mcp

Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
This runs the publisher's code on your machine (npx). Read its README first.
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). 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.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 0.4.1
Latest stable: 0.4.1
Status: current
Withdrawn: no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha512-jn8C9Q0sLXLCu4oVN…
Signature: signed and attested
License: AGPL-3.0-only

Source: the package registry · 2026-10-23.

Usage

Downloads: 5,607 in the last month

Source: api.npmjs.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 0.4.1 on npm	Exists and can be installed	matches	npm · 2026-10-23
Repository github.com/CordilleraSarl/clearotron	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.CordilleraSarl
GitHub owner: an organization (CordilleraSarl)
Build record: signed and attested

Repository: github.com/CordilleraSarl/clearotron
Stars: 2
Repository age: 31–90 days
Last push: 0–30 days ago
Archived: no
Security policy: SECURITY.md

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

9 of 9 record checks met

#385 of 15,112 packages by monthly downloads
Not ranked by stars: 2 stars (ranked from 10)
#72 of 1,074 packages meeting all 9 record checks, by downloads

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
MetPackage names its licence with a standard (SPDX) identifierAGPL-3.0-only
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. 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. How each check works · Leaderboards

Common questions about io.github.CordilleraSarl/clearotron

Answered from the data above

Is io.github.CordilleraSarl/clearotron safe to install?

We do not rate servers as safe or unsafe. 9 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 6 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.CordilleraSarl/clearotron been security tested?

Partly. 3 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.CordilleraSarl/clearotron do?

It lists 32 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and do something else. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.CordilleraSarl/clearotron change or delete data?

6 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.CordilleraSarl/clearotron publish a security policy?

Yes: its repository has a public security policy (github.com/cordillerasarl/clearotron/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 0.4.1, the latest stable release on npm.

Where is the source code of io.github.CordilleraSarl/clearotron?

In github.com/CordilleraSarl/clearotron, which opens publicly.

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.

Similar servers

Same topic · AI-read

app.himalayas/mcpHimalayas Remote Jobsalso has tools that does something else, reads or searchescompare with this one
io.github.askads/mcp-vk-adsVK Ads MCPalso has tools that does something else, reads or searchescompare with this one
io.github.antohins/seo-tools-mcp-ga4SEO Tools: Google Analytics 4also has tools that does something else, reads or searchescompare with this one
io.github.hermoso-ai/hermosoHermosoalso has tools that does something else, reads or searchescompare with this one
io.github.negm17111995/maqami-travelMAQAMI Travelalso has tools that does something else, reads or searchescompare with this one
io.github.nozikov/yandex-mcpYandex Analyticsalso has tools that does something else, reads or searchescompare with this one

Active servers whose topic is also “commerce-and-marketing” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

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

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

3 exercised9 not run (reason given)6 not applicable

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

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised

Not run, with the reason · 9

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants 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
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks 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-dataChecks 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-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks 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

Does not apply to this server · 6

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, 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.

0 msStarted the published package in an isolated sandbox (read-only mode)
116,513 msConnected after 0 redirects.
Read the inventory: 32 tools, 14 resources, 0 prompts.
117,286 msFinished: 3 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

commerce-and-marketing

AI-classified · 2026-10-23

Pricing modelAI-classified

not checked

no website in the registry entry

Programming language

JavaScript

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

prompts, resources, tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

npm

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

copyleft

package registry · 2026-10-23

Integrity hash

declared (sri)

package registry · 2026-10-23

Signature / provenance

signed and attested

package registry · 2026-10-23

Dependency advisories

none known

npm audit · 2026-10-23

Popularity

5,607 downloads a month

package registry · 2026-10-23

Publisher signals

owner: an organization · repository age: 31–90 days · stars: 0–9 · build record: signed and attested

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“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.github.CordilleraSarl/clearotron: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.CordilleraSarl/clearotron

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](https://protocolprobe.com/api/v1/badge/io.github.CordilleraSarl/clearotron)](https://protocolprobe.com/mcp/servers/io.github.CordilleraSarl/clearotron)

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