Pulore App Planner
REMOTE · PULORE.COM
Plan a software project, check website speed, find Pulore case studies, get a booking link.
Available components
Last scanned (5 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_project_brief_to_pulore). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 4 Nov 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://pulore.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pulore.com | CN=YE2,O=Let's Encrypt,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 63850990e687f824fc9d997aadd0e536020 |
| SANs: *.pulore.com, pulore.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pulore.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| pulore.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pulore.com/mcp | Verified | 200 | |
| http (plaintext) | http://pulore.com/mcp | HTTPS enforced | 308 | https://pulore.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_website_speed Audit a website's speed ~245
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.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | Test as a phone (the default, and what Google ranks on) or as a desktop. |
| url | string | yes | The public page to audit, for example example.com or https://example.com/pricing. No passwords, tokens or private links. |
No output schema declared.
No examples provided.
find_pulore_case_studies Find related Pulore projects ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What the project is about, for example 'health app with HIPAA' or 'Shopify storefront'. Topic words only, no personal details. |
No output schema declared.
No examples provided.
get_pulore_booking_link Get a Pulore intro-call booking link ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
scope_software_project Scope a software project ~616
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.
| Name | Type | Req | Description |
|---|---|---|---|
| compliance | array | – | Compliance it must meet, if any: hipaa (HIPAA (US health data)), soc2 (SOC 2 readiness), gdpr (GDPR). |
| features | array | yes | 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 | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
send_project_brief_to_pulore Send a project brief to Pulore ~257
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.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string | – | Their budget range, if they chose to share it. |
| company | string | – | Their company or role, if they gave one. |
| string | yes | The email address Pulore should reply to. | |
| name | string | yes | The person's name. |
| project_brief | string | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · pulore.com
claude mcp add --transport http com-pulore-app-planner 'https://pulore.com/mcp'
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.