# Clutch.co (remote · bot.clutch.co)

Trusted B2B service providers with verified client reviews

- Trust score: 69/100 (medium)
- Change this week: +9
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `bot.clutch.co`: 69/100 (this document), [markdown](https://verifymcp.io/servers/co-clutch-mcp/bot.md), [page](https://verifymcp.io/servers/co-clutch-mcp/bot)

## Channel facts

- Endpoint: `https://bot.clutch.co/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 37/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

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

### Codex

```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
    }
  }
}
```

### OpenClaw

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

### Hermes

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

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 69, +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.

### 2026-07-31 (score 68, +6)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 62, +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.

### 2026-07-28 (score 61, +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.

### 2026-07-27 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (3)

### `get_service_provider_reviews` (~118 tokens)

Get Service Provider's Reviews

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 parameters:

- `company_name` (string, required): 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

Output parameters:

- `result`

### `recommend_service_providers` (~476 tokens)

Recommend Service Providers

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 parameters:

- `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, required): The type of service the user is looking for (e.g., 'Web Development', 'Digital Marketing').

Output parameters:

- `result`

### `get_service_packages` (~251 tokens)

List Service Packages

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 parameters:

- `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, required): The type of service for which to retrieve packages

Output parameters:

- `result`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-clutch-mcp/bot#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 69
- 2026-08-01: 68
- 2026-07-31: 68
- 2026-07-30: 62
- 2026-07-29: 62
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 60

## Links

- Remote endpoint: https://bot.clutch.co/mcp
- Website: https://clutch.co/about-mcp
- Changelog RSS feed: https://verifymcp.io/servers/co-clutch-mcp/bot/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-clutch-mcp/bot/changelog.json
- HTML version of this page: https://verifymcp.io/servers/co-clutch-mcp/bot