VertoDigital MCP Server
REMOTE · MCP.VERTODIGITAL.COM · SCANNED SEP 28
B2B marketing intelligence and lead-capture tools for vertodigital.com.
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 851 tokens (~106/item across 8 items; 6 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · mcp.vertodigital.com
claude mcp add --transport http com-vertodigital-mcp 'https://mcp.vertodigital.com/mcp'
{
"mcpServers": {
"com-vertodigital-mcp": {
"url": "https://mcp.vertodigital.com/mcp"
}
}
} {
"servers": {
"com-vertodigital-mcp": {
"type": "http",
"url": "https://mcp.vertodigital.com/mcp"
}
}
} [mcp_servers.com-vertodigital-mcp] url = "https://mcp.vertodigital.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-vertodigital-mcp": {
"type": "remote",
"url": "https://mcp.vertodigital.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-vertodigital-mcp --url 'https://mcp.vertodigital.com/mcp' --transport streamable-http
mcp_servers:
com-vertodigital-mcp:
url: "https://mcp.vertodigital.com/mcp" {
"McpServers": {
"com-vertodigital-mcp": {
"Transport": "http",
"Url": "https://mcp.vertodigital.com/mcp"
}
}
} assistant mcp add com-vertodigital-mcp -t streamable-http -u 'https://mcp.vertodigital.com/mcp'
{
"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.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +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.
- 25 Sept 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
- 23 Sept 26 +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.
- 21 Sept 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.
- 19 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 18 Sept 26 66
First indexed and scored.
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 28 Sept 2026 · Probed https://mcp.vertodigital.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vertodigital.com | CN=WE1,O=Google Trust Services,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a9e1c2f9fba31f910e891afa0624c5c0 |
| SANs: vertodigital.com, *.vertodigital.com | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.vertodigital.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| vertodigital.com. | present | 2371 | 13 | Verified |
| mcp.vertodigital.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.vertodigital.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.vertodigital.com/mcp | HTTPS enforced | 301 | https://mcp.vertodigital.com/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 →
vertodigital_get_contact ~74
Return VertoDigital's contact information - how to get in touch with the team.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
vertodigital_get_page ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | 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… |
No output schema declared.
No examples provided.
vertodigital_get_site_index ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
vertodigital_search_case_studies ~147
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".
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
vertodigital_send_enquiry ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fromEmail | string | yes | Contact email address |
| fromName | string | yes | Full name of the person submitting the enquiry |
| message | string | yes | The enquiry itself, at least 10 characters |
| organization | string | – | Company or organization name |
| topic | string | – | Enquiry category. Defaults to "general". |
No output schema declared.
No examples provided.
vertodigital_why_verto ~220
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.