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

vibemarketing-mcp

https://vibemarketing.ninja

Registry code: b90d2db5967c6ee3

api record

Social Media · maintained by VibeMarketing · 7 tools: get_accounts, get_all_posts, schedule_post, bulk_schedule_posts, get_subscription_status, delete_post, update_post

from a public catalogue that lists it, not from the operator

endpoint
https://vibemarketing.ninja/mcp
protocol
streamable-http ·2024-11-05
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 vibemarketing-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is vibemarketing-mcp free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does vibemarketing-mcp have?
7 tools: update_post, bulk_schedule_posts, delete_post, get_accounts, get_subscription_status, get_all_posts, schedule_post.
Is vibemarketing-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
100%

90 days 99.7%· all time 99.7%

latency
110ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 351 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
communication social media
used for
  • schedule a social media post
  • bulk schedule posts
  • list connected social accounts
  • update or delete a scheduled post
takes → gives
text, data → data
tools
3 reads4 changes data
_ 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 7 tools
7 auth-required 7 of 7 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.

  • update_post changes data auth-required never probed

    Update a scheduled post (cannot update published posts)

    mcp-tool

    {
  "type": "object",
  "required": [
    "postId",
    "platform"
  ],
  "properties": {
    "postId": {
      "type": "string",
      "format": "uuid",
      "description": "ID of the post to update"
    },
    "content": {
      "type": "string",
      "description": "New content for the post (optional)"
    },
    "platform": {
      "enum": [
        "x",
        "linkedin"
      ],
      "type": "string",
      "description": "Platform the post is on"
    },
    "mediaUrls": {
      "type": "array",
      "items": {
        "type": "string",
        "format": "uri"
      },
      "description": "New media URLs (optional)"
    },
    "scheduledFor": {
      "type": "string",
      "format": "date-time",
      "description": "New scheduled time in ISO 8601 format (optional)"
    }
  }
}
    arguments 39 lines
  • bulk_schedule_posts changes data auth-required never probed

    Schedule multiple social media posts at once (up to 50 posts per batch). More efficient than scheduling posts individually.

    mcp-tool

    {
  "type": "object",
  "required": [
    "posts"
  ],
  "properties": {
    "posts": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "content",
          "platform",
          "accountId",
          "scheduledFor"
        ],
        "properties": {
          "content": {
            "type": "string",
            "maxLength": 10000,
            "minLength": 1,
            "description": "Post content"
          },
          "platform": {
            "enum": [
              "x",
              "linkedin"
            ],
            "type": "string",
            "description": "Social media platform"
          },
          "accountId": {
            "type": "string",
            "format": "uuid",
            "description": "Account ID to post from"
          },
          "mediaUrls": {
            "type": "array",
            "items": {
              "type": "string",
              "format": "uri"
            },
            "description": "Optional media URLs"
          },
          "scheduledFor": {
            "type": "string",
            "format": "date-time",
            "description": "When to publish the post"
          }
        }
      },
      "maxItems": 50,
      "minItems": 1,
      "description": "Array of posts to schedule"
    }
  }
}
    arguments 57 lines
  • delete_post changes data auth-required never probed

    Delete a scheduled post (cannot delete published posts)

    mcp-tool

    {
  "type": "object",
  "required": [
    "postId",
    "platform"
  ],
  "properties": {
    "postId": {
      "type": "string",
      "format": "uuid",
      "description": "ID of the post to delete"
    },
    "platform": {
      "enum": [
        "x",
        "linkedin"
      ],
      "type": "string",
      "description": "Platform the post is on"
    }
  }
}
    arguments 22 lines
  • get_accounts reads auth-required 9h ago

    Get all connected social media accounts across all platforms

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "default": 10,
      "maximum": 100,
      "minimum": 1,
      "description": "Maximum number of accounts to return per platform"
    },
    "platform": {
      "enum": [
        "x",
        "linkedin",
        "all"
      ],
      "type": "string",
      "default": "all",
      "description": "Filter by platform or get all platforms"
    }
  }
}
    arguments 22 lines
  • get_subscription_status reads auth-required 9h ago

    Get current subscription status and usage

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_all_posts reads auth-required never probed

    Get all posts across all platforms

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "default": 20,
      "maximum": 100,
      "minimum": 1,
      "description": "Maximum number of posts to return"
    },
    "status": {
      "enum": [
        "any",
        "draft",
        "scheduled",
        "published",
        "failed"
      ],
      "type": "string",
      "description": "Filter by post status (use \"any\" to get all statuses)"
    },
    "platform": {
      "enum": [
        "x",
        "linkedin",
        "all"
      ],
      "type": "string",
      "default": "all",
      "description": "Filter by platform or get all platforms"
    }
  }
}
    arguments 33 lines
  • schedule_post changes data auth-required never probed

    Schedule a new social media post

    mcp-tool

    {
  "type": "object",
  "required": [
    "content",
    "platform",
    "accountId",
    "scheduledFor"
  ],
  "properties": {
    "content": {
      "type": "string",
      "maxLength": 10000,
      "minLength": 1,
      "description": "Post content"
    },
    "platform": {
      "enum": [
        "x",
        "linkedin"
      ],
      "type": "string",
      "description": "Social media platform"
    },
    "accountId": {
      "type": "string",
      "format": "uuid",
      "description": "Account ID to post from"
    },
    "mediaUrls": {
      "type": "array",
      "items": {
        "type": "string",
        "format": "uri"
      },
      "description": "Optional media URLs"
    },
    "scheduledFor": {
      "type": "string",
      "format": "date-time",
      "description": "When to publish the post"
    }
  }
}
    arguments 43 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 b90d2db5967c6ee3.

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

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.