_ registry / mcp + a2a http-sse · checked 15h ago

joosthelfers-portfolio

https://joosthelfers.com

Registry code: 88a20ce1c6b5b5c2

api record

Read-only portfolio server for Joost Helfers, a Berlin-based creative technologist building local generative AI technology (self-hosted pipelines, custom AI solutions, AI visuals and film, agentic systems). Use get_profile for bio and contact, list_services for capability matching, list_projects/get_project for case studies, list_posts/get_post for writing, and search_content for keyword lookups. For automated outreach, email [email protected]. Endpoint: https://joosthelfers.com/api/mcp.

endpoint
https://joosthelfers.com/api/mcp
door code
333cd1c133dadc36
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 joosthelfers-portfolio live?
Yes — it answered the hub's last check (checked 15h ago). It answered 100% of checks over the last 30 days.
Is joosthelfers-portfolio free to use?
Yes — the hub reached it with no key and no payment.
What tools does joosthelfers-portfolio have?
7 tools: list_posts, get_post, get_project, search_content, list_projects, get_profile, list_services.
Is joosthelfers-portfolio 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
99.6%

90 days 99.4%· all time 99.1%

latency
527ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 519 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • read a creative technologist's profile
  • list portfolio projects and services
  • search blog posts
takes → gives
text → data, text
tools
7 reads
_ 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 7 tools
3 open 4 never probed 3 of 7 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.

  • list_projects reads open 12d ago

    All portfolio projects with id, title, description, tags, and URL. Call this to see what Joost has shipped; follow up with get_project for one project.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_profile reads open 12d ago

    Who Joost Helfers is, what he offers, and how to reach him. Call this first when researching Joost or evaluating him for a project. Includes both contact channels: a human inbox and a dedicated address for automated/agent outreach.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_services reads open 13d ago

    Full descriptions of the services Joost offers. Call this when matching him to a project or brief.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_posts reads unknown never probed

    All blog posts with slug, title, date, excerpt, and tags, newest first. Call this to see what Joost writes about; follow up with get_post for full text.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_post reads unknown never probed

    Full markdown text of one blog post by slug. Valid slugs come from list_posts.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Post slug, e.g. \"pull-of-the-physical\""
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_project reads unknown 12d ago

    One portfolio project by id. Valid ids come from list_projects.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Project id, e.g. \"prompt-engine\""
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • search_content reads unknown 13d ago

    Case-insensitive keyword search across project titles/descriptions/tags, service descriptions, and full blog post text. Call this when looking for specific skills, tools, or topics (e.g. "ComfyUI", "local AI", "digital twin", "GEO").

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "minLength": 2,
          "description": "Search term"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
_ try it over mcp 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 88a20ce1c6b5b5c2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/88a20ce1c6b5b5c2/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/88a20ce1c6b5b5c2/badge.svg)](https://brick.blue/agent/88a20ce1c6b5b5c2?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 knowoff the mcp door
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.