Pepitahq MCP Server

@pepitahq/mcp npm v0.22.0

Published by @pepitahq — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

pepita local MCP server (stdio) — drive your pepita sites from Claude.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Unconstrained URL/host parameter "url" on "add_content_image"MTC-CAP-007

Tool "add_content_image" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool add_content_image · inputSchema.properties.url

Tools 44

Each tool and what it can reach — statically extracted from the published source.

  • add_content_imageingests untrusted input
  • delete_email_template_imageingests untrusted input
  • get_form_export_urlingests untrusted input
  • get_video_original_urlingests untrusted input
  • read_email_templateingests untrusted input
  • add_content_recordsno sensitive capability
  • create_previewno sensitive capability
  • create_siteno sensitive capability
  • delete_content_recordno sensitive capability
  • delete_content_templateno sensitive capability
Show 34 more tools ↓
  • delete_email_templateno sensitive capability
  • delete_previewno sensitive capability
  • delete_site_fileno sensitive capability
  • delete_videono sensitive capability
  • edit_site_fileno sensitive capability
  • get_building_guideno sensitive capability
  • get_content_image_upload_urlno sensitive capability
  • get_form_records_countno sensitive capability
  • get_site_statusno sensitive capability
  • list_content_recordsno sensitive capability
  • list_content_templatesno sensitive capability
  • list_email_template_imagesno sensitive capability
  • list_email_templatesno sensitive capability
  • list_form_recordsno sensitive capability
  • list_previewsno sensitive capability
  • list_site_filesno sensitive capability
  • list_sitesno sensitive capability
  • list_videosno sensitive capability
  • publish_content_recordno sensitive capability
  • publish_siteno sensitive capability
  • read_content_fileno sensitive capability
  • read_content_templateno sensitive capability
  • read_served_pageno sensitive capability
  • read_site_fileno sensitive capability
  • rename_videono sensitive capability
  • save_content_templateno sensitive capability
  • save_email_templateno sensitive capability
  • unpublish_content_recordno sensitive capability
  • update_content_recordno sensitive capability
  • update_previewno sensitive capability
  • write_content_fileno sensitive capability
  • write_content_templateno sensitive capability
  • write_email_templateno sensitive capability
  • write_site_fileno sensitive capability

What this scan could not see

Versions 10

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.22.0 latest A 96/100 1 1.13.0 2026-09-09
v0.21.1 A 96/100 1 1.12.1 2026-08-13
v0.14.1 A 96/100 0 1.12.1 2026-08-09
v0.13.0 A 96/100 0 1.12.1 2026-08-07
v0.12.1 A 96/100 0 1.12.1 2026-08-06
Show 5 more versions ↓
v0.12.0 A 96/100 0 1.12.1 2026-08-02
v0.10.0 A 96/100 0 1.12.1 2026-07-29
v0.8.0 A 96/100 0 1.12.1 2026-07-28
v0.6.1 A 96/100 0 1.10.0 2026-07-25
v0.5.1 A 96/100 0 1.9.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/pepitahq-mcp/badge.svg)](https://mcptrustchecker.com/registry/pepitahq-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/pepitahq-mcp"><img src="https://mcptrustchecker.com/registry/pepitahq-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/pepitahq-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @pepitahq/mcp --online

Use the free API → How scoring works

More in Developer Tools