_ registry / mcp http-sse · checked 6h ago

made.show

https://made.show

Registry code: 0f427996a5391e7a

api record

made.show hosts structured portfolios of people who want to be hired.

Use it to understand a candidate's background, experience, projects and evidence of skills, in whatever shape you need.

endpoint
https://made.show/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is made.show live?
Yes — it answered the hub's last check (checked 6h ago). It answered 100% of checks over the last 30 days.
Is made.show free to use?
Yes — the hub reached it with no key and no payment.
What tools does made.show have?
8 tools: get_profile, request_work_sample, get_work_sample, get_portfolio, get_project, match_criteria, publish_tailored_view, search_people.
Is made.show safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
225ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
1 open 7 never probed 1 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_people open 6h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 25,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 200
    },
    "skills": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 60
      },
      "maxItems": 10,
      "description": "All listed skills must be evidenced"
    },
    "location": {
      "type": "string",
      "maxLength": 80,
      "description": "City or country"
    },
    "remoteOnly": {
      "type": "boolean"
    },
    "availability": {
      "enum": [
        "open",
        "passive",
        "not_looking"
      ],
      "type": "string"
    }
  }
}
    arguments 41 lines
  • get_profile unknown 6h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "handle": {
      "type": "string",
      "maxLength": 80,
      "description": "The person's made.show handle (\"par\") or full name (\"Pär Fagerberg\")"
    }
  }
}
    arguments 11 lines
  • request_work_sample unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "company",
    "contactName",
    "contactEmail",
    "title",
    "description"
  ],
  "properties": {
    "title": {
      "type": "string",
      "maxLength": 120,
      "minLength": 3
    },
    "handle": {
      "type": "string",
      "maxLength": 80,
      "description": "Handle or full name"
    },
    "company": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
    },
    "context": {
      "type": "string",
      "maxLength": 3000,
      "description": "Links or background, e.g. your design system docs"
    },
    "deadline": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "contactName": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
    },
    "description": {
      "type": "string",
      "maxLength": 3000,
      "minLength": 20,
      "description": "The brief: what you want made, the ambition, constraints"
    },
    "contactEmail": {
      "type": "string",
      "format": "email",
      "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      "maxLength": 120
    }
  }
}
    arguments 54 lines
  • get_work_sample unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "token"
  ],
  "properties": {
    "token": {
      "type": "string",
      "maxLength": 64,
      "minLength": 10
    }
  }
}
    arguments 14 lines
  • get_portfolio unknown 6h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "handle": {
      "type": "string",
      "maxLength": 80,
      "description": "Handle or full name"
    },
    "criteria": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 200
      },
      "maxItems": 15,
      "description": "Optional requirements to map against the portfolio"
    }
  }
}
    arguments 20 lines
  • get_project unknown never probed

    One project in full, by slug or id.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "project"
  ],
  "properties": {
    "handle": {
      "type": "string",
      "maxLength": 80,
      "description": "Handle or full name"
    },
    "project": {
      "type": "string",
      "maxLength": 80,
      "description": "Project slug or id"
    }
  }
}
    arguments 19 lines
  • match_criteria unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "criteria"
  ],
  "properties": {
    "handle": {
      "type": "string",
      "maxLength": 80,
      "description": "Handle or full name"
    },
    "criteria": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 200,
        "minLength": 2
      },
      "maxItems": 15,
      "minItems": 1
    }
  }
}
    arguments 24 lines
  • publish_tailored_view unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "title",
    "sections"
  ],
  "properties": {
    "gaps": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 200
      },
      "default": [],
      "maxItems": 12,
      "description": "Criteria with no evidence. Shown honestly on the page."
    },
    "title": {
      "type": "string",
      "maxLength": 100,
      "minLength": 3,
      "description": "e.g. \"Senior Product Designer — Design Systems\""
    },
    "handle": {
      "type": "string",
      "maxLength": 80,
      "description": "Handle or full name"
    },
    "company": {
      "type": "string",
      "maxLength": 80
    },
    "sections": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "criterion",
          "items"
        ],
        "properties": {
          "items": {
            "type": "array",
            "items": {
              "type": "object",
              "required": [
                "kind",
                "id"
              ],
              "properties": {
                "id": {
                  "type": "string",
                  "format": "uuid",
                  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
                },
                "kind": {
                  "enum": [
                    "project",
                    "role",
                    "education",
                    "writing",
                    "reference"
                  ],
                  "type": "string"
                },
                "note": {
                  "type": "string",
                  "maxLength": 240
                }
              }
            },
            "maxItems": 8
          },
          "criterion": {
            "type": "string",
            "maxLength": 200,
            "minLength": 2
          }
        }
      },
      "maxItems": 12,
      "minItems": 1
    }
  }
}
    arguments 86 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0f427996a5391e7a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0f427996a5391e7a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0f427996a5391e7a/badge.svg)](https://brick.blue/agent/0f427996a5391e7a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.