VertoDigital MCP Server

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
93%
Naming quality
77%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (1)

  • LOWTool 'vertodigital_search_case_studies' name length outside 3-30 rangein vertodigital_search_case_studies

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,166Tokens (tool definitions)
~1.4 KBTypical response size
Moderate attention impact (0.91% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://mcp.vertodigital.com/mcpstreamable-http

What it can do

Tool inventory

Tools (6)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢vertodigital_get_site_index(section)

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 Schema

{
  "type": "object",
  "properties": {
    "section": {
      "description": "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.",
      "type": "string"
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢vertodigital_get_page(slug)

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 Schema

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "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 vertodigital_get_site_index's output."
    }
  },
  "required": [
    "slug"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢vertodigital_search_case_studies(query)

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 Schema

{
  "type": "object",
  "properties": {
    "query": {
      "description": "Filter keyword - client name, industry, service, or outcome. Examples: \"cybersecurity\", \"LinkedIn\", \"SnapLogic\", \"pipeline\", \"SEO\". Omit to return the full list of case studies.",
      "type": "string"
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢vertodigital_get_contact(format)

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

Input Schema

{
  "type": "object",
  "properties": {
    "format": {
      "description": "\"summary\" returns a compact structured object (name, title, email, LinkedIn, response SLA, contact form URL). \"full\" (default) returns the complete /contact page as markdown.",
      "type": "string",
      "enum": [
        "summary",
        "full"
      ]
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢vertodigital_why_verto(query, aspect)

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 Schema

{
  "type": "object",
  "properties": {
    "query": {
      "description": "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.",
      "type": "string"
    },
    "aspect": {
      "description": "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). Omit to return all three.",
      "type": "string",
      "enum": [
        "services",
        "proof_points",
        "differentiators"
      ]
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟡vertodigital_send_enquiry(fromName, fromEmail, organization, topic, message)

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 Schema

{
  "type": "object",
  "properties": {
    "fromName": {
      "type": "string",
      "description": "Full name of the person submitting the enquiry"
    },
    "fromEmail": {
      "type": "string",
      "format": "email",
      "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      "description": "Contact email address"
    },
    "organization": {
      "description": "Company or organization name",
      "type": "string"
    },
    "topic": {
      "description": "Enquiry category. Defaults to \"general\".",
      "type": "string",
      "enum": [
        "assessment",
        "services",
        "partnership",
        "press",
        "careers",
        "general"
      ]
    },
    "message": {
      "type": "string",
      "description": "The enquiry itself, at least 10 characters"
    }
  },
  "required": [
    "fromName",
    "fromEmail",
    "message"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded6 tools
verifiedversion not recorded6 tools