made.show
REMOTE · MADE.SHOW
Designer portfolios on made.show. Find people, read their work, request work samples.
Available components
Last scanned (20 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1729 tokens (~216/item across 8 items; 8 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 Management37
- Stability observed for 11 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- “search_people” added an optional parameter “discipline” cosmetic
- “match_criteria” reworded the description of “criteria” cosmetic
- “publish_tailored_view” reworded the description of “title” cosmetic
- “request_work_sample” reworded the description of “context” cosmetic
- “search_people” reworded the description of “query” cosmetic
5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 12 Nov 26 +3
- Tool coverage: 52% → 100% ▲ functional
- “get_work_sample” reworded the description of “token” cosmetic
- “match_criteria” reworded the description of “criteria” cosmetic
- “publish_tailored_view” reworded the description of “company” cosmetic
- “publish_tailored_view” reworded the description of “sections” cosmetic
- “request_work_sample” reworded the description of “company” cosmetic
- “request_work_sample” reworded the description of “contactEmail” cosmetic
- “request_work_sample” reworded the description of “contactName” cosmetic
- “request_work_sample” reworded the description of “deadline” cosmetic
- “request_work_sample” reworded the description of “title” cosmetic
- “search_people” reworded the description of “availability” cosmetic
- “search_people” reworded the description of “limit” cosmetic
- “search_people” reworded the description of “query” cosmetic
- “search_people” reworded the description of “remoteOnly” cosmetic
- 11 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 10 Nov 26 72
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 21 Nov 2026 · Probed https://made.show/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=made.show | CN=YE1,O=Let's Encrypt,C=US | 10 Nov 2026 | 8 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 63b633ea5bd7d0800b6220e2d6aff4ab40e |
| SANs: *.made.show, made.show | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 made.show. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| show. | DS published | 31030 | 8 | Verified |
| made.show. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://images.unsplash.com https://*.public.blob.vercel-storage.com; media-src 'self' blob: https://*.public.blob.vercel-storage.com; font-src 'self'; connect-src 'self' https://vercel.com https://*.blob.vercel-storage.com; form-action 'self' https://checkout.stripe.com https://billing.stripe.com; frame-ancestors 'none'; object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://made.show/api/mcp | Verified | 200 | |
| http (plaintext) | http://made.show/api/mcp | HTTPS enforced | 301 | https://made.show/api/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 →
get_portfolio Get full portfolio ~91
The candidate's complete structured portfolio: experience, education, projects (problem / my part / approach / outcome / metrics / media), writing, references, languages and awards, plus computed facts like total experience and per-skill evidence. Pass `criteria` to also get an evidence map.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | Optional requirements to map against the portfolio |
| handle | string | – | Handle or full name |
No output schema declared.
No examples provided.
get_profile Get profile ~88
Start here whenever someone asks who a candidate is. Returns a ready-to-present introduction card (name, headline, current role, experience, strongest evidence, selected work, a quote) plus the underlying data. Present the card, then add one short paragraph relevant to the user's question.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | – | The person's made.show handle ("par") or full name ("Pär Fagerberg") |
No output schema declared.
No examples provided.
get_project Get project ~40
One project in full, by slug or id.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | – | Handle or full name |
| project | string | yes | Project slug or id |
No output schema declared.
No examples provided.
get_work_sample Get work sample ~69
Status of a brief sent with request_work_sample (requested, accepted, declined or submitted), and the candidate's work once submitted: summary, approach, rationale, media and links. Use when the user asks whether the candidate has replied.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The token request_work_sample returned |
No output schema declared.
No examples provided.
match_criteria Match criteria to evidence ~114
Map your requirements to concrete evidence in the portfolio. Returns, per criterion, the matching projects/roles/education/writing (with ids you can use in publish_tailored_view), per-skill evidence, and gaps where no written evidence exists. Lexical and conservative: use your own judgment on top.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | yes | Requirements to check, one per item, e.g. "Has shipped a design system" or "Has run Postgres in production" |
| handle | string | – | Handle or full name |
No output schema declared.
No examples provided.
publish_tailored_view Publish a tailored portfolio ~169
Compose a shareable portfolio page for your criteria, rendered in the candidate's own template. Each section is a criterion with the blocks (by kind + id from get_portfolio / match_criteria) that evidence it. You may add a short `note` per item explaining relevance; notes are labelled as AI-written. You cannot add new content: unknown ids are rejected. The candidate is notified.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | The hiring company, shown on the page |
| gaps | array | – | Criteria with no evidence. Shown honestly on the page. |
| handle | string | – | Handle or full name |
| sections | array | yes | One section per criterion |
| title | string | yes | e.g. "Senior Frontend Engineer, Design Systems" or "Senior Product Designer" |
No output schema declared.
No examples provided.
request_work_sample Request a work sample ~236
Send a candidate a brief for a real work sample: what you need, the context and when you need it. Before sending, ask the user for anything missing (what they need, their company, their name and email) and show them the brief, since the candidate gets notified. The candidate accepts or declines in made.show and replies with the work and their reasoning. Returns a token: keep it in the conversation and pass it to get_work_sample to check the status or read the work.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | The requesting company |
| contactEmail | string | yes | Email the candidate's reply goes to |
| contactName | string | yes | Name of the person sending the brief |
| context | string | – | Links or background, e.g. your docs, design system or repo |
| deadline | string | – | When you need it, as YYYY-MM-DD |
| description | string | yes | The brief: what you want made, the ambition, constraints |
| handle | string | – | Handle or full name |
| title | string | yes | Short name for the brief, e.g. "Onboarding flow redesign" |
No output schema declared.
No examples provided.
search_people Search people ~215
Find people across every public portfolio on made.show by free text (name with or without accents, headline, bio, role titles, organizations, skills), skills, location or availability. Returns short summaries with one suggested follow-up prompt each; call get_profile or get_portfolio for depth.
| Name | Type | Req | Description |
|---|---|---|---|
| availability | string | – | open: looking now. passive: open to the right offer. not_looking: not looking |
| discipline | string | – | What they do: designers, developers (engineering), product managers or writers. Self-chosen, so also check their roles. |
| limit | integer | – | How many people to return, 1 to 25 |
| location | string | – | City or country |
| query | string | – | Free text: a name, role, company, skill or anything in a bio, e.g. "design systems lead fintech" or "backend go payments" |
| remoteOnly | boolean | – | Only people open to remote work |
| skills | array | – | All listed skills must be evidenced |
No output schema declared.
No examples provided.
How do I install the made.show MCP server?
made.show is a hosted endpoint at https://made.show/api/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 · made.show
claude mcp add --transport http show-made-portfolios 'https://made.show/api/mcp'
What is the made.show MCP server?
made.show is an MCP server listed in the public MCP registry as show.made/portfolios. Designer portfolios on made.show. Find people, read their work, request work samples. This page covers its hosted endpoint (https://made.show/api/mcp).
Is the made.show MCP server safe to use?
made.show scores 79 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 made.show MCP server expose?
made.show exposes 8 tools: search_people, get_profile, get_portfolio, get_project, match_criteria, and 3 more. Their descriptions and schemas cost roughly 1,022 tokens of context every time the server is loaded.
Does the made.show MCP server require authentication?
No. We connected to made.show without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the made.show MCP server still maintained?
made.show 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 made.show MCP server?
VerifyMCP ran 13 checks on made.show, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.