Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Nothing to run from here
Pulore App Planner 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.
93/100
tool-list score
5
tools declared
remote
at its publisher
—
calls last 7d
What it does
Plan a software project, check website speed, find Pulore case studies, get a booking link.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http pulore-app-planner-mcp https://pulore.com/mcp
# 2 — ask your agent for something these tools do
# scope_software_project, audit_website_speed, find_pulore_case_studies and 2 more
Pulore App Planner costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PUAll 1 server
pulore1 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. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http pulore-app-planner-mcp https://pulore.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 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.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_summary | string | no | 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. |
| platforms | string | yes | Where it runs: web, mobile (iOS and Android) or web_and_mobile. |
| 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 w |
| 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. |
| compliance | array | no | Compliance it must meet, if any: hipaa (HIPAA (US health data)), soc2 (SOC 2 readiness), gdpr (GDPR). |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The public page to audit, for example example.com or https://example.com/pricing. No passwords, tokens or private links. |
| device | string | no | Test as a phone (the default, and what Google ranks on) or as a desktop. |
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 b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What the project is about, for example 'health app with HIPAA' or 'Shopify storefront'. Topic words only, no personal details. |
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. T
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The person's name. |
| string | yes | The email address Pulore should reply to. | |
| company | string | no | Their company or role, if they gave one. |
| 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 | no | When they hope to start or launch, if they said. |
| budget | string | no | Their budget range, if they chose to share it. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | The person's name, to fill in the booking form. |
| string | no | Their email, to fill in the booking form. | |
| note | string | no | A one or two sentence note about the project for the call. Never include payment details, ID numbers, passwords, keys or health records. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Pulore App Planner or to call it, 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: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 5 Nov 2026
Graded from the tools this server lists, not from its source code.
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 score93
Findings0 threat · 2 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest3a055682123f237ade3e9ce75a76d3007651ddd10e5d0c7064226a75387eb93d
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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 |
|---|---|---|
| scope_software_project | no tags | |
| audit_website_speed | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| find_pulore_case_studies | no tags | |
| send_project_brief_to_pulore | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| get_pulore_booking_link | no tags |
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.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest3a055682123f237a
Scanned2026-11-05
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Pulore App Planner can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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 a signed-in account that does not publish it, and nothing else.