# Parsley - Buyer Intent Signals (remote · www.parsley.id)

Query buyer intent signals, MEDDIC qualifications, and lead scores from Parsley.

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

## Components

- remote · `www.parsley.id`: 77/100 (this document), [markdown](https://verifymcp.io/servers/peterjduffy-parsley-mcp/api-mcp.md), [page](https://verifymcp.io/servers/peterjduffy-parsley-mcp/api-mcp)
- npm · `@tryparsley/mcp-server`: 35/100, [markdown](https://verifymcp.io/servers/peterjduffy-parsley-mcp/tryparsley-mcp-server.md), [page](https://verifymcp.io/servers/peterjduffy-parsley-mcp/tryparsley-mcp-server)

## Channel facts

- Endpoint: `https://www.parsley.id/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.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**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 594 tokens (~74/item across 8 items; 8 tools + 0 resources), lean.
  - 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**: 77/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 31% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http peterjduffy-parsley-mcp https://www.parsley.id/api/mcp
```

### Codex

```toml
[mcp_servers.peterjduffy-parsley-mcp]
url = "https://www.parsley.id/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "peterjduffy-parsley-mcp": {
      "type": "remote",
      "url": "https://www.parsley.id/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add peterjduffy-parsley-mcp --url https://www.parsley.id/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  peterjduffy-parsley-mcp:
    url: "https://www.parsley.id/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "peterjduffy-parsley-mcp": {
      "type": "http",
      "url": "https://www.parsley.id/api/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-03 (score 77, +1)

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

### 2026-08-01 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 75, +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 69, 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 69, +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 68, +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 67, 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 67)

First indexed and scored.

## MCP tools (8)

### `get_conversations` (~85 tokens)

List recent chatbot conversations with filtering by lead quality, intent signal, and date range.

Input parameters:

- `client` (string): Agency only: target a managed client org by its id to query that client's data. Omit for your own.
- `days` (number)
- `intent_signal` (string)
- `lead_quality` (string)
- `limit` (number)

### `get_conversation_detail` (~91 tokens)

Get full details of a single conversation: MEDDIC signals, engagement metrics, enrichment data, and any owner-configured discovery field values captured during the chat (e.g. company size, current tooling, hiring status).

Input parameters:

- `client` (string): Agency only: target a managed client org by its id to query that client's data. Omit for your own.
- `conversation_id` (string, required)

### `get_hot_leads` (~72 tokens)

Get all hot and warm leads with MEDDIC evidence. The morning briefing tool.

Input parameters:

- `client` (string): Agency only: target a managed client org by its id to query that client's data. Omit for your own.
- `days` (number)
- `include_warm` (boolean)

### `get_analytics_summary` (~60 tokens)

Dashboard-level overview: views, conversations, lead counts, conversion rate.

Input parameters:

- `client` (string): Agency only: target a managed client org by its id to query that client's data. Omit for your own.
- `days` (number)

### `search_by_intent` (~88 tokens)

Find conversations matching specific MEDDIC signals, intent score, or topic.

Input parameters:

- `client` (string): Agency only: target a managed client org by its id to query that client's data. Omit for your own.
- `days` (number)
- `meddic_signals` (array)
- `min_intent_score` (number)
- `topic` (string)

### `get_knowledge_gaps` (~72 tokens)

Surface unanswered questions from chatbot conversations, grouped by topic.

Input parameters:

- `client` (string): Agency only: target a managed client org by its id to query that client's data. Omit for your own.
- `days` (number)
- `limit` (number)
- `topic` (string)

### `get_lead_enrichment` (~69 tokens)

Get extracted company, role, timeline, and budget context from conversations.

Input parameters:

- `client` (string): Agency only: target a managed client org by its id to query that client's data. Omit for your own.
- `days` (number)
- `has_company` (boolean)

### `get_meddic_summary` (~57 tokens)

Aggregate MEDDIC signal distribution across all conversations.

Input parameters:

- `client` (string): Agency only: target a managed client org by its id to query that client's data. Omit for your own.
- `days` (number)

## Diagnostics

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

## Score history

- 2026-08-03: 77
- 2026-08-02: 76
- 2026-08-01: 76
- 2026-07-31: 75
- 2026-07-30: 69
- 2026-07-29: 69
- 2026-07-28: 68
- 2026-07-27: 67
- 2026-07-26: 67

## Links

- Remote endpoint: https://www.parsley.id/api/mcp
- Authorisation metadata: https://www.parsley.id/.well-known/oauth-protected-resource/api/mcp
- Repository: https://github.com/peterjduffy/parsley-mcp
- Changelog RSS feed: https://verifymcp.io/servers/peterjduffy-parsley-mcp/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/peterjduffy-parsley-mcp/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/peterjduffy-parsley-mcp/api-mcp