1 findingStatic scanned
Lets your assistant reason through a problem in numbered steps, revising and branching as it goes.
484.3k installs/moSEE LICENSE IN LICENSE
Clearotron
kwizzlek · MCP server
Clearotron checks whether a company name can be used before the company commits to it. Given the name, the classes and the territories, it searches trademark registers and the open web, places each conflict by mark similarity and goods proximity, and publishes a written report with a machine-readable audit trail behind every finding. It runs headless on your machine, needs a trademark register credential (some registers are paid subscriptions) and a Perplexity API key, and has an MCP server for questioning finished runs.
Written by ooruby from the README of clearotron 0.4.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
You find out what stands in the way of a name before you commit to it, with the record behind every finding.
What you could do with it
- Order a clearance by describing the name, classes and territories in a sentence, or set them yourself.
- Resume an interrupted clearance run so that only the missing stages are searched again.
- Ask your assistant questions about a finished clearance run in plain language through its MCP server.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (package.json:36)
- synchronous shell execution (package.json:36)
- node child_process (shared/bundle-freshness.mjs:18)
- synchronous shell execution (shared/bundle-freshness.mjs:83)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Corrected after a reading by hand on 2026-10-10
- No shipped credentials: the automated note “The scan matched 2 credential-shaped strings in the published files. Location withheld pending disclosure to the maker.” was withdrawn. Names for kinds of failure in an error vocabulary: a field called token holding an identifier, not a credential.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Trademark clearance engine. Searches the registers and the open web, rates the conflicts, and delivers a written report with the record behind every finding.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.4.0, the file with digest sha512-p3ITQMQAtDF0nskn4v/OsEFVt4BhKaoR8F1HKFP3V7wLNyjkCB3qiFt5zZRE8G9sTwz+aAC9bOfiVbgcuXoCZw==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"clearotron": {
"command": "npx",
"args": [
"-y",
"clearotron@0.4.0"
]
}
}
}Or run it directly.
npx -y clearotron@0.4.0Pinned to 0.4.0, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- clearotron
- Version read
- 0.4.0
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/cordillerasarl/clearotron
- Commit
- 9e66ced72d63
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/clearotron)About this listing
- Kind
- MCP server
- Category
- Research
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-09
Similar MCP servers
All MCP serversVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.