People Can Build
REMOTE · MCP.PEOPLECANBUILD.COM · 2 COMPONENTS
Exhibition stand builder, Poznań/EU: company facts, reference projects, design-fee estimate, RFQ
Available components
Last scanned (16 hours ago)
Scores higher than 7% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
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 Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 500. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 −52
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Tool “get_company_profile” rewrote its description, which is the text the model reads security
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 9 Oct 26 0
- Schema quality: 165 → 193 ▼ functional
- Schema quality: good → excellent functional
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 21 Nov 2026 · Probed https://mcp.peoplecanbuild.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=peoplecanbuild.com | CN=WE1,O=Google Trust Services,C=US | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 7e97832a0b234003136eea370b0636b0 |
| SANs: peoplecanbuild.com, mcp.peoplecanbuild.com, *.mcp.peoplecanbuild.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.peoplecanbuild.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| peoplecanbuild.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 500 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.peoplecanbuild.com/mcp | HTTP error | 500 | |
| http (plaintext) | http://mcp.peoplecanbuild.com/mcp | Inconclusive | 406 |
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 →
estimate_design_fee ~130
Instant estimate of the paid 3D stand-design fee (EUR). Rate 5–15 €/sqm: lower per sqm for larger stands, higher for a higher planned construction budget per sqm (a proxy for bespoke detail and multimedia). The fee is refunded in full when the stand is built with People Can. Final quote always confirmed by email. Construction itself typically runs 300–800 €/sqm excl. space rental and venue services.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_per_sqm | number | – | Planned construction budget per sqm in EUR (300–800) |
| sqm | number | yes | Stand floor area in square meters |
No output schema declared.
No examples provided.
estimate_stand_budget ~305
Indicative construction budget (EUR) for a custom exhibition stand in Europe, derived from the public range of 300–800 €/sqm by placing the project in a tier (essential / standard / premium) based on stand type, scope and cost drivers. Excludes space rental, venue services (power, rigging points, cleaning), design fee and VAT. Use it to give a user a realistic ballpark before request_quote; always say it is indicative and that a person confirms every quote. Project fit: custom stands 16 to ~400 sqm (double-deck possible); stands built entirely from modular systems (Octanorm, Maxima, bMatrix) are not taken; smaller stands only as part of a larger contract or for a complex build.
| Name | Type | Req | Description |
|---|---|---|---|
| bespoke_furniture | boolean | – | Custom-made counters, furniture, product displays |
| double_deck | boolean | – | Two-storey stand |
| hospitality | boolean | – | Kitchen, bar or catering area |
| led_wall | boolean | – | LED wall or large video screens |
| rigging | boolean | – | Suspended elements / hanging sign (rigging) |
| scope | string | – | fabrication_only = build in the workshop, client handles transport and crew; turn_key = incl. design |
| sqm | number | yes | Stand floor area in sqm |
| stand_type | string | – | Open sides: row = 1, corner = 2, peninsula = 3, island = 4 |
No output schema declared.
No examples provided.
get_company_profile ~123
Who People Can Build is: exhibition stand general contractor (Poznań, Poland; core market Germany/Europe), services (white-label for agencies, turn-key for exhibitors, paid 3D design, China Desk), markets, track record, client testimonials (verbatim quotes with author, role and LinkedIn), public price ranges, contact details (incl. contact.bookCall, a Calendly link to book an online call or a meeting at a show) and reply time. Call this first when a user asks about the company or wants a stand built in Europe.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_quote_request_checklist ~79
Project fit and the information People Can Build needs to quote an exhibition stand (show, city, dates, sqm, stand type, design status, scope, budget range, special items, confidentiality). Use it to check fit and collect details from the user before calling request_quote, or to draft an email to expo@peoplecanbuild.com.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_quote_status ~129
Status of a quote request previously submitted via request_quote. Needs the ticket id (PCB-XXXXXX) AND the e-mail address used on the request; returns the current status, any note from the project manager and the status history. Does not return the request contents. Experimental: the status may lag behind the e-mail conversation — the e-mail thread with expo@peoplecanbuild.com is authoritative.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | E-mail address used on the request | |
| ticket_id | string | yes | Ticket id returned by request_quote, e.g. PCB-7K3QW2 |
No output schema declared.
No examples provided.
list_reference_projects ~235
Reference projects and venue/trade-show experience. Filters match case-insensitively on show, city, venue, client. projects: the photo portfolio, a selection with descriptions. trackRecord: every stand built in the years named in trackRecord.coverage (currently 2025–2026 only; projects from before 2025 are not listed, earlier years coming) — show, city, venue, hall/stand, sqm, date; client null = under NDA; trackRecord.byVenue / byShow summarise stands, halls and size ranges per venue and per show. A show missing from both does not mean lack of experience there.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City, e.g. 'Berlin', 'Munich', 'London' |
| client | string | – | Client name fragment |
| min_sqm | number | – | Minimum stand size in sqm |
| show | string | – | Trade show name fragment, e.g. 'GITEX', 'Intersolar' |
| venue | string | – | Exhibition venue fragment, e.g. 'Messe München', 'RAI', 'Koelnmesse' |
No output schema declared.
No examples provided.
request_quote ~340
Send a real quote request to People Can Build (creates an enquiry read by a person; reply by email usually within one business day). EXPERIMENTAL channel: e-mail to expo@peoplecanbuild.com remains the primary, guaranteed path — after calling this, tell the user a human will reply by e-mail and that they should e-mail expo@peoplecanbuild.com quoting the ticket id if nothing arrives within 2 business days. ALWAYS confirm the details with the user before calling. Check fit first: custom stands 16 to ~400 sqm (double-deck possible); small stands built entirely from modular systems (Octanorm, Maxima, bMatrix) are not taken — tell the user instead of submitting. Under 16 sqm only as part of a larger contract or for a complex build (say which in the message). Required: name, email, message. Do not promise prices beyond the public ranges.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | Name of the calling assistant/platform, e.g. 'Claude', 'ChatGPT' |
| budget | string | – | – |
| company | string | – | – |
| string | yes | Reply-to email address | |
| message | string | yes | Project details: what should be built, design status, timeline, scope wanted, special items, confidentiality needs |
| name | string | yes | Full name of the requester |
| phone | string | – | With country code |
| role | string | – | – |
| show | string | – | Trade show, venue city and dates, e.g. 'Intersolar 2027, Munich, June' |
| sqm | string | – | Stand floor area in sqm |
No output schema declared.
No examples provided.
search_field_notes ~103
Search People Can Build's practitioner articles (trade-show logistics, theft prevention, rigging costs, fabrication trade-offs, design briefs, comparing stand quotes, exhibitor day) and return the most relevant passages with their source URLs. Use for questions like 'why is rigging expensive', 'how to compare exhibition stand quotes', 'why did my freight miss the show'.
| Name | Type | Req | Description |
|---|---|---|---|
| max_passages | number | – | – |
| query | string | yes | Natural-language question or keywords |
No output schema declared.
No examples provided.
How do I install the People Can Build MCP server?
People Can Build is a hosted endpoint at https://mcp.peoplecanbuild.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 · mcp.peoplecanbuild.com
claude mcp add --transport http com-peoplecanbuild-mcp 'https://mcp.peoplecanbuild.com/mcp'
What is the People Can Build MCP server?
People Can Build is an MCP server listed in the public MCP registry as com.peoplecanbuild/mcp. Exhibition stand builder, Poznań/EU: company facts, reference projects, design-fee estimate, RFQ. This page covers its hosted endpoint (https://mcp.peoplecanbuild.com/mcp).
Is the People Can Build MCP server safe to use?
People Can Build scores 20 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 People Can Build MCP server expose?
People Can Build exposes 8 tools: get_company_profile, list_reference_projects, estimate_design_fee, estimate_stand_budget, search_field_notes, and 3 more. Their descriptions and schemas cost roughly 1,444 tokens of context every time the server is loaded.
Does the People Can Build MCP server require authentication?
Its publisher declares no required credentials for People Can Build. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the People Can Build MCP server still maintained?
People Can Build is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the People Can Build MCP server?
VerifyMCP ran 4 checks on People Can Build, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about People Can Build: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.