Interact with Microsoft 365 and Office services through the Microsoft Graph API.
HDPhotoHub MCP by usefulapi 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.
What it does
Manage HDPhotoHub sites, clients, orders and media for real estate photography.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http hdphotohub-mcp-by-usefulapi https://hdphotohub.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# hdphotohub_get_brand, hdphotohub_list_users, hdphotohub_get_user and 17 more
HDPhotoHub MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 hdphotohub-mcp-by-usefulapi https://hdphotohub.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
20 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.
Get the business (brand) the API key belongs to: id and name. API: GET /brand.
No parameter schema on file.
List clients and team members, optionally filtered by email or name. API: GET /users.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | no | Filter by email address. | |
| name | string | no | Filter by name. |
Get one user by id or email. Pass uid or email. API: GET /user.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uid | integer | no | User id (from hdphotohub_list_users). |
| string | no | User email address. |
List the transactions of a user, optionally within a date range. API: GET /user/transactions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uid | integer | yes | User id. |
| datefrom | string | no | Include transactions on and after this date (yyyy-mm-dd). |
| dateto | string | no | Include transactions on and before this date (yyyy-mm-dd). |
List property sites, filtered by user id, user email or an address search string. API: GET /sites.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uid | integer | no | Only sites of this user id. |
| string | no | Only sites of the user with this email. | |
| address | string | no | Address search string. |
Get one property site with its status, purchase state, users and all media items (download URL, type, order). API: GET /site.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sid | integer | yes | Site id (from hdphotohub_list_sites). |
Get one media item (photo, video, floor plan) by id. API: GET /media.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mid | integer | yes | Media id (from hdphotohub_get_site). |
List orders, optionally for one site or one user. Orders carry totals, balance due, tasks and payments. API: GET /orders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sid | integer | no | Only orders of this site id. |
| uid | integer | no | Only orders of this user id. |
Get one order by id with tasks, taxes, payments and invoice URL. API: GET /order.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| oid | integer | yes | Order id (from hdphotohub_list_orders). |
List groups (brokerages and teams), optionally filtered by name. API: GET /groups.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Filter by group name. |
Get one group by id. API: GET /group.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| gid | integer | yes | Group id (from hdphotohub_list_groups). |
List the configured webhooks. API: GET /webhooks.
No parameter schema on file.
Get one webhook by id. API: GET /webhook.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wid | integer | yes | Webhook id (from hdphotohub_list_webhooks). |
List the available webhook event types and payload options. API: GET /webhook/events.
No parameter schema on file.
WRITE: create a new property site for a user. Not idempotent: a repeat call creates a second site. API: POST /site.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uid | integer | yes | Owner user id. |
| uid2 | integer | no | Co-user id. |
| address | string | no | Street address. |
| address2 | string | no | Address line 2 (unit, suite). |
| city | string | no | — |
| state | string | no | — |
| zip | string | no | — |
| banner | string | no | Banner text shown on the property site (for example 'Just Listed'). |
| bannerexpiration | string | no | Banner expiration date. |
| mls | string | no | MLS number. |
| price | string | no | List price. |
| beds | string | no | — |
| baths | string | no | — |
| garage | string | no | — |
| sqft | string | no | Living area in square feet. |
| sqm | string | no | Living area in square meters. |
| yearbuilt | string | no | — |
| lotsize | string | no | — |
| description | string | no | Property description. |
WRITE: update fields of an existing property site. Only the fields you pass change. API: PUT /site.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sid | integer | yes | Site id. |
| uid | integer | no | — |
| uid2 | integer | no | — |
| address | string | no | Street address. |
| address2 | string | no | Address line 2 (unit, suite). |
| city | string | no | — |
| state | string | no | — |
| zip | string | no | — |
| banner | string | no | Banner text shown on the property site (for example 'Just Listed'). |
| bannerexpiration | string | no | Banner expiration date. |
| mls | string | no | MLS number. |
| price | string | no | List price. |
| beds | string | no | — |
| baths | string | no | — |
| garage | string | no | — |
| sqft | string | no | Living area in square feet. |
| sqm | string | no | Living area in square meters. |
| yearbuilt | string | no | — |
| lotsize | string | no | — |
| description | string | no | Property description. |
WRITE: set a site to active, inactive or archived. This does not purchase the site. API: PUT /site/status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sid | integer | yes | Site id. |
| status | string | yes | — |
WRITE: set the sort order of the media of a site. Pass media ids in the wanted order. API: PUT /site/mediaorder.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sid | integer | yes | Site id. |
| mid | array | yes | Media ids in the wanted order. |
WRITE: update name, description, type, visibility, highlight or branding of one media item. API: PUT /media.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mid | integer | yes | Media id. |
| name | string | no | — |
| description | string | no | — |
| type | string | no | — |
| hidden | boolean | no | — |
| highlight | boolean | no | — |
| branding | string | no | — |
WRITE: create a user (no uid) or update one (uid or email of an existing user). API: PUT /user.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uid | integer | no | Existing user id to update. |
| string | no | — | |
| name | string | no | — |
| firstname | string | no | — |
| lastname | string | no | — |
| title | string | no | — |
| phone | string | no | — |
| website | string | no | — |
| status | string | no | — |
| type | string | no | — |
| gid | integer | no | Group id. |
- 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 HDPhotoHub MCP by usefulapi or to call it, at any volume.
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.
| 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 |
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.
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 |
|---|---|---|
| hdphotohub_get_brand | no tags | |
| hdphotohub_list_users | no tags | |
| hdphotohub_get_user | no tags | |
| hdphotohub_list_user_transactions | no tags | |
| hdphotohub_list_sites | no tags | |
| hdphotohub_get_site | no tags | |
| hdphotohub_get_media | no tags | |
| hdphotohub_list_orders | no tags | |
| hdphotohub_get_order | no tags | |
| hdphotohub_list_groups | no tags | |
| hdphotohub_get_group | no tags | |
| hdphotohub_list_webhooks | no tags | |
| hdphotohub_get_webhook | external-sink | external-sink: keyword "webhook" |
| hdphotohub_list_webhook_events | external-sink | external-sink: keyword "webhook" |
| hdphotohub_create_site | state-write | state-write: declares destructiveHint: true |
| hdphotohub_update_site | no tags | |
| hdphotohub_set_site_status | no tags | |
| hdphotohub_set_site_media_order | no tags | |
| hdphotohub_update_media | no tags | |
| hdphotohub_upsert_user | 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.
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
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.5.3.
No release note was published with this version.
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.
Any signed-in account that does not publish HDPhotoHub MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.