_ registry / mcp http-sse · checked 52m ago

Pieter-Jan Scheir

listed under this name in a public catalogue; the server gives only its address, scheir.eu

https://scheir.eu

Registry code: 3e95bd7015d5e1d9

api record

Read-only information about Pieter-Jan Scheir, an AI-first full-stack developer (TypeScript, Next.js) with a legal-tech background, based in Belgium: profile, projects, experience, skills and how to contact him. Every tool takes an optional locale (default en).

endpoint
https://scheir.eu/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 Pieter-Jan Scheir live?
Yes — it answered the hub's last check (checked 52m ago). It answered 100% of checks over the last 30 days.
Is Pieter-Jan Scheir free to use?
Yes — the hub reached it with no key and no payment.
What tools does Pieter-Jan Scheir have?
6 tools: list_projects, get_project, list_experience, get_profile, get_skills, how_to_contact.
Is Pieter-Jan Scheir 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
186ms

last good check

priced tools
0

of 6 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 6 tools
3 open 3 never probed 3 of 6 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.

  • get_profile open 52m ago

    Who Pieter-Jan Scheir is: positioning, about text, current roles, links and email.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "locale": {
      "enum": [
        "en",
        "nl",
        "fr",
        "de",
        "es",
        "it",
        "pt",
        "pl",
        "sv",
        "tr",
        "el",
        "ja",
        "ko",
        "zh",
        "da",
        "nb",
        "fi",
        "cs",
        "ro",
        "hu",
        "sk",
        "uk",
        "hr",
        "sl",
        "bg",
        "ar",
        "et",
        "lv",
        "lt",
        "zh-Hant",
        "vi",
        "id",
        "th",
        "my",
        "pt-BR",
        "ca"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of the answer (default en)"
    }
  }
}
    arguments 49 lines
  • get_skills open 52m ago

    His skill areas with certifications, and the languages and tools he works with.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "locale": {
      "enum": [
        "en",
        "nl",
        "fr",
        "de",
        "es",
        "it",
        "pt",
        "pl",
        "sv",
        "tr",
        "el",
        "ja",
        "ko",
        "zh",
        "da",
        "nb",
        "fi",
        "cs",
        "ro",
        "hu",
        "sk",
        "uk",
        "hr",
        "sl",
        "bg",
        "ar",
        "et",
        "lv",
        "lt",
        "zh-Hant",
        "vi",
        "id",
        "th",
        "my",
        "pt-BR",
        "ca"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of the answer (default en)"
    }
  }
}
    arguments 49 lines
  • how_to_contact open 52m ago

    How to reach him for development work: email, calendar link and contact page.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "locale": {
      "enum": [
        "en",
        "nl",
        "fr",
        "de",
        "es",
        "it",
        "pt",
        "pl",
        "sv",
        "tr",
        "el",
        "ja",
        "ko",
        "zh",
        "da",
        "nb",
        "fi",
        "cs",
        "ro",
        "hu",
        "sk",
        "uk",
        "hr",
        "sl",
        "bg",
        "ar",
        "et",
        "lv",
        "lt",
        "zh-Hant",
        "vi",
        "id",
        "th",
        "my",
        "pt-BR",
        "ca"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of the answer (default en)"
    }
  }
}
    arguments 49 lines
  • list_projects unknown never probed

    His projects in the order of the projects page (those with a year newest first, then alphabetical), with stack, status and a link to each project page. Filter by technology, category or featured.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "locale": {
      "enum": [
        "en",
        "nl",
        "fr",
        "de",
        "es",
        "it",
        "pt",
        "pl",
        "sv",
        "tr",
        "el",
        "ja",
        "ko",
        "zh",
        "da",
        "nb",
        "fi",
        "cs",
        "ro",
        "hu",
        "sk",
        "uk",
        "hr",
        "sl",
        "bg",
        "ar",
        "et",
        "lv",
        "lt",
        "zh-Hant",
        "vi",
        "id",
        "th",
        "my",
        "pt-BR",
        "ca"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of the answer (default en)"
    },
    "category": {
      "enum": [
        "legal-public",
        "client",
        "employer",
        "personal"
      ],
      "type": "string"
    },
    "featured": {
      "type": "boolean"
    },
    "technology": {
      "type": "string",
      "description": "Only projects using this technology, e.g. \"Next.js\""
    }
  }
}
    arguments 65 lines
  • get_project unknown never probed

    Everything about one project, by its id.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "enum": [
        "gdw-scheir",
        "vp-service",
        "courtbudget",
        "vgprovl",
        "rpv-calculator",
        "vgprovl-jobs",
        "vgprovl-event-center",
        "dapronext",
        "windows-keyboard-shortcuts",
        "verbos",
        "birth-date-analyzer",
        "secure-password-generator",
        "administration-indexation-calculator",
        "packing-list-manager",
        "q-treecare",
        "gogi-korean-bbq",
        "magical-code-formatter",
        "fietsen-roman",
        "mario-public-site",
        "ghent-parking",
        "tailwind-css-converter",
        "lorem-ipsum-generator",
        "justtools",
        "bewindvoeringen-be",
        "legalsquare",
        "spar-online",
        "gronddepot",
        "egovflow",
        "scan-search-online",
        "expertcenter",
        "marija-s-birthday-party",
        "vgprovl-tools",
        "ksa-aalter-generations-party",
        "portfolio",
        "wedding-management-application",
        "travel-allowance-calculator",
        "vat-calculator",
        "mmti",
        "residence-chambord-escurial",
        "tour-mandalay"
      ],
      "type": "string",
      "description": "A project id from list_projects"
    },
    "locale": {
      "enum": [
        "en",
        "nl",
        "fr",
        "de",
        "es",
        "it",
        "pt",
        "pl",
        "sv",
        "tr",
        "el",
        "ja",
        "ko",
        "zh",
        "da",
        "nb",
        "fi",
        "cs",
        "ro",
        "hu",
        "sk",
        "uk",
        "hr",
        "sl",
        "bg",
        "ar",
        "et",
        "lv",
        "lt",
        "zh-Hant",
        "vi",
        "id",
        "th",
        "my",
        "pt-BR",
        "ca"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of the answer (default en)"
    }
  }
}
    arguments 98 lines
  • list_experience unknown never probed

    His roles, newest first: company, period, description, stack and page.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "locale": {
      "enum": [
        "en",
        "nl",
        "fr",
        "de",
        "es",
        "it",
        "pt",
        "pl",
        "sv",
        "tr",
        "el",
        "ja",
        "ko",
        "zh",
        "da",
        "nb",
        "fi",
        "cs",
        "ro",
        "hu",
        "sk",
        "uk",
        "hr",
        "sl",
        "bg",
        "ar",
        "et",
        "lv",
        "lt",
        "zh-Hant",
        "vi",
        "id",
        "th",
        "my",
        "pt-BR",
        "ca"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of the answer (default en)"
    }
  }
}
    arguments 49 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 3e95bd7015d5e1d9.

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