_ registry / mcp http-sse · checked 2h ago

marketing_mcp

https://marketing-mcp.mcpize.run

Registry code: adb482e089e6af87

api record

Marketing MCP — SEO keyword analysis, meta tag extraction, word frequency. Zero auth.

endpoint
https://marketing-mcp.mcpize.run/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 marketing_mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is marketing_mcp free to use?
No — it charges per call, from 0 USDC, quoted in its own 402 answers.
What tools does marketing_mcp have?
4 tools: analyze_seo_keywords, extract_meta_tags, word_frequency, health_check.
Is marketing_mcp 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
98.4%

90 days 98.7%· all time 98.7%

latency
328ms

last good check

priced tools
1

of 4 tools

_ answered our checks, 90 days 621 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • extract seo keywords from copy
  • extract meta tags from a page
  • count word frequencies in text
takes → gives
text, web pages → data
tools
4 reads
_ 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 4 tools
1 paid 3 never probed 1 of 4 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.

  • health_check reads 0 USDC paid 2h ago

    Server health check.

    mcp-tool

    {
      "type": "object",
      "title": "health_checkArguments",
      "properties": {}
    }
    arguments 5 lines
  • analyze_seo_keywords reads unknown never probed

    Extract top SEO keywords from marketing copy using term frequency. Returns: {keywords: [{word, score}], total_words}

    mcp-tool

    {
      "type": "object",
      "title": "analyze_seo_keywordsArguments",
      "required": [
        "text"
      ],
      "properties": {
        "text": {
          "type": "string",
          "title": "Text"
        },
        "top_n": {
          "type": "integer",
          "title": "Top N",
          "default": 15
        }
      }
    }
    arguments 18 lines
  • extract_meta_tags reads unknown never probed

    Fetch a page and extract HTML meta tags (title, description, og:*). Returns: {title, description, og_title, og_description, meta: {name: content}}

    mcp-tool

    {
      "type": "object",
      "title": "extract_meta_tagsArguments",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "title": "Url"
        }
      }
    }
    arguments 13 lines
  • word_frequency reads unknown never probed

    Count word frequencies in text for content/marketing analysis. Returns: {words: [{word, count, pct}], total}

    mcp-tool

    {
      "type": "object",
      "title": "word_frequencyArguments",
      "required": [
        "text"
      ],
      "properties": {
        "text": {
          "type": "string",
          "title": "Text"
        },
        "top_n": {
          "type": "integer",
          "title": "Top N",
          "default": 20
        }
      }
    }
    arguments 18 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 adb482e089e6af87.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/adb482e089e6af87/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/adb482e089e6af87/badge.svg)](https://brick.blue/agent/adb482e089e6af87?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
80%

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.

_ also on mcpize.run 47 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

39 more sit on this domain. All of them.