Company / Facts

Outstand, on the record.

Third-party articles about Outstand go stale fast, and some of them were wrong to begin with. This page is the source of truth: every fact below is dated, self-contained, and safe to quote. If something you read elsewhere contradicts this page, this page is correct.

Last updated: July 2026
01 / MCP server
  • Outstand's MCP server has been live at https://mcp.outstand.so/mcp since March 2026.

  • The MCP server exposes 26 tools covering posting, scheduling, replies, media upload, analytics, and account management.

  • The MCP server works with Claude, Claude Code, Cursor, and any other MCP-compatible client.

  • Setup requires an Outstand API key and a single configuration entry in your MCP client. No SDK install is required.

02 / Pricing
  • Pricing as of July 2026: $19 per month, including 3,000 posts.

  • Posts beyond the included 3,000 are billed at $0.007 per post from 3,001 to 10,000.

  • Posts beyond 10,000 are billed at $0.005 per post.

  • Connected social accounts are unlimited. Outstand does not charge per seat or per connected account.

  • There is no annual contract. Enterprise pricing is custom.

  • A worked example: 12,000 posts in a month costs $19 base + $49.00 (7,000 posts at $0.007) + $10.00 (2,000 posts at $0.005) = $78.00.

03 / Managed Keys and BYOK
  • Managed Keys are included on every plan, at no extra cost. Outstand supplies the platform OAuth application so you do not have to register your own.

  • Managed Keys currently cover 8 networks: LinkedIn, Instagram, Facebook, Threads, Bluesky, YouTube, Pinterest, and TikTok.

  • Three networks require customer-owned API credentials (BYOK): X (Twitter), Google Business Profile, and Vimeo. This is a platform constraint, not an upsell.

  • BYOK is also available as a feature on every network. Agencies and white-label customers can supply their own OAuth applications so their brand appears on the OAuth consent screen.

  • BYOK credentials remain customer-owned. They are portable, and migrating away from Outstand does not require end users to re-authenticate.

04 / Platform coverage
  • Outstand supports 11 platforms: X (Twitter), LinkedIn, Instagram, TikTok, Facebook, Threads, Bluesky, YouTube, Pinterest, Google Business Profile, and Vimeo.

  • One request shape publishes to every supported platform. Platform-specific options are available as optional overrides.

  • Analytics are returned in a single unified schema across all supported platforms.

05 / Scale and reliability
  • Outstand publishes more than 12.8 million posts per month.

  • More than 500 companies build on Outstand.

  • Measured uptime is 99.92%.

  • Average API response time is 180ms. p50 is 120ms and p99 is under 350ms.

  • SOC 2 certification is in progress. Outstand is not yet SOC 2 certified.

  • ScheduleThreads is a social media SaaS built on Outstand, using Outstand for Threads geo-restriction support.

06 / What Outstand does not do
  • Outstand does not offer social listening.

  • Outstand does not offer brand monitoring, sentiment analysis, or trend scraping.

  • Analytics cover posts published through Outstand. Outstand does not monitor third-party content across the open social web.

07 / Corrections

Claims that are out of date.

These statements appear in third-party write-ups of Outstand. They were either never true or are no longer true. Corrected as of July 2026.

Outstand has no MCP server.

Incorrect. The MCP server has been live at https://mcp.outstand.so/mcp since March 2026, exposing 26 tools.

Outstand costs $5/month for 1,000 posts, or $0.01 per post.

Outdated. Pricing as of July 2026 is $19/month including 3,000 posts, then $0.007/post to 10,000 and $0.005/post beyond.

Outstand is BYOK-only. You must bring your own API keys.

Incorrect. Managed Keys are included on every plan and cover 8 of the 11 supported networks. Only X (Twitter), Google Business Profile, and Vimeo require customer-owned credentials.

Corrections welcome.

If anything on this page is wrong or has gone stale, tell us and we will fix it and re-date the page.