BetterPost
REMOTE · BETTERPOST.AI
Finds timely sources across news, social, and the web and writes posts worth publishing.
Available components
Last scanned (19 hours ago)
Scores higher than 98% 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 Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2239 tokens (~97/item across 23 items; 23 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 29% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 24 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 28 Sept 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
- 25 Sept 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
- 26 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 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
- 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
- 27 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 5 Nov 2026 · Probed https://betterpost.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=betterpost.ai | CN=WE1,O=Google Trust Services,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 14c51c990a7d3b5e0e0177c9b8d663d6 |
| SANs: betterpost.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of betterpost.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814, 3799 | 8, 8 | Verified |
| betterpost.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://betterpost.ai/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://betterpost.ai/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; script-src 'self' 'nonce-KaUIMW5NzL16Ba4Pwci/ag==' https://us-assets.i.posthog.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://assets.betterpost.ai; font-src 'self'; connect-src 'self' https://us.i.posthog.com https://us-assets.i.posthog.com; worker-src 'self' blob: |
Protected resource metadata
| Document | https://betterpost.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://betterpost.ai/mcp |
| Authorisation server | https://measured-mystery-47.authkit.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://betterpost.ai/mcp | Verified | 200 | |
| http (plaintext) | http://betterpost.ai/mcp | HTTPS enforced | 301 | https://betterpost.ai/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 →
betterpost_add_source Add source ~298
Adds a source to a project and fetches it immediately (bounded by a few seconds), returning `storiesAdded` so the next generate_content can use it; if it is still fetching it returns `fetched:false` with a note. Doubles as manual source import: paste any URL (RSS/Atom feed, article, or a page, profile, or post on a supported platform) and leave `type` as autodetect, or create a recurring keyword search by setting `value` to the search terms and `type` to a search kind (see `type`).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | – |
| projectId | string | yes | – |
| type | string | – | Source kind (one of the enum values; defaults to 'autodetect'). 'autodetect' infers the kind from `value` (a URL): RSS/Atom feeds, web pages, news, Reddit subreddits, X and Bluesky posts/users, Linke… |
| value | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| fetched | boolean | yes | – |
| note | string | – | – |
| source | object | yes | – |
| storiesAdded | integer | yes | – |
No examples provided.
betterpost_add_story Add story ~66
Manually imports a story you read about from its URL (pinned relevance, flagged is_manual) so generation can draw on it.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
| summary | string | – | – |
| title | string | – | – |
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| storyId | string | yes | – |
No examples provided.
betterpost_create_project Create project ~97
Create a content project. Slow, one-shot: infers config (criteria, industry, tone), discovers sources, and gathers/ranks an initial set of timely stories. Best called after the inferred audience, description, and tone have been confirmed with the user, since the config shapes everything downstream.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | yes | – |
| description | string | – | – |
| title | string | yes | – |
| tone | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | yes | – |
| hasXSource | boolean | yes | – |
| industry | string | yes | – |
| projectId | string | yes | – |
| reason | string | – | – |
| storiesGoal | integer | yes | – |
| storiesGot | integer | yes | – |
| tone | string | yes | – |
| warming | boolean | yes | – |
No examples provided.
betterpost_delete_content Delete content ~28
Delete a piece of content and its hosted images.
| Name | Type | Req | Description |
|---|---|---|---|
| contentId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | string | yes | – |
No examples provided.
betterpost_delete_project Delete project ~40
Permanently deletes a project and everything in it — its sources, stories, and content. Cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | string | yes | – |
No examples provided.
betterpost_derive_content Derive content ~61
Transform an existing piece into another format (e.g. newsletter → tweet). No fetching; reuses the source stories and topic.
| Name | Type | Req | Description |
|---|---|---|---|
| fromContentId | string | yes | – |
| tieIn | string | – | – |
| type | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| content | object | yes | The generated content. Fields present depend on `type`. |
| contentId | string | yes | – |
| creditsCharged | integer | yes | – |
| imagesHosted | integer | yes | – |
| publicUrl | string | yes | – |
| storyCount | integer | yes | – |
| summary | string | yes | – |
| topic | string | yes | – |
| type | string | yes | – |
No examples provided.
betterpost_expand_coverage Expand coverage ~224
Broadens a project's coverage: expands the relevance criteria (when needed), finds more sources across news, the web, and the relevant social platforms, and fetches them inline. Applies on a `topic_unavailable`, `no_stories`, or low-coverage signal. May return `warming: true` with `retryAfterMs` (~60s), meaning the newly gathered stories are still landing. An out-of-scope `focus` requires `confirmedByUser: true`; without it, it returns a `confirmation_required` error. No credits are charged.
| Name | Type | Req | Description |
|---|---|---|---|
| addAsCriteria | boolean | – | Also append an in-scope `focus` as a standing relevance criterion (out-of-scope, confirmed foci are added automatically). |
| confirmedByUser | boolean | – | Set true once the user has agreed to widen the project to an out-of-scope `focus`. |
| focus | string | – | The topic to get more on (e.g. "League of Legends"). Omit to broaden the whole project. |
| projectId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| criteriaAdded | array | yes | – |
| retryAfterMs | number | yes | – |
| sourcesAdded | array | yes | – |
| storiesAdded | integer | yes | – |
| warming | boolean | yes | – |
No examples provided.
betterpost_generate_content Generate content ~279
Generate a new piece of content for a project from its timely, relevant stories. Fast in steady state. Charges credits on success only. If you pass a `topic` the project has no stories about, this returns a `topic_unavailable` error (no charge) carrying an `inScope` flag and next steps — it never silently writes an off-topic piece.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
| reuse | boolean | – | Reuse the most recent topic. |
| tieIn | string | – | A product/service to weave in. |
| topic | string | – | Steer the piece to a specific topic. Generation only writes from stories actually about it. If none exist yet, it returns topic_unavailable (no charge) with an inScope flag: inScope:true means the to… |
| type | string | yes | Output format. 'x' and 'bluesky' are generated as a single post or, more often, a short numbered thread of connected posts (multiple tweets) when there is enough to say — this is the default for thos… |
| wordLimit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| content | object | yes | The generated content. Fields present depend on `type`. |
| contentId | string | yes | – |
| creditsCharged | integer | yes | – |
| imagesHosted | integer | yes | – |
| publicUrl | string | yes | – |
| storyCount | integer | yes | – |
| summary | string | yes | – |
| topic | string | yes | – |
| type | string | yes | – |
No examples provided.
betterpost_get_content Get content ~26
Fetch one piece of content in full.
| Name | Type | Req | Description |
|---|---|---|---|
| contentId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| content | object | yes | The generated content. Fields present depend on `type`. |
| createdAt | – | yes | ISO 8601 datetime string |
| derivedFromContentId | – | yes | – |
| id | string | yes | – |
| projectId | string | yes | – |
| publicUrl | string | yes | – |
| storyCount | integer | yes | – |
| summary | – | yes | – |
| topicId | – | yes | – |
| type | string | yes | – |
| wordLimit | – | yes | – |
No examples provided.
betterpost_get_project Get project ~47
Returns one project with its relevance `criteria` (each with an id, so a criterion can be targeted for removal via betterpost_update_project).
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| additionalInstructions | – | yes | – |
| audience | string | yes | – |
| createdAt | – | yes | ISO 8601 datetime string |
| criteria | array | yes | – |
| description | – | yes | – |
| hasXSource | boolean | yes | – |
| id | string | yes | – |
| industry | – | yes | – |
| maxStoryAgeDays | integer | yes | – |
| status | string | yes | – |
| timezone | string | yes | – |
| title | string | yes | – |
| tone | – | yes | – |
| updatedAt | – | yes | ISO 8601 datetime string |
No examples provided.
betterpost_get_settings Get settings ~35
Returns a project's per-content-type settings (wordLimit and additionalInstructions for each channel).
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contentTypeSettings | array | yes | – |
No examples provided.
betterpost_get_usage Get usage ~21
Your credit balance, freeze state, and recent spend.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| creditBalance | integer | yes | – |
| frozen | boolean | yes | – |
| kind | string | yes | – |
| recentSpendUsd | number | yes | – |
No examples provided.
betterpost_hide_story Hide story ~34
Hides a story so generation ignores it. Reversible with unhide_story.
| Name | Type | Req | Description |
|---|---|---|---|
| storyId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| hidden | boolean | yes | – |
| storyId | string | yes | – |
No examples provided.
betterpost_humanize Humanize text ~145
Rewrite existing text into BetterPost's readable, human voice. Preserves the meaning, facts, links, and format; returns the rewritten text plus short notes on what changed. Pass `projectId` to write in that project's tone and instructions, `type` to apply a channel's style, or `tone` to set the voice directly.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | – | Use this project's tone and writing instructions. |
| text | string | yes | The text to humanize (max 30,000 characters). |
| tone | string | – | Tone override; wins over the project tone. |
| type | string | – | Apply this channel's style rules to the rewrite. |
| Name | Type | Req | Description |
|---|---|---|---|
| changes | array | yes | Short notes on the main edits made |
| creditsCharged | integer | yes | – |
| inputWords | integer | yes | – |
| text | string | yes | The rewritten text, a drop-in replacement for the input |
No examples provided.
betterpost_list_content List content ~34
List a project's content (summaries + shareable `publicUrl` links).
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | yes | – |
No examples provided.
betterpost_list_projects List projects ~33
Returns your projects, each with its relevance `criteria` (with ids) that define what counts as on-topic.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| projects | array | yes | – |
No examples provided.
betterpost_list_sources List sources ~111
Returns one slimmed page of a project's sources plus project-wide `total` and `counts` (ok/failing/disabled/pending, and byType). Page with `limit` (default 50) and `offset`, following the returned `nextOffset` until it is null.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max sources to return (default 50). |
| offset | integer | – | Number of sources to skip; use the returned nextOffset to page. |
| projectId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| counts | object | yes | – |
| limit | integer | yes | – |
| nextOffset | – | yes | – |
| offset | integer | yes | – |
| returned | integer | yes | – |
| sources | array | yes | – |
| total | integer | yes | – |
No examples provided.
betterpost_list_stories List stories ~73
Returns a project's gathered stories, each with `title`, `url`, `summary`, `relevancy`, `publicationDate`, and `isManual`/`isHidden` flags. Pass includeHidden to include hidden ones.
| Name | Type | Req | Description |
|---|---|---|---|
| includeHidden | boolean | – | – |
| projectId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| stories | array | yes | – |
No examples provided.
betterpost_remove_source Remove source ~40
Removes a source from a project. Its already-gathered stories stay; the source is no longer fetched.
| Name | Type | Req | Description |
|---|---|---|---|
| sourceId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| removed | string | yes | – |
No examples provided.
betterpost_suggest_topics Suggest topics ~87
Clusters a project's current stories into a few candidate angles — each with a label, how many stories back it, and example headlines — and warms the project (gathers and ranks fresh stories) in the process. Returns topics you can offer the user before generate_content.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| projectId | string | yes | – |
| type | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
| topics | array | yes | – |
No examples provided.
betterpost_unhide_story Unhide story ~33
Unhides a previously hidden story so generation can use it again.
| Name | Type | Req | Description |
|---|---|---|---|
| storyId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| hidden | boolean | yes | – |
| storyId | string | yes | – |
No examples provided.
betterpost_update_project Update project ~218
Updates a project's title, audience, description, tone, freshness window, timezone, or relevance criteria, and returns the updated project with its criteria. Changing title/audience/description re-derives the relevance criteria (replace-all), which broadens or narrows what counts as on-topic. To edit criteria incrementally instead, pass `patch.addCriteria` (texts to append) and/or `patch.removeCriteria` (criterion ids from get_project/list_projects). Dates default to US Eastern unless a `timezone` (an IANA name like "America/New_York") is set.
| Name | Type | Req | Description |
|---|---|---|---|
| patch | object | – | Partial update: EVERY field is optional — include only the fields you want to change and omit the rest (an omitted field is left untouched; there are no required patch fields). Passing an empty objec… |
| projectId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| additionalInstructions | – | yes | – |
| audience | string | yes | – |
| createdAt | – | yes | ISO 8601 datetime string |
| criteria | array | yes | – |
| description | – | yes | – |
| hasXSource | boolean | yes | – |
| id | string | yes | – |
| industry | – | yes | – |
| maxStoryAgeDays | integer | yes | – |
| status | string | yes | – |
| timezone | string | yes | – |
| title | string | yes | – |
| tone | – | yes | – |
| updatedAt | – | yes | ISO 8601 datetime string |
No examples provided.
betterpost_update_settings Update settings ~90
Patches one content type's wordLimit and/or additionalInstructions (free-form writing guidance for that type; pass an empty string to clear it). Project-wide preferences (title/audience/tone, project-wide additionalInstructions) live on betterpost_update_project.
| Name | Type | Req | Description |
|---|---|---|---|
| additionalInstructions | – | – | – |
| projectId | string | yes | – |
| type | string | yes | – |
| wordLimit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| updated | object | yes | – |
No examples provided.
How do I install the BetterPost MCP server?
BetterPost is a hosted endpoint at https://betterpost.ai/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 · betterpost.ai
claude mcp add --transport http ai-betterpost-server 'https://betterpost.ai/mcp'
What is the BetterPost MCP server?
BetterPost is an MCP server listed in the public MCP registry as ai.betterpost/server. Finds timely sources across news, social, and the web and writes posts worth publishing. This page covers its hosted endpoint (https://betterpost.ai/mcp).
Is the BetterPost MCP server safe to use?
BetterPost scores 91 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 BetterPost MCP server expose?
BetterPost exposes 23 tools: betterpost_create_project, betterpost_generate_content, betterpost_derive_content, betterpost_list_content, betterpost_get_content, and 18 more. Their descriptions and schemas cost roughly 2,120 tokens of context every time the server is loaded.
Does the BetterPost MCP server require authentication?
Yes. BetterPost asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the BetterPost MCP server still maintained?
BetterPost 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.
What did VerifyMCP test on the BetterPost MCP server?
VerifyMCP ran 13 checks on BetterPost, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.