what2post
REMOTE · WHAT2POSTAPP.COM · SCANNED SEP 20
Read-only access to your what2post LinkedIn data: posts, profile stats, follower growth and goals.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the what2post MCP server?
what2post is a hosted endpoint at https://what2postapp.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.
remote · what2postapp.com
claude mcp add --transport http thedesti-what2post 'https://what2postapp.com/mcp'
{
"mcpServers": {
"thedesti-what2post": {
"url": "https://what2postapp.com/mcp"
}
}
} {
"servers": {
"thedesti-what2post": {
"type": "http",
"url": "https://what2postapp.com/mcp"
}
}
} [mcp_servers.thedesti-what2post] url = "https://what2postapp.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"thedesti-what2post": {
"type": "remote",
"url": "https://what2postapp.com/mcp",
"enabled": true
}
}
} openclaw mcp add thedesti-what2post --url 'https://what2postapp.com/mcp' --transport streamable-http
mcp_servers:
thedesti-what2post:
url: "https://what2postapp.com/mcp" {
"McpServers": {
"thedesti-what2post": {
"Transport": "http",
"Url": "https://what2postapp.com/mcp"
}
}
} assistant mcp add thedesti-what2post -t streamable-http -u 'https://what2postapp.com/mcp'
{
"mcpServers": {
"thedesti-what2post": {
"type": "http",
"url": "https://what2postapp.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 30 Aug 26 −52
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 20 Sept 2026 · Probed https://what2postapp.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=what2postapp.com | CN=YR2,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | RSA 2048 | SHA256-RSA | 51e46af9f74433c2460a202c95bc5703f09 |
| SANs: what2postapp.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 insecure
Validation of what2postapp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| what2postapp.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 | 503 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://what2postapp.com/mcp | HTTP error | 503 | |
| http (plaintext) | http://what2postapp.com/mcp | HTTPS enforced | 308 | https://what2postapp.com/mcp |
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 →
get_my_goals List my growth goals ~42
List your growth goals with progress. Optionally filter by status (e.g. active, completed).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| status | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_my_growth Get my follower growth ~50
Get follower-growth statistics over the last days_back days for one LinkedIn profile. Defaults to your primary profile when profile_id is omitted.
| Name | Type | Req | Description |
|---|---|---|---|
| days_back | integer | – | – |
| profile_id | – | – | – |
No output schema declared.
No examples provided.
get_my_profile_stats Get my profile stats ~46
Get engagement statistics and recent posts for one of your LinkedIn profiles. Defaults to your primary profile when profile_id is omitted. Requires an active subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| profile_id | – | – | – |
No output schema declared.
No examples provided.
list_my_posts List my LinkedIn posts ~52
List your synced LinkedIn posts, newest first. Scoped to one profile when profile_id is given, otherwise all your profiles. Requires an active subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| profile_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
What is the what2post MCP server?
what2post is an MCP server listed in the public MCP registry as io.github.theDestI/what2post. Read-only access to your what2post LinkedIn data: posts, profile stats, follower growth and goals. This page covers its hosted endpoint (https://what2postapp.com/mcp).
Is the what2post MCP server safe to use?
what2post scores 25 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 what2post MCP server expose?
what2post exposes 4 tools: list_my_posts, get_my_profile_stats, get_my_growth, get_my_goals. Their descriptions and schemas cost roughly 190 tokens of context every time the server is loaded.
Does the what2post MCP server require authentication?
No. We connected to what2post without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the what2post MCP server still maintained?
what2post is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.