Skip to content
Surgemesh logo

Surgemesh MCP server

Which MCP servers are Surgemesh's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to Surgemesh

Whose server it is
  • Registry namecom.surgemesh/surgemeshverified in the MCP registry

The registry name sits under surgemesh.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-29
  • Stateanswerschecked 2026-10-29
  • Tools26
  • Server calls itselfsurgemesh
  • Server version1.4.0
  • Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 569 ms.

Should an agent connect itConnect it, with care
  • Its tools do every use case we checked: Queue posts to Facebook pages and Instagram accounts; Check and cancel queued posts for several brands; Get a price quote before scheduling a post.

Once connected

  • For "Check and cancel queued posts for several brands", the likely first call is list_brands.
  • For "Get a price quote before scheduling a post", the likely first call is get_quote.
  • add_channel, create_post, cancel_post, create_checkout_link, update_account_settings change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 21 of 28 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 7, the first on 2026-10-29
  • INITE MCP score74 of 100answers 100 · does the job 100 · definitions 71 · context 96 · connects 100 · lowered by the warning signs below
  • What an agent can do with it3 of 3 use cases
  • Answered100% of days7 of 7 daily checks
  • Median first answer451 ms
  • Space in an agent's context≈ 3,489 tokensthe definitions of all its tools (28), which an agent carries on every turn
  • Tool definitionsC · 71 of 100
  • Typed results0 of 28 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 21 of 28
  • Not saying whether it only reads or can destroy: 28 of 28

What an agent can do with it

  • can do · Queue posts to Facebook pages and Instagram accounts
  • can do · Check and cancel queued posts for several brands
  • can do · Get a price quote before scheduling a post

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: add_channel, create_post, cancel_post, create_checkout_link, update_account_settings

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers26 tools · read 2026-10-29
  • get_pricing

    Surgemesh prices: base per delivery, a hard ceiling (never more than $0.06 per delivery), time-of-day pricing (quieter times cost less, busier times cost more), credit packs. No auth needed.

  • get_quote

    Exact price quote (locks at post acceptance; guard with max_price_usd) for N deliveries at scheduled_at (ISO 8601 UTC, e.g. 2026-10-29T15:00:00Z), or for a network mix (networks, e.g. {"bluesky": 1, "facebook": 2}; adds by_network), with…

  • list_channels

    Channels this key can post to (connected social accounts and sandbox test channels). Disconnected channels are hidden unless include_disconnected is true.

  • add_channel

    Add a channel directly (admin key). network "sandbox": a built-in test channel, no credentials, never publishes; it enforces the real limits of the network in simulates (bluesky, facebook or instagram; default bluesky). network "bluesky"…

  • list_brands

    Brands in this account.

  • create_post

    Schedule a post to one or more channels. idempotency_key is required; retries with the same key never double-post or double-charge. Optional max_price_usd refuses a price above your cap. Preview: posts are validated and priced in the…

  • list_posts

    Recent posts for a brand: status (pending, accepted, rejected, cancelled), cancelled, sandbox, price_usd (quoted), charged_usd, per-channel delivery state.

  • cancel_post

    Cancel a queued post. Undelivered deliveries are refunded to credit.

  • get_topup_link

    Coming soon (payments are not enabled yet). Payment link to buy a credit pack (pack_5 $5, pack_20 $20, pack_100 $100; each pack buys exactly its price in credit). Rails: mpp_card (card via Stripe Shared Payment Token), mpp_stablecoin…

  • create_checkout_link

    Card checkout for a human (coming soon): returns a Stripe-hosted checkout_url for a credit pack (pack_5 $5, pack_20 $20, pack_100 $100; each pack buys exactly its price in credit). Give the link to the person paying; credits arrive only…

  • get_referral_code

    Your referral code, share link and stats (referred signups, qualified, credits earned and pending). Referral rewards are Surgemesh credits only, never cash, and are coming soon; codes can be shared now. Verified owners only.

  • get_usage

    Account: plan, verification, credit, sandbox allowance (monthly_allowance, posts_used_this_month, posts_remaining_this_month, resets_at) and settings.

  • update_account_settings

    Account settings (admin key). trend_opt_out: true opts this account out of contributing to any aggregated trend statistics Surgemesh may create in future (see Terms); none exist today. get_usage shows the current setting.

  • get_onboarding

    Onboarding status: verification state, remaining steps and the exact next call. Start here after signup.

  • start_email_verification

    Email a 6-digit code to the account email (expires in 10 minutes, 5 attempts). Then call confirm_email_verification with the code.

  • confirm_email_verification

    Submit the 6-digit code from the verification email.

  • start_dns_verification

    Get a TXT record to publish on the account email domain (or a parent domain). Then call check_dns_verification.

  • check_dns_verification

    Check whether the TXT record is visible; verifies the account when it is.

  • request_owner_approval

    Email the account owner a one-tap Approve link (24 h, single use). Poll get_verification until verified or denied.

  • get_verification

    Status of one verification (pending, verified, expired, failed, denied).

  • rotate_my_key

    Rotate the calling key: returns a new key (shown once) with the same scopes; the old key keeps working for grace_seconds (default 3600, 0 = revoke now).

  • list_networks

    Every supported network: status (available, connect_pending_review, connect_pending_setup = coming soon), how to connect it, and the limits enforced on every post (text, hashtags, media count, types, sizes), plus the built-in sandbox test…

  • connect_channel

    Start a one-tap connect for a brand on an OAuth or app-password network (networks marked coming soon in list_networks are refused). Returns connect_url: give it to the account owner to open once. Then poll get_connect_status.

  • get_connect_status

    Status of a connect session: pending, connected (with channel_id), failed or expired.

  • disconnect_channel

    Disconnect a channel: erases its stored credentials and revokes the provider token where the network supports it.

  • get_analytics

    Posts, deliveries, published, failed and spend over time (UTC), with a per-brand breakdown.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "surgemesh": {
      "type": "http",
      "url": "https://api.surgemesh.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http surgemesh https://api.surgemesh.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.surgemesh.com/mcp as a custom connector in the settings.

OpenAPI spec

31 paths, read 2026-10-29. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.