Enhanced MCP server for Limitless Pendant with advanced conversation analysis, meeting detection, action item extraction, and comprehensive
Free
Nothing to run from here
Pepitahq is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
pepita local MCP server (stdio) — drive your pepita sites from Claude.
Quickstart
# 1 — run it from where its publisher ships it
npx -y @pepitahq/mcp
# 2 — ask your agent something
> pepita local MCP server (stdio) — drive your pepita sites from Claude.
Pepitahq is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
PEAll 1 server
@pepitahq1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Pepitahq as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add pepitahq-mcp -- npx -y @pepitahq/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
44 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List the user
Takes no parameters.
Example callreturns →
Create a NEW pepita website in pepita
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
List the file paths that make up a pepita website (in the cloud, NOT on the local disk). Reads the working copy by default; state
Takes no parameters.
Example callreturns →
Read a text file from a pepita website (fetched from the cloud, NOT the local filesystem \u2014 use this, not the Read tool, to see a pepita site
Takes no parameters.
Example callreturns →
Create or overwrite a TEXT file in a pepita website
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Publish a pepita website \u2014 deploy / ship / put it live / go live \u2014 promoting the current working copy to the public live URL. Docs: https://pepita.dev/developers/#publish_site
Takes no parameters.
Example callreturns →
Freeze the current pepita site as a NEW shareable preview / share link \u2014 a stable URL you can send to anyone (for review/staging) and update or delete later. Docs: https://pepita.dev/developers/#create_preview
Takes no parameters.
Example callreturns →
List a pepita site
Takes no parameters.
Example callreturns →
Push the current pepita site onto an EXISTING preview / share link \u2014 same URL, new content. Use the preview name from list_previews. Docs: https://pepita.dev/developers/#update_preview
Takes no parameters.
Example callreturns →
Stop serving a pepita site preview / share link. The version stays restorable from History. Docs: https://pepita.dev/developers/#delete_preview
Takes no parameters.
Example callreturns →
List the videos uploaded to a pepita site (they live in pepita
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Rename an asset in a pepita site
Takes no parameters.
Example callreturns →
Permanently delete a pepita video asset \u2014 the original, the streaming ladder and the poster. Assets are NOT versioned: restoring an old site version will not bring it back, and any page referencing it stops playing. Docs: https://pepita.dev/developers/#delete_video
Takes no parameters.
Example callreturns →
REQUIRED READING before writing forms, confirmation emails, video markup, repeating content collections or _headers on a pepita site: returns the exact platform contract for the topic, so the site works with pepita
Takes no parameters.
Example callreturns →
List a pepita site
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Create or update the confirmation email pepita sends when a form is submitted \u2014 UPSERT by form name (the form
Takes no parameters.
Example callreturns →
Promote a template
Takes no parameters.
Example callreturns →
Delete a form
Takes no parameters.
Example callreturns →
List the images stored beside one confirmation-email template
Takes no parameters.
Example callreturns →
Permanently delete one image beside a confirmation-email template
Takes no parameters.
Example callreturns →
List a site
Takes no parameters.
Example callreturns →
Read one content template \u2014 the COMPLETE HTML document for a single item, with {{placeholder}} fields. Read it BEFORE changing it or adding items, so you keep what should not change and know which fields the template actually names. For the authoring rules call get_building_guide with topic
Takes no parameters.
Example callreturns →
Create or replace a content collection
Takes no parameters.
Example callreturns →
A content collection
Takes no parameters.
Example callreturns →
Replace a content collection
Takes no parameters.
Example callreturns →
Make a content collection
Takes no parameters.
Example callreturns →
Delete a content collection
Takes no parameters.
Example callreturns →
Fetch a picture from a public web address into a content collection
Takes no parameters.
Example callreturns →
Get a short-lived address that accepts ONE picture file uploaded straight from this machine, for a content collection
Takes no parameters.
Example callreturns →
One collection
Takes no parameters.
Example callreturns →
Add items to a collection \u2014 an ARRAY, so many in one call. Each item is a JSON object whose keys are the field names the TEMPLATE names: call read_content_template first, because a field the template does not name is refused rather than stored. ONE field is always required:
Takes no parameters.
Example callreturns →
Replace one existing item
Takes no parameters.
Example callreturns →
Put one item on the live site. New items are DRAFTS \u2014 they show in the owner
Takes no parameters.
Example callreturns →
Take one item off the live site, keeping it as a draft the owner can still see and edit. Takes effect immediately. Nothing is deleted \u2014 delete_content_record is the one that cannot be undone. Docs: https://pepita.dev/developers/#unpublish_content_record
Takes no parameters.
Example callreturns →
Remove one item from a collection. It disappears from the site immediately and cannot be recovered. Get the id from list_content_records, and ask the owner first unless they asked for it in as many words. Docs: https://pepita.dev/developers/#delete_content_record
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Read what visitors submitted through one of a site
Takes no parameters.
Example callreturns →
A time-limited link to download one form
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Pepitahq costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 96 / 100
Release 0.22.0 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings1 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest4c9c955c8d5e909d4e63b57bf9e4b9a766ea0ed973cd43d4d0d070814ebbe917
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (44 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_sites | no tags | |
| create_site | no tags | |
| get_site_status | no tags | |
| list_site_files | no tags | |
| read_site_file | no tags | |
| write_site_file | no tags | |
| edit_site_file | no tags | |
| read_served_page | no tags | |
| delete_site_file | no tags | |
| publish_site | no tags | |
| create_preview | no tags | |
| list_previews | no tags | |
| update_preview | no tags | |
| delete_preview | no tags | |
| list_videos | no tags | |
| get_video_original_url | untrusted-input | |
| rename_video | no tags | |
| delete_video | no tags | |
| get_building_guide | no tags | |
| list_email_templates | no tags | |
| read_email_template | untrusted-input | |
| write_email_template | no tags | |
| save_email_template | no tags | |
| delete_email_template | no tags | |
| list_email_template_images | no tags | |
| delete_email_template_image | untrusted-input | |
| list_content_templates | no tags | |
| read_content_template | no tags | |
| write_content_template | no tags | |
| read_content_file | no tags | |
| write_content_file | no tags | |
| save_content_template | no tags | |
| delete_content_template | no tags | |
| add_content_image | untrusted-input | |
| get_content_image_upload_url | no tags | |
| list_content_records | no tags | |
| add_content_records | no tags | |
| update_content_record | no tags | |
| publish_content_record | no tags | |
| unpublish_content_record | no tags | |
| delete_content_record | no tags | |
| get_form_records_count | no tags | |
| list_form_records | no tags | |
| get_form_export_url | untrusted-input |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest4c9c955c8d5e909d
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 0.22.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.22.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Pepitahq in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.