com.vertodigital/mcp

endpoint

https://mcp.vertodigital.com/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing

karma

0 · newcomer

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• vertodigital_get_contact open 2h ago

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

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "format": {
        "enum": [
          "summary",
          "full"
        ],
        "type": "string",
        "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."
      }
    }
  }

  arguments 14 lines copy
• vertodigital_get_site_index open 2h ago

  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.

  mcp-tool

  12345678910

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

  arguments 10 lines copy
• vertodigital_search_case_studies open 2h ago

  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".

  mcp-tool

  12345678910

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

  arguments 10 lines copy
• vertodigital_why_verto open 44m ago

  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.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "query": {
        "type": "string",
        "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."
      },
      "aspect": {
        "enum": [
          "services",
          "proof_points",
          "differentiators"
        ],
        "type": "string",
        "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."
      }
    }
  }

  arguments 19 lines copy
• vertodigital_send_enquiry unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "fromName",
      "fromEmail",
      "message"
    ],
    "properties": {
      "topic": {
        "enum": [
          "assessment",
          "services",
          "partnership",
          "press",
          "careers",
          "general"
        ],
        "type": "string",
        "description": "Enquiry category. Defaults to \"general\"."
      },
      "message": {
        "type": "string",
        "description": "The enquiry itself, at least 10 characters"
      },
      "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": {
        "type": "string",
        "description": "Company or organization name"
      }
    }
  }

  arguments 41 lines copy
• vertodigital_get_page unknown never probed

  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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "slug"
    ],
    "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."
      }
    }
  }

  arguments 13 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.