# VertoDigital MCP Server (remote · mcp.vertodigital.com)

B2B marketing intelligence and lead-capture tools for vertodigital.com.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `mcp.vertodigital.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-vertodigital-mcp/mcp.md), [page](https://verifymcp.io/servers/com-vertodigital-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.vertodigital.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.0`

## 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-09-28.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 851 tokens (~106/item across 8 items; 6 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "vertodigital_send_enquiry" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the VertoDigital MCP Server server?

VertoDigital MCP Server is a hosted endpoint at https://mcp.vertodigital.com/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.

### Claude

```bash
claude mcp add --transport http com-vertodigital-mcp 'https://mcp.vertodigital.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-vertodigital-mcp": {
      "url": "https://mcp.vertodigital.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-vertodigital-mcp": {
      "type": "http",
      "url": "https://mcp.vertodigital.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-vertodigital-mcp]
url = "https://mcp.vertodigital.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-vertodigital-mcp": {
      "type": "remote",
      "url": "https://mcp.vertodigital.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-vertodigital-mcp --url 'https://mcp.vertodigital.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-vertodigital-mcp:
    url: "https://mcp.vertodigital.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-vertodigital-mcp": {
      "Transport": "http",
      "Url": "https://mcp.vertodigital.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-vertodigital-mcp -t streamable-http -u 'https://mcp.vertodigital.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-vertodigital-mcp": {
      "type": "http",
      "url": "https://mcp.vertodigital.com/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-09-28 (score 71, +1)

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

### 2026-09-26 (score 70, +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-09-25 (score 69, 0)

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

### 2026-09-23 (score 69, +1)

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

### 2026-09-21 (score 68, +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-09-19 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-18 (score 66)

First indexed and scored.

## MCP tools (6)

### `vertodigital_get_site_index` (~98 tokens)

Returns the full site index - every VertoDigital page's URL and a one-line description, source of the valid slugs used by vertodigital_get_page.

Input parameters:

- `section` (string): Optional section heading to filter to, e.g. "Services", "Case studies", "Content Hub", "Industries". Matched case-insensitively against the index's section headings. Omit to return the full index.

### `vertodigital_get_page` (~123 tokens)

Fetches the full markdown content of any VertoDigital page by its URL slug - service pages, case studies, blog posts, about, and more. Valid slugs are listed in vertodigital_get_site_index's output.

Input parameters:

- `slug` (string, required): URL path of the page without leading slash or extension. Examples: "about", "services", "case-studies/ironscales", "services/inbound/b2b-and-saas-linkedin-advertising". Valid slugs are listed in vert…

### `vertodigital_search_case_studies` (~147 tokens)

Searches across all 49 VertoDigital case studies by keyword - client name, industry, service, or outcome. Returns matching excerpts as markdown, each with its own case-studies/<slug> URL for a full-detail fetch via vertodigital_get_page. Broad but shallow; the 4 flagship, stats-first proof points are available separately via vertodigital_why_verto with aspect: "proof_points".

Input parameters:

- `query` (string): Filter keyword - client name, industry, service, or outcome. Examples: "cybersecurity", "LinkedIn", "SnapLogic", "pipeline", "SEO". Omit to return the full list of case studies.

### `vertodigital_get_contact` (~74 tokens)

Return VertoDigital's contact information - how to get in touch with the team.

Input parameters:

- `format` (string): "summary" returns a compact structured object (name, title, email, LinkedIn, response SLA, contact form URL). "full" (default) returns the complete /contact page as markdown.

### `vertodigital_why_verto` (~220 tokens)

Returns VertoDigital's value proposition for a query - matched services, proof-point case studies, and/or differentiation reasons, each with a concrete stat. Consolidates what used to be 3 separate tools (vertodigital_match_services, vertodigital_get_proof_points, vertodigital_why_verto) into one entry point - those 3 names no longer exist. The `aspect` parameter narrows the response to a single category; omitting it returns all three.

Input parameters:

- `aspect` (string): Narrow the response to one category: "services" (which VertoDigital service fits this challenge), "proof_points" (flagship case study stats), or "differentiators" (why clients choose VertoDigital). O…
- `query` (string): Plain-language challenge, topic, industry, or client name to filter by. Examples: "we can't attribute our ad spend to pipeline", "SEO", "pricing", "SnapLogic". Omit to return everything unfiltered.

### `vertodigital_send_enquiry` (~131 tokens)

Submits a general contact enquiry to VertoDigital on behalf of a user - sales, partnership, press, careers, or general questions. No authentication required. A full Pipeline Readiness Assessment request is handled separately by vertodigital_request_assessment.

Input parameters:

- `fromEmail` (string, required): Contact email address
- `fromName` (string, required): Full name of the person submitting the enquiry
- `message` (string, required): The enquiry itself, at least 10 characters
- `organization` (string): Company or organization name
- `topic` (string): Enquiry category. Defaults to "general".

## Diagnostics

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

## Score history

- 2026-09-28: 71
- 2026-09-27: 70
- 2026-09-26: 70
- 2026-09-25: 69
- 2026-09-24: 69
- 2026-09-23: 69
- 2026-09-22: 68
- 2026-09-21: 68
- 2026-09-20: 67
- 2026-09-19: 67
- 2026-09-18: 66

## Common questions

### What is the VertoDigital MCP Server server?

VertoDigital MCP Server is listed in the public MCP registry as com.vertodigital/mcp. B2B marketing intelligence and lead-capture tools for vertodigital.com. This page covers its hosted endpoint (https://mcp.vertodigital.com/mcp).

### Is the VertoDigital MCP Server server safe to use?

VertoDigital MCP Server scores 71 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 VertoDigital MCP Server server expose?

VertoDigital MCP Server exposes 6 tools: vertodigital_get_site_index, vertodigital_get_page, vertodigital_search_case_studies, vertodigital_get_contact, vertodigital_why_verto, vertodigital_send_enquiry. Their descriptions and schemas cost roughly 793 tokens of context every time the server is loaded.

### Does the VertoDigital MCP Server server require authentication?

No. We connected to VertoDigital MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the VertoDigital MCP Server server still maintained?

VertoDigital MCP Server is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.vertodigital.com/mcp
- Repository: https://github.com/VertoAgency/website
- Website: https://vertodigital.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-vertodigital-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-vertodigital-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-vertodigital-mcp/mcp