tech.distribution/distribution
REMOTE · APP.DISTRIBUTION.TECH · 2 COMPONENTS
Priced X creators, campaigns from a goal, plan changes, mandated payment links, proof and results.
Available components
Last scanned (3 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 946 tokens (~105/item across 9 items; 6 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management58
- Stability check failed: schema churn in the 20 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 55 to 58.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 45 to 48.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 38 to 42.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 32 to 35.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 25 to 28.
- 26 Oct 26 0
- Server version: 1.36.0 → 1.37.0 functional
- 25 Oct 26 +1
- Server version: 1.35.1 → 1.36.0 functional
- 24 Oct 26 0
- Server version: 1.35.0 → 1.35.1 functional
- Server version: 1.34.0 → 1.35.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://app.distribution.tech/api/mcp/guest
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.distribution.tech | CN=YR1,O=Let's Encrypt,C=US | 6 Oct 2026 | 4 Jan 2027 | RSA 2048 | SHA256-RSA | 5f8e5699735740d3efa6b1fd5c4ef101713 |
| SANs: app.distribution.tech | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of app.distribution.tech. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| distribution.tech. | present | 2371 | 13 | Verified |
| app.distribution.tech. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.distribution.tech/api/mcp/guest | Verified | 200 | |
| http (plaintext) | http://app.distribution.tech/api/mcp/guest | HTTPS enforced | 308 | https://app.distribution.tech/api/mcp/guest |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
brain_get Company context ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | One section. Leave out for the whole context. |
No output schema declared.
No examples provided.
feedback_send Send feedback ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | Where it happened: the tool, request id, URL, error code and HTTP status. Other keys are dropped. |
| details | string | yes | What happened (the exact error), how to repeat it (the call), what you expected. Identifiers only. |
| kind | string | yes | bug, gap (a missing capability or an empty or wrong field), idea, praise or other. |
| title | string | yes | One line: what happened or what is missing. |
No output schema declared.
No examples provided.
guest_status Guest access ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
inventory Network coverage ~84
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_quote_guest Estimate a plan ~185
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).
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | post (an original post), quote (a quote repost) or thread. Default post. |
| posts | integer | – | How many posts, 1 to 50. Default 1. |
No output schema declared.
No examples provided.
resolve_audience Resolve an audience ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Who it is for, in your words. |
| geography | string | – | Where the audience is, or worldwide. |
| product | string | – | What is being promoted. |
No output schema declared.
No examples provided.
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.
remote · app.distribution.tech
claude mcp add --transport http tech-distribution-distribution 'https://app.distribution.tech/api/mcp/guest'
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.