# tech.distribution/distribution (remote · app.distribution.tech)

Priced X creators, campaigns from a goal, plan changes, mandated payment links, proof and results.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `app.distribution.tech`: 39/100, [markdown](https://verifymcp.io/servers/tech-distribution-distribution/api-mcp.md), [page](https://verifymcp.io/servers/tech-distribution-distribution/api-mcp)
- remote · `app.distribution.tech`: 84/100 (this document), [markdown](https://verifymcp.io/servers/tech-distribution-distribution/api-mcp-guest.md), [page](https://verifymcp.io/servers/tech-distribution-distribution/api-mcp-guest)

## Channel facts

- Endpoint: `https://app.distribution.tech/api/mcp/guest`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.37.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**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 946 tokens (~105/item across 9 items; 6 tools + 3 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 58/100
  - Stability check failed: schema churn in the 20 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 0 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the tech.distribution/distribution MCP server?

tech.distribution/distribution is a hosted endpoint at https://app.distribution.tech/api/mcp/guest, 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 tech-distribution-distribution 'https://app.distribution.tech/api/mcp/guest'
```

### Cursor

```json
{
  "mcpServers": {
    "tech-distribution-distribution": {
      "url": "https://app.distribution.tech/api/mcp/guest"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-distribution-distribution": {
      "type": "http",
      "url": "https://app.distribution.tech/api/mcp/guest"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-distribution-distribution]
url = "https://app.distribution.tech/api/mcp/guest"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-distribution-distribution": {
      "type": "remote",
      "url": "https://app.distribution.tech/api/mcp/guest",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-distribution-distribution --url 'https://app.distribution.tech/api/mcp/guest' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-distribution-distribution:
    url: "https://app.distribution.tech/api/mcp/guest"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-distribution-distribution": {
      "Transport": "http",
      "Url": "https://app.distribution.tech/api/mcp/guest"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-distribution-distribution -t streamable-http -u 'https://app.distribution.tech/api/mcp/guest'
```

### Other

```json
{
  "mcpServers": {
    "tech-distribution-distribution": {
      "type": "http",
      "url": "https://app.distribution.tech/api/mcp/guest"
    }
  }
}
```

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 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 55 to 58.

### 2026-11-02 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 45 to 48.

### 2026-10-31 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 38 to 42.

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

No change was recorded against any check on this day. Stability & Change Management went from 32 to 35.

### 2026-10-27 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 25 to 28.

### 2026-10-26 (score 79, 0)

- [functional] Server version: 1.36.0 → 1.37.0

### 2026-10-25 (score 79, +1)

- [functional] Server version: 1.35.1 → 1.36.0

### 2026-10-24 (score 78, 0)

- [functional] Server version: 1.35.0 → 1.35.1
- [functional] Server version: 1.34.0 → 1.35.0

## MCP tools (6)

### `inventory` (~84 tokens)

Network coverage

No account needed. As a guest (no audience on file): how much of the network is on sale today, per channel: approved creators, posts on sale at a current price, and whether coverage is strong or thin. Counts only, never a creator's identity. resolve_audience narrows it to an audience you describe; with an account it is measured against your own audience.

### `resolve_audience` (~117 tokens)

Resolve an audience

No account needed for a profile you describe (product, audience, geography; at least a product or an audience): the audience segments it matches and the coverage per channel, the same check a campaign gets when it starts. Counts only, never a creator's identity. The fit for a campaign of yours (intent_id) needs an account.

Input parameters:

- `audience` (string): Who it is for, in your words.
- `geography` (string): Where the audience is, or worldwide.
- `product` (string): What is being promoted.

### `brain_get` (~92 tokens)

Company context

A guest has no saved company context, so as a guest this answers the empty context (version 0, nothing confirmed) with claim, where to sign in and confirm your company in the workspace. With an account: your company context as confirmed (name, summary, audience), its version and the version history. Optionally one section.

Input parameters:

- `section` (string): One section. Leave out for the whole context.

### `feedback_send` (~162 tokens)

Send feedback

Needs an account. A signed-in agent tells the distribution team about a problem or an idea with any API key. As a guest this sends nothing: it answers with claim, where to sign in and create a key, so the report can be sent from an account.

Input parameters:

- `context` (object): Where it happened: the tool, request id, URL, error code and HTTP status. Other keys are dropped.
- `details` (string, required): What happened (the exact error), how to repeat it (the call), what you expected. Identifiers only.
- `kind` (string, required): bug, gap (a missing capability or an empty or wrong field), idea, praise or other.
- `title` (string, required): One line: what happened or what is missing.

### `plan_quote_guest` (~185 tokens)

Estimate a plan

No account needed. The all-in price range a brand pays per post in one format (post, quote or thread) across every creator on sale now, and that range times the number of posts you name (1 to 50), with how many creators sell that format and when the numbers were read. A guest gets 3 quotes in any 7 days from one address (quotes_left says how many remain); the next is refused with rate_limited (reason guest_quote_limit, retry_after and resets_at). A range, not a plan: a plan names creators and dates and needs an account (claim says where to sign in and create a key).

Input parameters:

- `format` (string): post (an original post), quote (a quote repost) or thread. Default post.
- `posts` (integer): How many posts, 1 to 50. Default 1.

### `guest_status` (~49 tokens)

Guest access

No account needed. What this connection can do without a key: which tools answer now, which need an account, the guest limits, and claim, where to sign in and create a key in Developers.

## Diagnostics

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

## Score history

- 2026-11-05: 84
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 83
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 81
- 2026-10-29: 81
- 2026-10-28: 80
- 2026-10-27: 80
- 2026-10-26: 79
- 2026-10-25: 79
- 2026-10-24: 78
- 2026-10-23: 78
- 2026-10-22: 77
- 2026-10-21: 77
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 80
- 2026-10-17: 79
- 2026-10-16: 79

## Common questions

### What is the tech.distribution/distribution MCP server?

tech.distribution/distribution is an MCP server listed in the public MCP registry as tech.distribution/distribution. Priced X creators, campaigns from a goal, plan changes, mandated payment links, proof and results. This page covers its hosted endpoint (https://app.distribution.tech/api/mcp/guest).

### Is the tech.distribution/distribution MCP server safe to use?

tech.distribution/distribution scores 84 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 tech.distribution/distribution MCP server expose?

tech.distribution/distribution exposes 6 tools: inventory, resolve_audience, brain_get, feedback_send, plan_quote_guest, guest_status. Their descriptions and schemas cost roughly 689 tokens of context every time the server is loaded.

### Does the tech.distribution/distribution MCP server require authentication?

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

### Is the tech.distribution/distribution MCP server still maintained?

tech.distribution/distribution 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://app.distribution.tech/api/mcp/guest
- Website: https://distribution.tech/
- Changelog RSS feed: https://verifymcp.io/servers/tech-distribution-distribution/api-mcp-guest.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-distribution-distribution/api-mcp-guest.json
- HTML version of this page: https://verifymcp.io/servers/tech-distribution-distribution/api-mcp-guest