HumanPost 1.0.4 — OpenAI review walkthrough

Actual ChatGPT review walkthrough for HumanPost 1.0.4, using only the isolated OpenAI Review sample workspace.

This edited sequence of actual UI captures demonstrates read-only scope/refusal tests, separate affirmative write consent, creation of an unqueued sample draft, saved-content/status read-back, and disconnection. Idle time is shortened. Password entry, tokens, and unrelated customer data are excluded. Both ChatGPT test grants were revoked.

Review ZIP bundles were provided directly to OpenAI's publisher portal. This release publishes the walkthrough only. The latest complete public installable ZIP bundles remain in v1.0.3: https://github.com/HumanPost-co/humanpost-mcp/releases/tag/v1.0.3 . Functional integration behavior is unchanged; 1.0.4 adds review metadata.

The cases ran through private ChatGPT MCP test connectors. Publisher package and skill checks pass. ChatGPT's separate private archive importer returned a generic error for both bundle formats, so full bundled installation is not claimed. Account setup, queueing, live social publication, rendering, and tasks were not performed in these sample tests. Reviewer credentials are provided only in OpenAI's private review form.

HumanPost 1.0.3 — TikTok and Instagram listing update

Improve HumanPost discovery for TikTok and Instagram account setup, social content preparation, and human posting across multiple accounts.

• Clearer subtitle, About section, capability labels, keywords, and three starter prompts.
• Explain that human operators handle account setup and posting, with asynchronous status and explicit publication approval.
• Clarify use of existing videos/images, editable carousel drafts, schedules, published links, and available analytics.
• Keep the hosted MCP URL, OAuth settings, scopes, and tool behavior unchanged. The Official MCP Registry service record remains at 1.0.2; this is a client listing-package update.

Both 22-file archives are reproducible from tag v1.0.3, contain no credentials, and have published SHA-256 checksums. Marketplace approval is separate from this package release.

HumanPost MCP 1.0.2 — OAuth connections

HumanPost now supports company-scoped OAuth connections at https://humanpost.com/mcp, using S256 PKCE and dynamic client registration. Users sign in to HumanPost, choose one company, and grant specific permissions. Writes are off by default; connections can be revoked in Settings → API Keys.

• humanpost-plugin-1.0.2.zip: portable Agent Plugins bundle with the canonical OAuth endpoint. Claude/Grok, Cline and Muse compatibility files retain the existing API-key setup.
• humanpost-openai-plugin-1.0.2.zip: OpenAI upload bundle with explicit OAuth/DCR configuration and read-only default scopes. Publisher identity verification and marketplace review are still required.
• SHA256SUMS: checksums for both deterministic 22-file archives. No credentials or hosted backend source are included.

Validation: portable schemas, Claude manifest, official Registry manifest validation, archive integrity, reproducible builds and credential-pattern scan passed. The deployed service passed live browser consent, scoped reads, denied posting, PKCE/audience rejection, refresh/downscope, replay revocation, explicit revocation and legacy API-key compatibility in TEST COMPANY. All test credentials were revoked; no posts or model calls were made.

To rebuild: python3 scripts/build_release.py --output-dir /tmp/humanpost-release.

HumanPost MCP integration 1.0.1

Adds explicit Cline configuration and clarifies that the MCP advertises its complete tool catalog while enforcing scopes on each call.

Authenticated validation against hosted server 2.4.0 passed with a temporary accounts:read key in an existing test company:

• MCP initialization and discovery of 45 tools.
• Successful get_context call.
• Posting call denied by the read-only scope.
• The documented configuration loaded and connected through Cline Core's MCP client, with a successful context call and denied write. No model calls were made.
• The key was revoked after testing and HTTP 401 confirmed revocation.

No content was posted, no posting/rendering credits were consumed, and no customer data or credentials are included in this package. Full write workflows were not exercised in this distribution check.

HumanPost requires an account and company-scoped API key. Public OpenAI remote-MCP submission still requires a supported authentication flow and developer identity verification; Muse MCP is configured separately. Package availability does not imply marketplace approval.

The ZIP contains public integration files, with its root plugin manifest. Verify the SHA-256 against the attached checksum file.

HumanPost MCP integration 1.0.0

HumanPost's public integration package provides client configurations for Cursor, Claude Code, Grok Build, and Muse Code, plus the HumanPost publishing skill for compatible agent hosts.

The hosted MCP requires a HumanPost account and company-scoped API key. The ZIP contains no credentials or hosted backend source. Tool approval and HumanPost plan allowances still apply.

Validation: portable manifest schemas, official Claude plugin validation, skill format validation, Grok catalog checks, and a successful public Skills CLI installation. The unauthenticated endpoint returns HTTP 401; full authenticated workflows have not been verified as part of this release.

OpenAI public remote-MCP submission remains blocked by API-key authentication support and developer verification. Muse uses a separately configured authenticated MCP entry. This package release does not claim approval in any marketplace.

The official MCP Registry entry is active: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.HumanPost-co%2Fhumanpost/versions/latest

Download the ZIP for local plugin import where supported, or install directly from the repository using the README. Verify the archive against SHA256SUMS.