Skip to content
martechdevs logo

martechdevs MCP server

Which MCP servers are martechdevs's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-28

← Back to martechdevs

Whose server it is
  • Registry namecom.martechdevs.www/skillsverified in the MCP registry

The registry name sits under martechdevs.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools3
  • Server calls itselfmartechdevs
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 667 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: trigger lifecycle emails from in-app behaviour and purchase data; measure ad spend against customer lifetime value by channel.
  • Checked on 6 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 6, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • What an agent can do with it0 of 2 use cases
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer146 ms
  • Space in an agent's context≈ 613 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · connect analytics, CRM and ad platforms into one customer dataset
  • cannot · trigger lifecycle emails from in-app behaviour and purchase data
  • cannot · measure ad spend against customer lifetime value by channel

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-28
  • search_skills

    Search the skills library by task, tool or problem, for example "GA4 unassigned traffic", "UTM convention for paid social", "Meta CAPI dedupe" or "HubSpot implementation order". Returns skill names with a one-line summary, practice area…

  • get_skill

    Return one skill as Markdown: when to use it, inputs, procedure, acceptance checks, boundaries and live docs to check. Pass file to read one of the skill's reference, asset or script files, using the relative path the skill links to (for…

  • list_skills

    List every skill in the library by practice area, with a one-line summary and access level, plus how many more are in review.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "skills": {
      "type": "http",
      "url": "https://www.martechdevs.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http martechdevs https://www.martechdevs.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://www.martechdevs.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.