# made.show (remote · made.show)

Designer portfolios on made.show. Find people, read their work, request work samples.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `made.show`: 79/100 (this document), [markdown](https://verifymcp.io/servers/show-made-portfolios/api-mcp.md), [page](https://verifymcp.io/servers/show-made-portfolios/api-mcp)

## Channel facts

- Endpoint: `https://made.show/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http show-made-portfolios 'https://made.show/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "show-made-portfolios": {
      "url": "https://made.show/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "show-made-portfolios": {
      "type": "http",
      "url": "https://made.show/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.show-made-portfolios]
url = "https://made.show/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "show-made-portfolios": {
      "type": "remote",
      "url": "https://made.show/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add show-made-portfolios --url 'https://made.show/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  show-made-portfolios:
    url: "https://made.show/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "show-made-portfolios": {
      "Transport": "http",
      "Url": "https://made.show/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add show-made-portfolios -t streamable-http -u 'https://made.show/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "show-made-portfolios": {
      "type": "http",
      "url": "https://made.show/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 79, +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.

### 2026-11-19 (score 78, +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.

### 2026-11-17 (score 77, +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.

### 2026-11-14 (score 76, +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.

### 2026-11-13 (score 75, 0)

- [cosmetic] “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”

### 2026-11-12 (score 75, +3)

- [functional improvement] Tool coverage: 52% → 100%
- [cosmetic] “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”

### 2026-11-11 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-10 (score 72)

First indexed and scored.

## MCP tools (8)

### `search_people` (~215 tokens)

Search people

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.

Input parameters:

- `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

### `get_profile` (~88 tokens)

Get profile

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.

Input parameters:

- `handle` (string): The person's made.show handle ("par") or full name ("Pär Fagerberg")

### `get_portfolio` (~91 tokens)

Get full portfolio

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.

Input parameters:

- `criteria` (array): Optional requirements to map against the portfolio
- `handle` (string): Handle or full name

### `get_project` (~40 tokens)

Get project

One project in full, by slug or id.

Input parameters:

- `handle` (string): Handle or full name
- `project` (string, required): Project slug or id

### `match_criteria` (~114 tokens)

Match criteria to evidence

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.

Input parameters:

- `criteria` (array, required): 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

### `publish_tailored_view` (~169 tokens)

Publish a tailored portfolio

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.

Input parameters:

- `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, required): One section per criterion
- `title` (string, required): e.g. "Senior Frontend Engineer, Design Systems" or "Senior Product Designer"

### `request_work_sample` (~236 tokens)

Request a work sample

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.

Input parameters:

- `company` (string, required): The requesting company
- `contactEmail` (string, required): Email the candidate's reply goes to
- `contactName` (string, required): 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, required): The brief: what you want made, the ambition, constraints
- `handle` (string): Handle or full name
- `title` (string, required): Short name for the brief, e.g. "Onboarding flow redesign"

### `get_work_sample` (~69 tokens)

Get work sample

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.

Input parameters:

- `token` (string, required): The token request_work_sample returned

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/show-made-portfolios/api-mcp#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 76
- 2026-11-13: 75
- 2026-11-12: 75
- 2026-11-11: 72
- 2026-11-10: 72

## Common questions

### 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.

## Links

- Remote endpoint: https://made.show/api/mcp
- Website: https://made.show/employers
- Changelog RSS feed: https://verifymcp.io/servers/show-made-portfolios/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/show-made-portfolios/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/show-made-portfolios/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/show-made-portfolios/api-mcp
