Clutch.co

REMOTE · BOT.CLUTCH.CO · SCANNED AUG 3

Trusted B2B service providers with verified client reviews

Available components

+9 this week 69 69 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security83

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability37

0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 1064 tokens (~177/item across 6 items; 3 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage97

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
90% of tool parameters carry a description.Partial
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Supports UI / widget rendering.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · bot.clutch.co

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http co-clutch-mcp https://bot.clutch.co/mcp

# ~/.codex/config.toml

[mcp_servers.co-clutch-mcp]
url = "https://bot.clutch.co/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-clutch-mcp": {
      "type": "remote",
      "url": "https://bot.clutch.co/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add co-clutch-mcp --url https://bot.clutch.co/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  co-clutch-mcp:
    url: "https://bot.clutch.co/mcp"

// mcp.json

{
  "mcpServers": {
    "co-clutch-mcp": {
      "type": "http",
      "url": "https://bot.clutch.co/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 60

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://bot.clutch.co/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=clutch.co	CN=WE1,O=Google Trust Services,C=US	30 Jun 2026	28 Sept 2026	ECDSA 256	ECDSA-SHA256	71108c6015dc6d17132ba24cda39f2bf
SANs: clutch.co, *.clutch.co
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC secure

Validation of bot.clutch.co. — Secure

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
co.	present	7786	8	Verified
clutch.co.	present	2371	13	Verified
bot.clutch.co.				Verified address RRset verified with the apex keys

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=2592000

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://bot.clutch.co/mcp	Verified	200
http (plaintext)	http://bot.clutch.co/mcp	HTTPS enforced	301	https://bot.clutch.co/mcp

MCP tools — 3 exposed · ~845 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

get_service_packages List Service Packages ~251

Use this tool when the user wants to see service packages with fixed pricing and scope for a specific type of service. This tool returns standardized packages offered by service providers, including pricing tiers, deliverables, and delivery timelines. Do NOT use this tool for custom project questions (e.g. "How much would it cost to build a custom app?"). It only returns providers' pre-defined, fixed-price packages, not a quote tailored to a specific project; use recommend_service_providers for those needs instead. Examples: - "Show me SEO packages" -> service="SEO" - "What web design packages can I get for $5,000?" -> service="Web Design", budget=5000 - "Marketing packages from agencies in New York" -> service="Digital Marketing", location="New York" Use `page`/`limit` for pagination.

Input Output Examples

Name	Type	Req	Description
budget	—	—	The client's budget to filter packages
limit	integer	—	The number of packages to return per page.
location	—	—	The location to filter packages
page	integer	—	The page number (zero-based) for pagination.
service	string	yes	The type of service for which to retrieve packages

Name	Type	Req	Description
result	—	yes	—

No examples provided.

get_service_provider_reviews Get Service Provider's Reviews ~118

Use this tool when the user asks to see client reviews for a specific service provider (company). It returns detailed reviews that include project information, pricing, scope, client feedback, ratings, and more. Optionally filter reviews by a specific service.

Input Output Examples

Name	Type	Req	Description
company_name	string	yes	The name of the company to get reviews for
limit	integer	—	The maximum number of reviews to return
offset	integer	—	The number of reviews to skip for pagination
service	—	—	The specific service to filter reviews by

Name	Type	Req	Description
result	—	yes	—

No examples provided.

recommend_service_providers Recommend Service Providers ~476

Use this tool when the user is looking for service providers (companies, agencies, consultants, contractors, vendors) and describes requirements such as service type, industry, location, budget and pricing, company size, or specific focus areas (technologies/specialties). The tool returns a ranked list of providers that best match the criteria, including basic profile info and review/rating signals for comparison. Use `offset`/`limit` for pagination. Examples: - "Give me top web development companies for small businesses in the healthcare industry" -> service="Web Development", industry="Healthcare", client_type="Small Business( <$10M)" - "I need to improve SEO of my online store" -> service="SEO" - "I need SEO agencies that specialize in Shopify and have at least 10 reviews" -> service="SEO", focus_areas=["Shopify"], min_reviews=10

Input Output Examples

Name	Type	Req	Description
client_budget	—	—	The dollar amount the user is willing to spend on the project.
client_type	—	—	The type of client the user represents (e.g., 'small business', 'enterprise'). Only set client_type if the user explicitly specifies their business type.
company_size	—	—	The size of the company the user is looking for. This parameter is not budget-dependent, only set if the user explicitly requests it.
find_near_me	boolean	—	Takes user location into account if set to true, but that must be explicitly requested by the user. In that case the location parameter will be ignored.
focus_areas	—	—	—
hourly_rate	—	—	The service company's minimum hourly rate. This parameter is not budget-dependent, only set if the user explicitly requests it.
industry	—	—	The industry the user is in or the project is related to (e.g., 'Medical', 'eCommerce').
limit	integer	—	The number of providers to return.
location	—	—	—
min_reviews	integer	—	Minimum number of reviews a provider must have to be considered. Only set min_reviews if the user explicitly requests a minimum review count.
offset	integer	—	The number of providers to skip (for pagination).
service	string	yes	The type of service the user is looking for (e.g., 'Web Development', 'Digital Marketing').

Name	Type	Req	Description
result	—	yes	—

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	60
27 Jul	60
28 Jul	61
29 Jul	62
30 Jul	62
31 Jul	68
1 Aug	68
2 Aug	69
3 Aug	69