Claw Mcp Toolkit MCP Server

claw-mcp-toolkit npm v1.0.0

Published by elromevedelelyon — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

All-in-one MCP server with 32 tools for AI agents. Crypto, Web, Social, Finance, Productivity, Operations. Zero config, zero API keys required.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([web_fetch]) co-exist with external-action tools ([social_generate_tweet]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [web_fetch] → sinks [social_generate_tweet]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow web_fetch → social_generate_tweet

medium Hardcoded egress to an external endpoint (dist/modules/web.js)MTC-SRC-003

In the server's implementation (`dist/modules/web.js:45`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const res = await fetch(`https://${domain}`, { method: "HEAD" }); return { content: [{ type: "text", t

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/modules/web.js

Tools 32

Each tool and what it can reach — statically extracted from the published source.

  • social_generate_tweetnetwork egress
  • web_fetchingests untrusted input
  • buy_stbtcxno sensitive capability
  • crypto_fear_greedno sensitive capability
  • crypto_market_overviewno sensitive capability
  • crypto_priceno sensitive capability
  • crypto_price_historyno sensitive capability
  • crypto_searchno sensitive capability
  • crypto_trendingno sensitive capability
  • finance_expense_logno sensitive capability
Show 22 more tools ↓
  • finance_forex_rateno sensitive capability
  • finance_invoice_generatorno sensitive capability
  • finance_portfolio_trackerno sensitive capability
  • finance_stock_priceno sensitive capability
  • list_productsno sensitive capability
  • productivity_calendar_eventno sensitive capability
  • productivity_noteno sensitive capability
  • productivity_pomodorono sensitive capability
  • productivity_reminderno sensitive capability
  • productivity_task_breakdownno sensitive capability
  • rota_mortal_activateno sensitive capability
  • rota_mortal_pipelineno sensitive capability
  • rota_mortal_statusno sensitive capability
  • social_content_calendarno sensitive capability
  • social_engagement_analyzerno sensitive capability
  • social_hashtag_researchno sensitive capability
  • social_thread_builderno sensitive capability
  • stbtcx_priceno sensitive capability
  • web_dns_lookupno sensitive capability
  • web_extract_linksno sensitive capability
  • web_seo_checkno sensitive capability
  • web_ssl_checkno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 96/100 2 1.13.0 2026-09-08

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/claw-mcp-toolkit/badge.svg)](https://mcptrustchecker.com/registry/claw-mcp-toolkit)
HTML
<a href="https://mcptrustchecker.com/registry/claw-mcp-toolkit"><img src="https://mcptrustchecker.com/registry/claw-mcp-toolkit/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/claw-mcp-toolkit/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan claw-mcp-toolkit --online

Use the free API → How scoring works

More in Web, Search & Scraping