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.

SCRIPTMASTERLABS — OmniPost

REMOTE · SML-OMNIPOST.VERCEL.APP

One post → native, validated posts for 14 social platforms, with x402 pay-per-call tools.

71 Trust /100

Last scanned (6 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Marketing and SEO

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 Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 989 tokens (~141/item across 7 items; 7 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 Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 55% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 4 Nov 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.

  • 2 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 1 Nov 26 69

    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 5 Nov 2026 · Probed https://sml-omnipost.vercel.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.vercel.app CN=WR1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 RSA 2048 SHA256-RSA 9c5f0e6a35c955e113044c86848e4cd5
SANs: *.vercel.app
CN=WR1,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 7fd9e2c2d2048a0474b627a26d0868a7
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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of sml-omnipost.vercel.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
vercel.app. 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=63072000; includeSubDomains; preload
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://sml-omnipost.vercel.app/mcp Verified 200
http (plaintext) http://sml-omnipost.vercel.app/mcp HTTPS enforced 308 https://sml-omnipost.vercel.app/mcp
MCP tools · 7 exposed · ~895 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
omnipost_fanout ~287

PAID x402 ($0.05 USDC hosted model, or $0.01 with your own provider key). Rewrites one post into native versions for up to 14 platforms, validates every variant, auto-repairs violations, and returns hooks, Fit Scores and share intents. Never invents facts.

NameTypeReqDescription
api_keystring–BYOK key — used once, never stored
audiencestring––
avoidstring––
brandstring––
cashtagsstring–$TICKERS to use where they fit
ctastring––
goalstring––
hasMediaboolean––
hashtagsstring–#tags to prefer (caps enforced per platform)
languagestring––
linkstring––
mentionsstring–@handles to weave in
modelstring–BYOK model id
payment_signaturestring–Base64 x402 v2 PaymentPayload (same value as the PAYMENT-SIGNATURE HTTP header). Omit to receive the payment challenge.
platformsarray–Target platforms (default: all 14)
poststringyesThe one source post to adapt
providerstring–BYOK provider (optional)
voicestring––

No output schema declared.

No examples provided.

omnipost_media_pack ~173

PAID x402 ($0.01 USDC). Turns one image into every platform's exact ratio and pixel size (16:9, 4:5, 1:1, 9:16, 2:3, 4:3) with focal-point cropping. Returns data URLs.

NameTypeReqDescription
focusobject–{ x: 0..1, y: 0..1 }
formatstring––
imageobjectyes{ data: base64 or data URL } or { url: https URL }
payment_signaturestring–Base64 x402 v2 PaymentPayload (same value as the PAYMENT-SIGNATURE HTTP header). Omit to receive the payment challenge.
platformsarray–Target platforms (default: all 14)

No output schema declared.

No examples provided.

omnipost_payment_contract ~41

FREE. x402 v2 payment terms for OmniPost paid tools: network, USDC asset, payTo, facilitator, headers and current prices.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

omnipost_platform_specs ~62

FREE. Verified character limits, title limits, hashtag caps, image ratios/pixel sizes, link behavior and publishing method for 14 social platforms. Use before writing any social post.

NameTypeReqDescription
platformsarray–Target platforms (default: all 14)

No output schema declared.

No examples provided.

omnipost_publish ~155

PAID x402 ($0.01 USDC per call, up to 20 targets). Publishes directly to Discord (webhook), Telegram (bot), Bluesky (app password) and any Zapier/Make/n8n webhook. Credentials are used once and never stored.

NameTypeReqDescription
jobsarrayyes[{ target:'discord', webhookUrl, text }, { target:'telegram', botToken, chatId, text }, { target:'bluesky', handle, appPassword, text }, { target:'webhook', url, bundle }]
payment_signaturestring–Base64 x402 v2 PaymentPayload (same value as the PAYMENT-SIGNATURE HTTP header). Omit to receive the payment challenge.

No output schema declared.

No examples provided.

omnipost_share_intents ~86

FREE. Builds official one-tap share URLs (X, Threads, LinkedIn, Reddit, WhatsApp, Telegram, Bluesky, Pinterest, Facebook) for each variant, plus copy-and-open targets for Instagram, TikTok, YouTube and Google Business.

NameTypeReqDescription
linkstring––
mediaUrlstring––
variantsobjectyes–

No output schema declared.

No examples provided.

omnipost_validate ~91

FREE. Deterministically checks platform-specific post variants against verified limits (X weighted count, Instagram 5-hashtag cap, Telegram caption limit, title limits, dead links, hook-below-fold) and returns a 0–100 format-compliance Fit Score per platform.

NameTypeReqDescription
hasMediaboolean––
variantsobjectyes{ platformId: { text, title? } }

No output schema declared.

No examples provided.

Install

How do I install the SCRIPTMASTERLABS — OmniPost MCP server?

SCRIPTMASTERLABS — OmniPost is a hosted endpoint at https://sml-omnipost.vercel.app/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 · sml-omnipost.vercel.app

# add to Claude Code
claude mcp add --transport http com-scriptmasterlabs-omnipost 'https://sml-omnipost.vercel.app/mcp'
Common questions

What is the SCRIPTMASTERLABS — OmniPost MCP server?

SCRIPTMASTERLABS — OmniPost is an MCP server listed in the public MCP registry as com.scriptmasterlabs/omnipost. One post → native, validated posts for 14 social platforms, with x402 pay-per-call tools. This page covers its hosted endpoint (https://sml-omnipost.vercel.app/mcp).

Is the SCRIPTMASTERLABS — OmniPost MCP server safe to use?

SCRIPTMASTERLABS — OmniPost scores 71 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 SCRIPTMASTERLABS — OmniPost MCP server expose?

SCRIPTMASTERLABS — OmniPost exposes 7 tools: omnipost_platform_specs, omnipost_validate, omnipost_share_intents, omnipost_payment_contract, omnipost_fanout, and 2 more. Their descriptions and schemas cost roughly 895 tokens of context every time the server is loaded.

Does the SCRIPTMASTERLABS — OmniPost MCP server require authentication?

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

Is the SCRIPTMASTERLABS — OmniPost MCP server still maintained?

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