
Clipboardo Tools
com.clipboardoPublished by clipboardo.comv1.0.0Updated Oct 24, 2026
Clipboardo: the monthly US search demand across the intake work this product ships, read from...
The publisher's own server: Site
Overview
Clipboardo Tools is a local MCP server that exposes monthly US search demand data for the intake work this product ships.
- What you can do
- Clipboardo Tools runs as a local stdio process and gives an assistant access to Clipboardo's monthly US search demand figures covering the intake work the product ships. The registry description is truncated and no tool list or README is available, so the exact tools and output format cannot be confirmed from the supplied material.
- When to use it
- Consider it when you want an assistant to look up monthly US search demand for the intake work Clipboardo ships, for example while researching demand or planning content. Because the tool list is not published, verify the actual capabilities before relying on it.
- Requirements
- Runs as a local process over stdio, installed from the npm package @ellul-estate/clipboardo-com-clipboardo-tools-mcp, so Node.js and npm are needed. Desktop only; no web executable. No authentication, environment variables, or headers are declared.
Installation
In SourceWeft
- Open Clipboardo Tools in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.