_ registry / mcp http-sse · checked 44m ago

martechdevs

https://www.martechdevs.com

Registry code: 1ba2834b47c1b6be

api record

Practitioner skills for marketing technology work: tracking plans and event naming, UTM and campaign naming, finding where tracking breaks (GA4, Google Tag Manager, server-side tagging, consent mode), purchase reconciliation, attribution and multi-touch attribution, mobile app attribution, choosing analytics tools, Google Ads Editor and negative keywords, HubSpot, Braze, and safe use of vendor MCP servers.

Workflow: call search_skills with the user's task in plain words, then get_skill on the best match and follow its procedure. Skills link to reference files; fetch one with get_skill and the…

endpoint
https://www.martechdevs.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is martechdevs live?
Yes — it answered the hub's last check (checked 44m ago). It answered 100% of checks over the last 30 days.
Is martechdevs free to use?
Yes — the hub reached it with no key and no payment.
What tools does martechdevs have?
3 tools: get_skill, search_skills, list_skills.
Is martechdevs safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
255ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

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.

  • list_skills open 43m ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "area": {
      "enum": [
        "tracking-plans-and-naming",
        "tracking-troubleshooting",
        "web-tracking-setup",
        "ad-conversion-tracking",
        "google-ads-ops",
        "attribution-and-measurement",
        "mobile-app-measurement",
        "product-analytics",
        "crm-revops",
        "lifecycle-messaging",
        "warehouse-and-activation",
        "gtm-engineering",
        "martech-ai-mcp",
        "martech-stack-strategy"
      ],
      "type": "string",
      "description": "Limit the list to one practice area."
    }
  }
}
    arguments 26 lines
  • get_skill unknown 43m ago

    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 example "references/destination-mapping.md").

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "name"
  ],
  "properties": {
    "file": {
      "type": "string",
      "maxLength": 200,
      "description": "Relative path of a file inside the skill folder."
    },
    "name": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "Skill name from search_skills or list_skills, for example \"tracking-plan-builder\"."
    }
  }
}
    arguments 20 lines
  • search_skills unknown 43m ago

    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 and access level. Use get_skill next to read one.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "query"
  ],
  "properties": {
    "area": {
      "enum": [
        "tracking-plans-and-naming",
        "tracking-troubleshooting",
        "web-tracking-setup",
        "ad-conversion-tracking",
        "google-ads-ops",
        "attribution-and-measurement",
        "mobile-app-measurement",
        "product-analytics",
        "crm-revops",
        "lifecycle-messaging",
        "warehouse-and-activation",
        "gtm-engineering",
        "martech-ai-mcp",
        "martech-stack-strategy"
      ],
      "type": "string",
      "description": "Limit results to one practice area."
    },
    "limit": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "Maximum results, default 6."
    },
    "query": {
      "type": "string",
      "maxLength": 200,
      "minLength": 2,
      "description": "The task or problem in plain words."
    }
  }
}
    arguments 41 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1ba2834b47c1b6be.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1ba2834b47c1b6be/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1ba2834b47c1b6be/badge.svg)](https://brick.blue/agent/1ba2834b47c1b6be?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

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

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

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.