Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SpeedContent Social

REMOTE · SPEEDCONTENT.ONLINE · SCANNED OCT 6

Generate platform-native social posts that are humanized, AI-detection scored and illustrated.

73 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 946 tokens (~189/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the SpeedContent Social MCP server?

SpeedContent Social is a hosted endpoint at https://speedcontent.online/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · speedcontent.online

# add to Claude Code
claude mcp add --transport http seotrader-speedcontent-social 'https://speedcontent.online/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "seotrader-speedcontent-social": {
      "url": "https://speedcontent.online/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "seotrader-speedcontent-social": {
      "type": "http",
      "url": "https://speedcontent.online/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.seotrader-speedcontent-social]
url = "https://speedcontent.online/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "seotrader-speedcontent-social": {
      "type": "remote",
      "url": "https://speedcontent.online/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add seotrader-speedcontent-social --url 'https://speedcontent.online/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  seotrader-speedcontent-social:
    url: "https://speedcontent.online/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "seotrader-speedcontent-social": {
      "Transport": "http",
      "Url": "https://speedcontent.online/mcp"
    }
  }
}
# add to Vellum
assistant mcp add seotrader-speedcontent-social -t streamable-http -u 'https://speedcontent.online/mcp'
// mcp.json
{
  "mcpServers": {
    "seotrader-speedcontent-social": {
      "type": "http",
      "url": "https://speedcontent.online/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Oct 26 +1
    • Tool “generate_social_post” rewrote its description, which is the text the model reads security
    • Schema quality: 211 → 189 ▲ functional
    • New tool “humanize_text” functional
    • New tool “score_text” functional
  • 4 Oct 26 0
    • Schema quality: 577 → 635 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • “generate_social_post” added an optional parameter “humanize” cosmetic
  • 3 Oct 26 71

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 6 Oct 2026 · Probed https://speedcontent.online/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=speedcontent.online CN=WR3,O=Google Trust Services,C=US 24 Sept 2026 23 Dec 2026 RSA 2048 SHA256-RSA d206154aeda7fdb40a66f2597dd3c8eb
SANs: speedcontent.online
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 1 Sept 1998 28 Jan 2028 RSA 2048 SHA1-RSA 40000000001154b5ac394

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of speedcontent.online. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
online. present 30961 13 Verified
speedcontent.online. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31556926

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://speedcontent.online/mcp Verified 200
http (plaintext) http://speedcontent.online/mcp HTTPS enforced 301 https://speedcontent.online/mcp
MCP tools · 5 exposed · ~912 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_social_job ~55

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.

NameTypeReqDescription
job_idstringyesThe job id returned by generate_social_post.

No output schema declared.

No examples provided.

generate_social_post ~539

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.

NameTypeReqDescription
brand_audiencestring–Who the post should speak to.
brand_descriptionstring–What the business does.
brand_keywordsstring–Comma-separated terms to work in.
brand_namestring–Brand to mention where it reads naturally.
brand_tonestring–Voice guidance, e.g. 'Direct, no jargon'.
detect_aiboolean–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.
emojiboolean–Add emoji to the post. Omit for automatic: off on LinkedIn and YouTube, on elsewhere. Set false for a clean post on any platform.
generate_imageboolean–Generate a matching image for the post. Defaults to false over MCP; pass true to request one. Adds 10 credits per post.
humanizeboolean–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, sin…
languagestring–Output language by name. Defaults to English.
platformstringyesTarget platform. Each has its own style guide and default length.
preservearray–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 ra…
quantityinteger–How many distinct variations to generate. Defaults to 1.
tonestring–Defaults to friendly.
topicstringyesWhat the post should be about.
word_countinteger–Target length per post. Omit to use the platform default (LinkedIn 100, YouTube 150, Facebook/Pinterest 75, Instagram/TikTok 50, X 40).

No output schema declared.

No examples provided.

humanize_text ~179

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.

NameTypeReqDescription
brand_termsarray–Names that must not be altered, e.g. a product name the humanizer would otherwise split into two words.
preservearray–Exact lines that must survive verbatim — a tagline, a call to action, a closing question.
score_afterboolean–Score the rewritten text and return it. Adds 8 credits. Defaults to false.
textstringyesThe text to rewrite. At least 10 characters.

No output schema declared.

No examples provided.

list_social_platforms ~36

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

score_text ~103

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.

NameTypeReqDescription
textstringyesThe text to score. At least 10 characters.

No output schema declared.

No examples provided.

Common questions

What is the SpeedContent Social MCP server?

SpeedContent Social is an MCP server listed in the public MCP registry as io.github.seotrader/speedcontent-social. Generate platform-native social posts that are humanized, AI-detection scored and illustrated. This page covers its hosted endpoint (https://speedcontent.online/mcp).

Is the SpeedContent Social MCP server safe to use?

SpeedContent Social scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the SpeedContent Social MCP server expose?

SpeedContent Social exposes 5 tools: generate_social_post, score_text, humanize_text, check_social_job, list_social_platforms. Their descriptions and schemas cost roughly 912 tokens of context every time the server is loaded.

Does the SpeedContent Social MCP server require authentication?

No. We connected to SpeedContent Social without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SpeedContent Social MCP server still maintained?

SpeedContent Social is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.