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

speedcontent-social

https://generatecontentwithaiservice-g5zrtckfda-ue.a.run.app

Registry code: 56abf16ec179fef9

api record

Generates social media posts that are humanized and scored against AI detection. Call generate_social_post to start a job, then check_social_job until it completes.

endpoint
https://generatecontentwithaiservice-g5zrtckfda-ue.a.run.app/mcp
protocol
streamable-http ·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 speedcontent-social live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is speedcontent-social free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does speedcontent-social have?
5 tools: generate_social_post, humanize_text, list_social_platforms, check_social_job, score_text.
Is speedcontent-social 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
97.9%

90 days 98.5%· all time 98.5%

latency
149ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 324 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
  • generate a social media post
  • humanize ai-written text
  • score text for ai detection
takes → gives
text → text
tools
4 reads1 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 5 tools
1 open2 auth-required 2 never probed 3 of 5 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_social_platforms reads open 5h ago

    List the platforms generate_social_post supports, with each one's default post length and emoji policy. Costs nothing and makes no network call.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • check_social_job reads auth-required 5h ago

    Look up a social post generation job by id. Returns the finished posts once the job completes, or its current progress while it runs. Costs nothing.

    mcp-tool

    {
      "type": "object",
      "required": [
        "job_id"
      ],
      "properties": {
        "job_id": {
          "type": "string",
          "description": "The job id returned by generate_social_post."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • score_text reads auth-required 5h ago

    Check how machine-written a piece of text reads, using an external AI detector. Returns a score from 0 to 65 where 0 reads as human and anything above 30 is likely to be flagged. Use this on text you have already written to find out whether it will pass before it is published — it is a measurement you cannot make yourself. Costs 8 credits per call.

    mcp-tool

    {
      "type": "object",
      "required": [
        "text"
      ],
      "properties": {
        "text": {
          "type": "string",
          "minLength": 10,
          "description": "The text to score. At least 10 characters."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • generate_social_post changes data unknown never probed

    Write a social media post from scratch for a given platform and topic. Use this when you do not already have a draft — for example to produce several variations at once, or for platforms whose conventions you are unsure of. If you have already written the post yourself, prefer score_text and humanize_text, which check and fix your own wording instead of replacing it. Returns a job id immediately — poll it with check_social_job, which usually completes in 20-90 seconds. Costs credits.

    mcp-tool

    {
      "type": "object",
      "required": [
        "topic",
        "platform"
      ],
      "properties": {
        "tone": {
          "enum": [
            "casual",
            "educational",
            "friendly",
            "humorous",
            "inspirational",
            "professional"
          ],
          "type": "string",
          "description": "Defaults to friendly."
        },
        "emoji": {
          "type": "boolean",
          "description": "Add emoji to the post. Omit for automatic: off on LinkedIn and YouTube, on elsewhere. Set false for a clean post on any platform."
        },
        "topic": {
          "type": "string",
          "minLength": 3,
          "description": "What the post should be about."
        },
        "humanize": {
          "type": "boolean",
          "description": "Rewrite the post to read as human-authored. Omit for automatic: the draft is scored first and humanized only if it reads as machine-written. Skipping it keeps the exact wording and saves credits, since a well-written post often already passes."
        },
        "language": {
          "type": "string",
          "description": "Output language by name. Defaults to English."
        },
        "platform": {
          "enum": [
            "facebook",
            "instagram",
            "linkedin",
            "pinterest",
            "tiktok",
            "twitter",
            "youtube"
          ],
          "type": "string",
          "description": "Target platform. Each has its own style guide and default length."
        },
        "preserve": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Exact lines that must appear verbatim in the finished post — a closing question, a call to action, a tagline. The humanizer rewrites sentences, so anything whose exact wording matters belongs here rather than only in the topic."
        },
        "quantity": {
          "type": "integer",
          "maximum": 10,
          "minimum": 1,
          "description": "How many distinct variations to generate. Defaults to 1."
        },
        "detect_ai": {
          "type": "boolean",
          "description": "Score the post against AI detection and retry if it reads as machine-written. Adds 8 credits per post. Omit for automatic: runs only at 150+ words, because short posts score unreliably."
        },
        "brand_name": {
          "type": "string",
          "description": "Brand to mention where it reads naturally."
        },
        "brand_tone": {
          "type": "string",
          "description": "Voice guidance, e.g. 'Direct, no jargon'."
        },
        "word_count": {
          "type": "integer",
          "maximum": 500,
          "minimum": 10,
          "description": "Target length per post. Omit to use the platform default (LinkedIn 100, YouTube 150, Facebook/Pinterest 75, Instagram/TikTok 50, X 40)."
        },
        "brand_audience": {
          "type": "string",
          "description": "Who the post should speak to."
        },
        "brand_keywords": {
          "type": "string",
          "description": "Comma-separated terms to work in."
        },
        "generate_image": {
          "type": "boolean",
          "description": "Generate a matching image for the post. Defaults to false over MCP; pass true to request one. Adds 10 credits per post."
        },
        "brand_description": {
          "type": "string",
          "description": "What the business does."
        }
      },
      "additionalProperties": false
    }
    arguments 99 lines
  • humanize_text reads unknown never probed

    Rewrite text so it no longer reads as machine-written, using an external humanizing service. Use this on your own writing when score_text says it would be flagged. Brand names, domains and any lines listed in `preserve` are restored verbatim afterwards, because the humanizer rewrites whole sentences and splits names. Costs 1 credit per 20 words.

    mcp-tool

    {
      "type": "object",
      "required": [
        "text"
      ],
      "properties": {
        "text": {
          "type": "string",
          "minLength": 10,
          "description": "The text to rewrite. At least 10 characters."
        },
        "preserve": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Exact lines that must survive verbatim — a tagline, a call to action, a closing question."
        },
        "brand_terms": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Names that must not be altered, e.g. a product name the humanizer would otherwise split into two words."
        },
        "score_after": {
          "type": "boolean",
          "description": "Score the rewritten text and return it. Adds 8 credits. Defaults to false."
        }
      },
      "additionalProperties": false
    }
    arguments 32 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 56abf16ec179fef9.

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

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.