# Postlia (remote · postlia.com)

Schedule and publish social posts to 7 networks from AI agents. Postlia API key (Pro) required.

- Trust score: 76/100 (medium)
- Change this week: +9
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

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

## Channel facts

- Endpoint: `https://postlia.com/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.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-08-03.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 133 tokens (~33/item across 4 items; 4 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**: 73/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 20% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

```json
{
  "mcpServers": {
    "com-postlia-postlia": {
      "type": "http",
      "url": "https://postlia.com/api/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-08-02 (score 76, +1)

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

### 2026-07-31 (score 75, +6)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, +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-07-27 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (4)

### `list_accounts` (~19 tokens)

List the connected social accounts on this Postlia workspace.

### `list_scheduled_posts` (~15 tokens)

List upcoming scheduled posts.

### `create_post` (~77 tokens)

Create a text post. Provide scheduledAt (ISO datetime) to schedule, queue=true for the next open queue slot, or neither to post within ~5 minutes.

Input parameters:

- `content` (string, required)
- `platforms` (array, required): e.g. linkedin, bluesky
- `queue` (boolean)
- `scheduledAt` (string)

### `cancel_post` (~22 tokens)

Cancel a scheduled post by id.

Input parameters:

- `id` (string, required)

## Diagnostics

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

## Score history

- 2026-08-03: 76
- 2026-08-02: 76
- 2026-08-01: 75
- 2026-07-31: 75
- 2026-07-30: 69
- 2026-07-29: 68
- 2026-07-28: 67
- 2026-07-27: 67
- 2026-07-26: 66

## Links

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