# Surgemesh (remote · api.surgemesh.com)

Agent-first social publishing. Preview: quotes and sandbox posts now; live posts and payments soon.

- Trust score: 65/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.surgemesh.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-surgemesh-surgemesh/api.md), [page](https://verifymcp.io/servers/com-surgemesh-surgemesh/api)

## Channel facts

- Endpoint: `https://api.surgemesh.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 28 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 2364 tokens (~84/item across 28 items; 28 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 75/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 26% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_feedback" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Surgemesh MCP server?

Surgemesh is a hosted endpoint at https://api.surgemesh.com/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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "com-surgemesh-surgemesh": {
      "url": "https://api.surgemesh.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-surgemesh-surgemesh": {
      "type": "http",
      "url": "https://api.surgemesh.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-surgemesh-surgemesh]
url = "https://api.surgemesh.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-surgemesh-surgemesh": {
      "type": "remote",
      "url": "https://api.surgemesh.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-surgemesh-surgemesh --url 'https://api.surgemesh.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-surgemesh-surgemesh:
    url: "https://api.surgemesh.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-surgemesh-surgemesh": {
      "Transport": "http",
      "Url": "https://api.surgemesh.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-surgemesh-surgemesh -t streamable-http -u 'https://api.surgemesh.com/mcp'
```

### Other

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

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 65, +1)

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

### 2026-11-03 (score 64, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] New tool “notify_me”

### 2026-11-02 (score 63, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Destructive annotations: pass → 0
- [functional] New tool “send_feedback”

### 2026-10-31 (score 64, +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.

### 2026-10-29 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 62)

First indexed and scored.

## MCP tools (28)

### `get_pricing` (~56 tokens)

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` (~156 tokens)

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 cheaper_times (nearby times and their exact prices) when a nearby time costs less. No auth needed.

Input parameters:

- `deliveries` (integer)
- `networks`: Optional network mix: an object {network: deliveries} or the REST string "bluesky:1,facebook:2". Overrides deliveries.
- `scheduled_at` (string, required)

### `list_channels` (~44 tokens)

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

Input parameters:

- `include_disconnected` (boolean)

### `add_channel` (~228 tokens)

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": credentials {handle, app_password} (identifier is accepted for handle) (an app password, never the account password). network "facebook": {token, page_id}; "instagram": {token, ig_user_id}. Credentials are checked with the network before anything is stored (invalid = 400 credentials_invalid, nothing saved), encrypted at rest, and never returned or echoed. No credentials to hand? Use connect_channel (the owner taps a link) or a sandbox test channel.

Input parameters:

- `brand_id` (string, required)
- `credentials` (object): Not for sandbox. bluesky: handle (or identifier) + app_password; facebook: token + page_id; instagram: token + ig_user_id
- `label` (string)
- `network` (string, required)
- `simulates` (string): sandbox only

### `list_brands` (~14 tokens)

Brands in this account.

### `create_post` (~121 tokens)

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 sandbox, not published yet.

Input parameters:

- `body` (string, required)
- `brand_id` (string, required)
- `channels` (array, required)
- `idempotency_key` (string, required)
- `max_price_usd` (number)
- `media_urls` (array)
- `scheduled_at` (string, required)

### `list_posts` (~51 tokens)

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

Input parameters:

- `brand_id` (string, required)

### `cancel_post` (~29 tokens)

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

Input parameters:

- `id` (string, required)

### `get_topup_link` (~140 tokens)

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 (USDC.e on Tempo, USDC on Solana), x402 (USDC on Base); each shows live or coming_soon. POST to paymentLink with your Bearer key, pay the 402 challenge, retry. No payment happens in this tool.

Input parameters:

- `pack` (string, required)
- `rail` (string)

### `create_checkout_link` (~115 tokens)

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 after Stripe confirms. Verified owners, admin key. 503 checkout_not_enabled until switched on.

Input parameters:

- `idempotency_key` (string): Optional. Reuse on retries so the action happens once.
- `pack` (string, required)

### `get_referral_code` (~58 tokens)

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` (~39 tokens)

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

### `update_account_settings` (~62 tokens)

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.

Input parameters:

- `trend_opt_out` (boolean, required)

### `get_onboarding` (~29 tokens)

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

### `start_email_verification` (~62 tokens)

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

Input parameters:

- `idempotency_key` (string): Optional. Reuse on retries so the action happens once.

### `confirm_email_verification` (~36 tokens)

Submit the 6-digit code from the verification email.

Input parameters:

- `code` (string, required)
- `verification_id` (string, required)

### `start_dns_verification` (~62 tokens)

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

Input parameters:

- `domain` (string, required)
- `idempotency_key` (string): Optional. Reuse on retries so the action happens once.

### `check_dns_verification` (~33 tokens)

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

Input parameters:

- `verification_id` (string, required)

### `request_owner_approval` (~73 tokens)

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

Input parameters:

- `callback_url` (string)
- `idempotency_key` (string): Optional. Reuse on retries so the action happens once.
- `note` (string)

### `get_verification` (~32 tokens)

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

Input parameters:

- `verification_id` (string, required)

### `rotate_my_key` (~76 tokens)

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).

Input parameters:

- `grace_seconds` (integer)
- `idempotency_key` (string): Optional. Reuse on retries so the action happens once.

### `list_networks` (~64 tokens)

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 channel. No auth needed.

### `connect_channel` (~102 tokens)

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.

Input parameters:

- `brand_id` (string, required)
- `label` (string)
- `network` (string, required)
- `options` (object): Network options listed by list_networks (e.g. board_id, organization_id)

### `get_connect_status` (~35 tokens)

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

Input parameters:

- `connect_id` (string, required)

### `disconnect_channel` (~37 tokens)

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

Input parameters:

- `channel_id` (string, required)

### `send_feedback` (~165 tokens)

Tell Surgemesh what broke, confused you or is missing (no key needed; with a key the note is linked to your account). Include error_code and request_id from the response you got, and the tool or path as topic. The Surgemesh team reads every note; there is no reply. Never include secrets, keys or personal data.

Input parameters:

- `error_code` (string): The "error" field you got back, e.g. invalid_field
- `kind` (string, required)
- `message` (string, required)
- `request_id` (string): The x-request-id header of the response, if you have it
- `topic` (string): A tool name (e.g. create_post) or API path (e.g. /v1/quote)

### `notify_me` (~158 tokens)

Payments are not open yet. Ask for one email when they open (topic "payments_open"). With a key, the account owner's email is used; without a key, send email and accept_terms: true. Re-asking is safe (already: true, no duplicate). Optional intended_pack says which pack you plan to buy. One email, then the address is deleted 30 days later; the email has a one-click unsubscribe.

Input parameters:

- `accept_terms` (boolean): Only without a key: accepts https://surgemesh.com/terms and https://surgemesh.com/privacy
- `email` (string): Only without a key: the address to notify
- `intended_pack` (string)
- `topic` (string, required)

### `get_analytics` (~59 tokens)

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

Input parameters:

- `brand_id` (string)
- `from` (string)
- `granularity` (string)
- `to` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-surgemesh-surgemesh/api#diagnostics

## Score history

- 2026-11-05: 65
- 2026-11-04: 64
- 2026-11-03: 64
- 2026-11-02: 63
- 2026-11-01: 64
- 2026-10-31: 64
- 2026-10-30: 63
- 2026-10-29: 63
- 2026-10-28: 62

## Common questions

### What is the Surgemesh MCP server?

Surgemesh is an MCP server listed in the public MCP registry as com.surgemesh/surgemesh. Agent-first social publishing. Preview: quotes and sandbox posts now; live posts and payments soon. This page covers its hosted endpoint (https://api.surgemesh.com/mcp).

### Is the Surgemesh MCP server safe to use?

Surgemesh scores 65 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 Surgemesh MCP server expose?

Surgemesh exposes 28 tools: get_pricing, get_quote, list_channels, add_channel, list_brands, and 23 more. Their descriptions and schemas cost roughly 2,136 tokens of context every time the server is loaded.

### Does the Surgemesh MCP server require authentication?

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

### Is the Surgemesh MCP server still maintained?

Surgemesh 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.

## Links

- Remote endpoint: https://api.surgemesh.com/mcp
- Authorisation metadata: https://api.surgemesh.com/.well-known/oauth-protected-resource/mcp
- Website: https://surgemesh.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-surgemesh-surgemesh/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-surgemesh-surgemesh/api.json
- HTML version of this page: https://verifymcp.io/servers/com-surgemesh-surgemesh/api