# Pulore App Planner (remote · pulore.com)

Plan a software project, check website speed, find Pulore case studies, get a booking link.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `pulore.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-pulore-app-planner/pulore.md), [page](https://verifymcp.io/servers/com-pulore-app-planner/pulore)

## Channel facts

- Endpoint: `https://pulore.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_project_brief_to_pulore).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1622 tokens (~324/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Pulore App Planner MCP server?

Pulore App Planner is a hosted endpoint at https://pulore.com/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.

### Claude

```bash
claude mcp add --transport http com-pulore-app-planner 'https://pulore.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-pulore-app-planner": {
      "url": "https://pulore.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-pulore-app-planner": {
      "type": "http",
      "url": "https://pulore.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-pulore-app-planner]
url = "https://pulore.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-pulore-app-planner": {
      "type": "remote",
      "url": "https://pulore.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-pulore-app-planner --url 'https://pulore.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-pulore-app-planner:
    url: "https://pulore.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-pulore-app-planner": {
      "Transport": "http",
      "Url": "https://pulore.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-pulore-app-planner -t streamable-http -u 'https://pulore.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-pulore-app-planner": {
      "type": "http",
      "url": "https://pulore.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-04 (score 63)

First indexed and scored.

## MCP tools (5)

### `scope_software_project` (~616 tokens)

Scope a software project

Use this when someone wants to know what it would take to build a software product, such as an app, website, SaaS, marketplace, internal tool, AI feature or MVP: how long it would take, what it would cost, what team or tech stack it needs, or a build plan or estimate for their idea. Returns a rough plan with effort ranges for each feature, the team, a timeline range, phases, a suggested stack and a budget (the hours priced at $100 to $150 an hour). The ranges reflect how Pulore builds today, with managed services such as Clerk and Stripe where they fit and AI-assisted development. The plan is calculated locally from fixed estimation tables; this tool does not save a project or call an external service. Map the idea to the closest features in the list and say in your reply what doesn't fit. Results are planning ranges, not a quote. Don't use it for projects that aren't software (like renovations, events or business plans), for task or project management, or to write code.

Input parameters:

- `compliance` (array): Compliance it must meet, if any: hipaa (HIPAA (US health data)), soc2 (SOC 2 readiness), gdpr (GDPR).
- `features` (array, required): The features it needs. Choose from: accounts (Sign-up, login and user accounts), teams_roles (Teams, roles and permissions), payments (Payments and subscriptions), marketplace (Two-sided marketplace…
- `needs_design` (boolean, required): True if they don't have designs yet and need design work. If they haven't said, assume true and mention the assumption.
- `platforms` (string, required): Where it runs: web, mobile (iOS and Android) or web_and_mobile.
- `project_summary` (string): One short sentence on what they want to build, used as the plan's title. Product details only. Never include payment details, ID numbers, passwords, keys or health records.

### `audit_website_speed` (~245 tokens)

Audit a website's speed

Use this when someone wants to know how fast a public web page is, why it's slow, how it does on Core Web Vitals or Lighthouse, or what to fix to speed it up. Runs Google PageSpeed Insights (Lighthouse) and returns performance, accessibility, best-practices and SEO scores, lab measurements, real-user Core Web Vitals when Google has them, and the fixes with the biggest estimated impact. The address is sent to Google, which loads the page. The tool does not edit the target website or submit forms. It only works on public pages, not local sites, pages behind a login or addresses that contain a password or token. An audit takes about 20 to 40 seconds, and the same page's result is reused for up to 12 hours. Don't use it to check whether a site is up, for security scans or for keyword research.

Input parameters:

- `device` (string): Test as a phone (the default, and what Google ranks on) or as a desktop.
- `url` (string, required): The public page to audit, for example example.com or https://example.com/pricing. No passwords, tokens or private links.

### `find_pulore_case_studies` (~156 tokens)

Find related Pulore projects

Use this only when someone asks about Pulore's own work or experience, for example whether Pulore has built something like their idea. Finds published Pulore case studies related to a topic, matching industry, platform, services and technology tags, and returns each project's summary and link, with timeline, team size and results where the case study publishes them. Searches the case-study files bundled with this server; it does not browse or modify external sites. Returns nothing when no project matches. Don't use it to find examples of other companies' products.

Input parameters:

- `query` (string, required): What the project is about, for example 'health app with HIPAA' or 'Shopify storefront'. Topic words only, no personal details.

### `send_project_brief_to_pulore` (~257 tokens)

Send a project brief to Pulore

Use this only when the person has explicitly asked to contact Pulore or send Pulore their project. Sends an external email through Resend to Pulore's fixed inbox, hello@pulore.com, so the team can reply to the person directly. This sends a message outside ChatGPT and cannot be recalled by this tool. First show them the recipient and every field you'll send, and call this only after they approve. The email contains only these fields, never the conversation. A brief identical to one sent in the last day isn't sent again, and each email address can send a few briefs a day.

Input parameters:

- `budget` (string): Their budget range, if they chose to share it.
- `company` (string): Their company or role, if they gave one.
- `email` (string, required): The email address Pulore should reply to.
- `name` (string, required): The person's name.
- `project_brief` (string, required): What they want to build and what they want from Pulore, exactly as they approved it. Product requirements only. Never include payment details, ID numbers, passwords, keys or health records.
- `timeline` (string): When they hope to start or launch, if they said.

### `get_pulore_booking_link` (~165 tokens)

Get a Pulore intro-call booking link

Use this only when someone asks to talk to Pulore or book a call with them. Builds a link locally to Pulore's fixed Cal.com page for a 30-minute intro call, with the person's name, email and a short note filled in when given. This tool makes no request to Cal.com and does not create or reserve a booking. The person opens the link, picks a time and confirms on Cal.com themselves.

Input parameters:

- `email` (string): Their email, to fill in the booking form.
- `name` (string): The person's name, to fill in the booking form.
- `note` (string): A one or two sentence note about the project for the call. Never include payment details, ID numbers, passwords, keys or health records.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-pulore-app-planner/pulore#diagnostics

## Score history

- 2026-11-05: 63
- 2026-11-04: 63

## Common questions

### What is the Pulore App Planner MCP server?

Pulore App Planner is an MCP server listed in the public MCP registry as com.pulore/app-planner. Plan a software project, check website speed, find Pulore case studies, get a booking link. This page covers its hosted endpoint (https://pulore.com/mcp).

### Is the Pulore App Planner MCP server safe to use?

Pulore App Planner scores 63 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 Pulore App Planner MCP server expose?

Pulore App Planner exposes 5 tools: scope_software_project, audit_website_speed, find_pulore_case_studies, send_project_brief_to_pulore, get_pulore_booking_link. Their descriptions and schemas cost roughly 1,439 tokens of context every time the server is loaded.

### Does the Pulore App Planner MCP server require authentication?

No. We connected to Pulore App Planner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Pulore App Planner MCP server still maintained?

Pulore App Planner 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.

## Links

- Remote endpoint: https://pulore.com/mcp
- Website: https://pulore.com/chatgpt
- Changelog RSS feed: https://verifymcp.io/servers/com-pulore-app-planner/pulore.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-pulore-app-planner/pulore.json
- HTML version of this page: https://verifymcp.io/servers/com-pulore-app-planner/pulore