Pulsecheck Alternative: an Indie MCP Board vs HITL Merges

Looking for a pulsecheck alternative when the job is a multi-app feedback board with MCP triage, and you want a human confirm before statuses change or duplicates merge? Pulsecheck (pulsecheckapp.com) is a hosted board for indie developers who ship several apps from one dashboard. It has anonymous voting by default, a public roadmap on every plan, an embeddable widget on Pro, and a remote MCP server on Pro so an assistant can read and write the board. Feedjolt is a hosted human-in-the-loop (HITL) voting board with public feedback, voting, a public roadmap, a changelog, and MCP where agents propose and a human decides. Insights never merges without that confirm.

Prices below are from the 2026-10-05 cards on pulsecheckapp.com/#pricing: Free at $0 forever, Pro at $19/month, and Team at $49/month marked Coming Soon. Re-open those cards the week you buy. Nearby: MCP feedback triage and HITL merges.

What Pulsecheck optimizes for

A pulsecheck feedback board is hosted. The hero line is: "Your users are talking. Are you listening?" and "Bug reports and feature requests for indie developers who ship fast and listen faster." The product marks Early Access. Trust lines on the homepage include "Edge-Deployed — Runs on Cloudflare," "Zero Per-User Pricing — Unlimited voters. Always.," and "Dark Mode First."

One dashboard covers every app. Voting is anonymous by default: no login or account required for voters, and each visitor gets a unique voter ID stored locally so they can only vote once per item. When you ship a feature, you mark it shipped and users who asked for it get notified. Their shipping line is: "No 14-step workflow. No approval chain." The public roadmap uses Planned, In Progress, and Shipped, and they say it is available on all plans, free and Pro.

Every project has analytics. Pro adds time-series trends, average time to close, and period comparisons. The embeddable widget is a script tag on Pro (Shadow DOM isolated, under 5KB gzipped), with iframe support and iOS via a Safari view controller with "No SDK needed." Use cases they name: SaaS and web apps, iOS and mobile apps, and open-source projects. A headless submit API is documented at /docs/api: no authentication is required for submissions, and submissions are rate-limited by IP address.

The founder post "Why I Built PulseCheck" is by Dan Elggren (February 28, 2026). The footer is "© 2026 Pulsecheck" and "Built by Out of Office Outdoors." Primary product marks say Pulsecheck; some docs and compare titles spell PulseCheck. Spelling below stays Pulsecheck except when quoting a title that uses PulseCheck.

Pulsecheck is its own product

The footer is "© 2026 Pulsecheck." Its compare pages position it against Canny, Nolt, and Featurebase. Uplooped is a different product, already covered in the Uplooped alternative post. For a wider buying pass, see how to choose a feedback board.

What the pricing section showed on 2026-10-05

Prices below are the homepage cards at /#pricing under "Simple pricing. No per-user traps." Their line about other tools charging per tracked user is Pulsecheck's claim about those tools, not a verified figure for them. Visible cards that day:

• Free: $0 forever. "Perfect for trying it out." One project, unlimited feedback, unlimited voters, public board and roadmap, feedback analytics, and email notifications. Button: "Get Started Free."
• Pro: $19 /month. "For indie devs who ship." Unlimited projects, embeddable widget, Connect AI assistants (MCP), custom branding and logo, Slack notifications, advanced analytics and trends, admin comments, CSV export, and remove the "Powered by" badge. Button: "Upgrade to Pro."
• Team: $49 /month, Coming Soon. "When it's not just you anymore." Everything in Pro, plus multiple admin users, API access, webhooks, advanced analytics, and priority support. Button: "Coming Soon."

Under the cards: "Start free, upgrade when you're ready. Cancel anytime." On 2026-10-05 the live cards showed Free at $0 forever, Pro at $19/month, and Team at $49/month marked Coming Soon. They are still that day's cards, not a locked price.

Billing interval

The cards say "/month" on Pro and Team. There is no monthly/yearly toggle, no annual price, and no save-N% line on those cards. Terms section 5 says Pulsecheck offers a free tier and a paid Pro plan at $19/month, that Pro subscriptions are billed monthly and renew automatically, that cancel runs through the Stripe Customer Portal with access to the end of the billing period, and that they do not offer refunds for partial months. Pricing changes come with 30 days' notice. No free trial appears on the cards.

Free vs Pro is a project, embed, MCP, and branding gate

Voters and feedback are unlimited on Free. The gates that change at Pro are projects, the widget, MCP, branding, Slack, admin comments, CSV, and badge removal. Terms section 6 agrees: Free accounts are limited to 1 project, and features like custom logos, admin comments, embeddable widgets, and removing the "Powered by Pulsecheck" badge require Pro.

Two pages disagree on how much lands at $19. The Canny compare page says "All features included at $19/mo," while the pricing section lists multiple admins, API access, webhooks, and priority support on the Coming Soon Team card at $49/month. Treat the pricing cards as the plan gates, and confirm with Pulsecheck if you need Team features today.

The Team card lists "API access" as Coming Soon, while /docs/api already documents a public, unauthenticated submit endpoint. Both are true on their own pages: there is a headless submit path today, and a broader Team API access line is still marked Coming Soon. Custom branding and logo sit on the Pro card, not on Free.

Pulsecheck's MCP server

Source: the "Connect AI Assistants (MCP) — PulseCheck" docs at /docs/mcp, labelled a Pro feature. The changelog says MCP shipped 2026-06-12. The server speaks MCP over Streamable HTTP and authenticates with a personal access token. Every request is owner-scoped. The server URL is https://pulsecheckapp.com/api/v1/mcp. Tokens start with pc_mcp_, are shown once, are stored hashed, and are revocable from Billing → Connect AI (MCP). Documented clients include Claude Code, Claude Desktop (via mcp-remote), and Cursor.

Nine tools. Read: list_projects, list_feedback, get_feedback, get_analytics. Write: create_feedback, update_status (notifies the submitter), add_comment (public reply or a private internal note), set_pin, and set_lock. The endpoint is rate-limited to 120 requests per minute; exceeding it returns 429. The token stops working if the plan is no longer Pro. An example prompt in the docs asks the assistant to flag likely duplicates, then set the highest-voted one to planned and add a comment.

Those owner-scoped tokens, hashed storage, revocation, and the rate limit are real safeguards. The docs show write tools that act directly. A merge tool is not in that nine-tool list, and a confirm or approval step before a write tool runs is not described in those docs. For a solo developer who wants speed, that direct path is a fair choice. For a team that wants an agent to suggest and a person to approve, especially before duplicates merge, the HITL model fits.

The HITL difference: proposals and merges

Feedjolt is a hosted HITL voting board. Agents propose changes over MCP and a human decides. Insights never merges without that human confirm. Contrast with the dated Pulsecheck MCP docs: an assistant with a Pro token can change a status (which emails the submitter) or post a public reply directly, and no merge tool appears in the nine-tool list. Stay on Pulsecheck when direct writes are the job. Choose a HITL board when proposals need a human gate before they land, and when merges must wait for that confirm. The Feedjolt merge flow is covered in merge duplicate feature requests with HITL. For MCP triage patterns across tools, see MCP feedback comparisons.

Hosting and privacy

Privacy (Effective March 4, 2026) says: "Your data is stored on Cloudflare's global network: Database: Cloudflare D1 (SQLite at the edge). File storage: Cloudflare R2 (project logos only)." Third parties named: Stripe for payments, Resend for transactional email, and Cloudflare for hosting, CDN, DNS, and storage. They say they do not use analytics services, tracking pixels, or advertising networks. The voter ID is a random hex string in localStorage. Admin auth is an httpOnly JWT cookie for 7 days. Account deletion is by request. The privacy page also states that Cloudflare maintains SOC 2 Type II, ISO 27001, and PCI DSS certifications; those are Cloudflare's certifications, not Pulsecheck's own.

No hosting region or country appears on those pages. Cloudflare's global network names no country or region.

Pulsecheck vs Canny

For pulsecheck vs canny, start with Pulsecheck's own "PulseCheck vs Canny" compare page and the homepage FAQ. That compare page (dated March 2026) says Canny Free covers 25 tracked users, that Pulsecheck's comparison table lists Canny's Core tier at $19/month, the same as Pulsecheck Pro, with no integrations and a 100 tracked-user cap, and that Growth sits higher with unlimited users and integrations. It also notes: "Canny pricing as of March 2026. Check canny.io for current pricing." Their fair line: "Choose Canny if you need AI categorization, Jira/Linear integrations, or custom domains."

Those two Pulsecheck surfaces do not match. The homepage FAQ says Canny starts at a higher monthly tier and charges per tracked user. The homepage comparison table lists Canny's Core tier at $19/month, the same as Pulsecheck Pro, with a footnote on Core's 100-user cap and a higher Growth tier. Both are Pulsecheck's claims. Canny's current price is unknown, so check canny.io before comparing. Their Nolt and Featurebase compare pages are also dated March 2026, so treat those competitor prices as Pulsecheck's claims and check each vendor. Nearby: Feedjolt vs Canny, flat-price Canny alternatives, Nolt alternatives, and Feedjolt vs Featurebase.

Which job fits which board

On the 2026-10-05 cards, Free is $0 forever with one project, unlimited feedback and voters, a public board and roadmap, analytics, and email notifications. Pro is $19/month with unlimited projects, the widget, MCP, branding, Slack, advanced analytics, admin comments, CSV, and badge removal. Team is $49/month and Coming Soon, with multiple admins, API access, webhooks, and priority support.

Stay on Pulsecheck when you ship several small apps, want anonymous voting with no login, a public roadmap on Free, flat $19 Pro, an embeddable widget, and an assistant that can change statuses and reply directly through MCP. Wait or look elsewhere if you need multiple admins, webhooks, or the Team-tier API today, or a custom domain, SSO, or Jira/Linear sync. A hosted HITL board fits when agents should propose and a human should decide, and when merges must never happen without that confirm. Flat boards without a per-tracked-user tax are also covered in flat-price feedback boards and public roadmap tools.

Where Feedjolt places

Feedjolt is a hosted HITL voting board: public feedback, voting, a public roadmap, a changelog, and MCP so agents can propose changes and a human decides. Insights never merges without that human confirm. It is not a suite. Custom domain, SSO, native SDKs, a knowledge base, guest voting, email when something ships, and Jira sync are not Feedjolt claims.

FAQ

What is a practical pulsecheck alternative if you want MCP with a human confirm?

A practical pulsecheck alternative is a hosted voting board for public feedback, votes, a roadmap, and a changelog, with MCP where agents propose and a human decides before statuses change or duplicates merge. It is not a second copy of Pulsecheck. Pulsecheck already has the multi-project dashboard, anonymous voting, a public roadmap on Free, flat Pro at $19/month on the 2026-10-05 cards, and nine Pro MCP tools with direct writes. Feedjolt is the HITL board: agents propose over MCP, a human decides, and Insights never merges without that confirm.

On pulsecheck vs canny, what do Pulsecheck's own pages say?

Pulsecheck's compare page (dated March 2026) lists Canny's Core tier at $19/month, the same as Pulsecheck Pro, and says Core caps tracked users, with a higher Growth tier. The homepage FAQ says Canny starts at a higher monthly tier and charges per tracked user. The homepage table also lists Canny at $19/month with a Core footnote. Those Pulsecheck surfaces disagree with each other. Canny's current price is unknown, so check canny.io before comparing.

What does a pulsecheck feedback board include on Free, and what waits for Pro or Team?

On Free, at $0 forever on 2026-10-05, a pulsecheck feedback board includes 1 project, unlimited feedback and voters, a public board and roadmap, feedback analytics, and email notifications. Unlimited projects, the embeddable widget, Connect AI assistants (MCP), custom branding and logo, Slack notifications, advanced analytics and trends, admin comments, CSV export, and badge removal wait for Pro at $19/month. Multiple admin users, API access, webhooks, and priority support wait for Team at $49/month, which was Coming Soon that day. Pro is billed monthly per their terms. No annual price or trial appears on the cards.

Where to start

Read the project, MCP, and branding gates before the feature list. Pulsecheck when the $0 forever card is the board you want, Pro at $19/month on the 2026-10-05 cards when you need unlimited projects, the widget, or MCP with direct writes, and Team at $49/month when multiple admins and webhooks matter and that tier is live. Feedjolt when you want a hosted HITL voting board and a human decision on what an agent publishes, including merges. Start on the Feedjolt homepage:

https://www.feedjolt.com/?utm_source=blog&utm_medium=organic&utm_campaign=seo-pulsecheck-alternative