Parsley - Buyer Intent Signals
REMOTE · WWW.PARSLEY.ID · 2 COMPONENTS · SCANNED SEP 20
Query buyer intent signals, MEDDIC qualifications, and lead scores from Parsley.
Available components
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 → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 594 tokens (~74/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 31% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Parsley - Buyer Intent Signals MCP server?
Parsley - Buyer Intent Signals is a hosted endpoint at https://www.parsley.id/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.parsley.id
claude mcp add --transport http peterjduffy-parsley-mcp 'https://www.parsley.id/api/mcp'
{
"mcpServers": {
"peterjduffy-parsley-mcp": {
"url": "https://www.parsley.id/api/mcp"
}
}
} {
"servers": {
"peterjduffy-parsley-mcp": {
"type": "http",
"url": "https://www.parsley.id/api/mcp"
}
}
} [mcp_servers.peterjduffy-parsley-mcp] url = "https://www.parsley.id/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"peterjduffy-parsley-mcp": {
"type": "remote",
"url": "https://www.parsley.id/api/mcp",
"enabled": true
}
}
} openclaw mcp add peterjduffy-parsley-mcp --url 'https://www.parsley.id/api/mcp' --transport streamable-http
mcp_servers:
peterjduffy-parsley-mcp:
url: "https://www.parsley.id/api/mcp" {
"McpServers": {
"peterjduffy-parsley-mcp": {
"Transport": "http",
"Url": "https://www.parsley.id/api/mcp"
}
}
} assistant mcp add peterjduffy-parsley-mcp -t streamable-http -u 'https://www.parsley.id/api/mcp'
{
"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.
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.
- 26 Aug 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
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 6 Aug 26 0
- Tool “get_hot_leads” changed its title: Get hot leads cosmetic
- Tool “get_conversations” changed its title: List conversations cosmetic
- Tool “get_analytics_summary” changed its title: Get analytics summary cosmetic
- Tool “get_conversation_detail” changed its title: Get conversation detail cosmetic
- Tool “search_by_intent” changed its title: Search by intent cosmetic
- Tool “get_meddic_summary” changed its title: Get MEDDIC summary cosmetic
- Tool “get_lead_enrichment” changed its title: Get lead enrichment cosmetic
- Tool “get_knowledge_gaps” changed its title: Get knowledge gaps cosmetic
8 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 31 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
- 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
- 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
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 20 Sept 2026 · Probed https://www.parsley.id/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.parsley.id | CN=YR1,O=Let's Encrypt,C=US | 23 Aug 2026 | 21 Nov 2026 | RSA 2048 | SHA256-RSA | 6aade1e0c5c9723f1dae09aa713a7377b89 |
| SANs: www.parsley.id | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.parsley.id. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| id. | present | 26887 | 8 | Verified |
| parsley.id. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://*.i.posthog.com https://*.google.com https://*.googleapis.com https://*.firebaseio.com https://*.firebase.com https://cdn.jsdelivr.net https://*.sentry.io https://cdn.tinytalk.ai https://*.gstatic.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https://*.googleapis.com https://*.googleusercontent.com https://*.firebasestorage.app https://firebasestorage.googleapis.com https://media.licdn.com https://images.unsplash.com https://*.i.posthog.com https://dashboard.tinytalk.ai https://tiny-talk-prod-uploads.s3.eu-central-1.amazonaws.com https://image.mux.com https://*.mux.com https://ui-avatars.com; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://*.googleapis.com https://*.google.com https://*.google-analytics.com https://*.firebaseio.com https://*.firebase.com https://*.firebasestorage.app https://*.i.posthog.com https://*.sentry.io wss:/ |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.parsley.id/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.parsley.id/api/mcp | HTTPS enforced | 308 | https://www.parsley.id/api/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_analytics_summary Get analytics summary ~60
Dashboard-level overview: views, conversations, lead counts, conversion rate.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Agency only: target a managed client org by its id to query that client's data. Omit for your own. |
| days | number | – | – |
No output schema declared.
No examples provided.
get_conversation_detail Get conversation detail ~91
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
get_conversations List conversations ~85
List recent chatbot conversations with filtering by lead quality, intent signal, and date range.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
get_hot_leads Get hot leads ~72
Get all hot and warm leads with MEDDIC evidence. The morning briefing tool.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
get_knowledge_gaps Get knowledge gaps ~72
Surface unanswered questions from chatbot conversations, grouped by topic.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
get_lead_enrichment Get lead enrichment ~69
Get extracted company, role, timeline, and budget context from conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
get_meddic_summary Get MEDDIC summary ~57
Aggregate MEDDIC signal distribution across all conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Agency only: target a managed client org by its id to query that client's data. Omit for your own. |
| days | number | – | – |
No output schema declared.
No examples provided.
search_by_intent Search by intent ~88
Find conversations matching specific MEDDIC signals, intent score, or topic.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
What is the Parsley - Buyer Intent Signals MCP server?
Parsley - Buyer Intent Signals is an MCP server listed in the public MCP registry as io.github.peterjduffy/parsley-mcp. Query buyer intent signals, MEDDIC qualifications, and lead scores from Parsley. This page covers its hosted endpoint (https://www.parsley.id/api/mcp).
Is the Parsley - Buyer Intent Signals MCP server safe to use?
Parsley - Buyer Intent Signals scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Parsley - Buyer Intent Signals MCP server expose?
Parsley - Buyer Intent Signals exposes 8 tools: get_conversations, get_conversation_detail, get_hot_leads, get_analytics_summary, search_by_intent, and 3 more. Their descriptions and schemas cost roughly 594 tokens of context every time the server is loaded.
Does the Parsley - Buyer Intent Signals MCP server require authentication?
Yes. Parsley - Buyer Intent Signals asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Parsley - Buyer Intent Signals MCP server still maintained?
Parsley - Buyer Intent Signals is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.