AgentArmorHQ
Sign in

@workpowers/speckle

MCP server · npm · graded 2026-10-27Source linked

Local MCP router for Speckle — resolves project context from a committed .speckle marker and forwards calls to the remote Speckle MCP endpoint.

No outside reports on file

@workpowers/speckle is distributed via npm (@workpowers/speckle); review its source code, dependencies, and requested permissions before use.

Based on public adoption and transparency signals as of Oct 27, 2026. Our opinion, not a code audit or security guarantee.

Was this verdict for @workpowers/speckle helpful?

What it can access

  • Local filesNo local folder access notedLOW
  • Command executionNo shell command runner notedLOW
  • Network reachLocal or standard API callsLOW
  • CredentialsNo API token requiredLOW
  • Package sourcenpm (@workpowers/speckle)PUBLIC

Inferred from this listing’s public package details and description. Check the project’s source before installing.

Install

npx -y @workpowers/speckle

All setup options ↓

Check this skillWatch it in my stackCompareAdd to allowlistREADME badgeView project

About @workpowers/speckle

@workpowers/speckle is an MCP server focused on Memory & knowledge: Local MCP router for Speckle — resolves project context from a committed .speckle marker and forwards calls to the remote Speckle MCP endpoint.

It is published on npm as @workpowers/speckle and hosted on GitHub at workpowers/speckle. Based on its public metadata, it operates with standard local or API scope without broad shell execution flags noted.

Setup

These use the package this listing points to. Check the project’s own instructions before running anything.

npm command

npx -y @workpowers/speckle

MCP client config

For Claude Desktop (claude_desktop_config.json) or Cursor (.cursor/mcp.json).

json
{
  "mcpServers": {
    "speckle": {
      "command": "npx",
      "args": [
        "-y",
        "@workpowers/speckle"
      ]
    }
  }
}

Why this grade

DD — High risk signals

Signal-based grade (1/7 points): public source code. This reflects adoption and transparency, not a code review.

Popularity and upkeep

4/100
Listing last refreshed
2026-10-27

These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.

Security reports

No reports found for this package in our research (last checked 2026-10-29).

Check a specific version →

Risks to watch for

  • Dependency & version pinning: Distributed via npm (@workpowers/speckle). Pin an exact release version or commit SHA rather than floating tags so upstream updates are reviewed first.

How to lower the risk

Least-privilege permissions

  • Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
  • Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.

Network isolation

  • Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
  • If your IT team can, limit which websites and services it is allowed to contact.

Monitoring

  • Check its activity history or logs weekly at first, and look at what it changed or sent.
  • Turn on alerts for new logins or unusual usage on any account it connects to.

Red flags to watch for

  • It asks for more access than its job requires, or prompts you to paste passwords.
  • It suddenly updates with new owners, or starts contacting unfamiliar websites.

Questions

How do I install @workpowers/speckle?

Run npx -y @workpowers/speckle in your terminal, or add the server entry to your claude_desktop_config.json or .cursor/mcp.json as shown in the Setup section on this page. Full setup docs and environment variables are in github.com/workpowers/speckle.

Are there security reports about @workpowers/speckle?

No reports found for this package in our research (last checked 2026-10-29). @workpowers/speckle currently holds Grade D (High risk signals) based on public adoption and transparency signals. Review the permissions and source repository before granting access to local files, shell commands, or API keys.

Is @workpowers/speckle actively maintained?

We do not have star or download counts on file for @workpowers/speckle yet (listing refreshed 2026-10-27). Check the commit history and open issues at github.com/workpowers/speckle before relying on it.

What are alternatives to @workpowers/speckle?

Compare @workpowers/speckle side by side with similar MCP servers in the Related tools section on this page, or browse all MCP servers on AgentArmorHQ.

README badge and team notes

Maintain or use @workpowers/speckle? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.

AgentArmorHQ Risk Grade D for @workpowers/speckle

GitHub README Markdown:

markdown
[![AgentArmorHQ Risk Grade for @workpowers/speckle](https://agentarmorhq.com/api/badge/workpowers-speckle)](https://agentarmorhq.com/skills/workpowers-speckle)

HTML embed:

html
<a href="https://agentarmorhq.com/skills/workpowers-speckle"><img src="https://agentarmorhq.com/api/badge/workpowers-speckle" alt="AgentArmorHQ Risk Grade for @workpowers/speckle" height="20" /></a>

Terminal check:

terminal
curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "workpowers-speckle"

Share with your security lead

Need sign-off to use @workpowers/speckle? Copy this note for Slack, a ticket or a pull request.

### AgentArmorHQ Security Review Memo: @workpowers/speckle
- **Listing URL:** https://agentarmorhq.com/skills/workpowers-speckle
- **Type:** App connector
- **Risk Grade:** Grade D (High risk signals)
- **Outside Security Advisories on File:** 0

#### Permission & Blast-Radius Signals
- **Local files:** No local folder access noted
- **Command execution:** No shell command runner noted
- **Network reach:** Local or standard API calls
- **Credentials:** No API token required
- **Package source:** npm (@workpowers/speckle)

#### Recommended Hardened Setup
- **Command:** `npx -y --ignore-scripts @workpowers/speckle`
- **Controls:** Pin an exact version in `.mcp.json`, scope access to a single workspace folder, and use a least-privilege read-only token where supported.

_Based on public adoption and transparency signals as of Oct 27, 2026. Our opinion, not a code audit or security guarantee._

Key facts

Type
App connector
Publisher
workpowers
Source code
github.com/workpowers/speckle
Install command
npm install @workpowers/speckle
Est. context load
~850 tokens / turn (~5 tool schemas, 0.43% of 200k context)
Last updated
2026-10-27
Last graded
2026-10-27

Community

Discussions for @workpowers/speckle

Ask questions or share configuration tips. Governed by our Community Rules & Terms.

No posts match this filter yet.

Be the first to ask a question or share a working tip.

Was this listing for @workpowers/speckle helpful?

Check before you install, in Claude

Your assistant answers Block, Review or No known issues for any package before it installs it.

Get this check inside Claude