_ registry / mcp streamable-http · checked 1h ago

janlinketscher

https://janlinketscher.com

Registry code: 3cacdbe70068db89

api record

Access to Jan Linketscher's personal site (https://janlinketscher.com): profile, the essays and full-text search. You can also book a call with him: list_meeting_types, get_availability, then book_meeting. Clients with elicitation get a confirmation form for the user; others must get the user's explicit approval first and pass confirmed: true. Content is German. Cite with name and URL. Docs: https://janlinketscher.com/agent

endpoint
https://janlinketscher.com/api/mcp
protocol
streamable-http ·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 janlinketscher live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is janlinketscher free to use?
Yes — the hub reached it with no key and no payment.
What tools does janlinketscher have?
7 tools: search, get_availability, book_meeting, get_essay, get_profile, list_essays, list_meeting_types.
Is janlinketscher 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
144ms

last good check

priced tools
0

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

  • get_profile open 1h ago

    Who Jan Linketscher is: managing director and shareholder of the digital agency i22 (Bonn), his background, how his texts are written, and how to contact him. Content is in German.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "section": {
          "enum": [
            "all",
            "role",
            "background",
            "writing",
            "contact"
          ],
          "type": "string",
          "description": "Limit the text answer to one section (default: all). Structured output is always complete."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • list_essays open 1h ago

    List the essays, newest first: title, date, one-sentence summary, topics, URL and slug. Optionally filter by topic slug. Also returns the available topics.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum number of essays (default 20)."
        },
        "topic": {
          "type": "string",
          "description": "Topic slug, e.g. \"transformation\" or \"agentic-visibility\". Omit for all essays."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • list_meeting_types open 1h ago

    The kinds of calls that can be booked with Jan Linketscher ("kennenlernen" (Kennenlernen, 30 min), "sparring" (Sparring, 60 min)), with duration, purpose and a booking link for humans.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • search unknown never probed

    Full-text search across all essays and pages (about, context). Returns the best matches with title, URL and a short snippet. German queries work best.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Maximum number of results (default 5)."
        },
        "query": {
          "type": "string",
          "minLength": 2,
          "description": "Search terms."
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • get_availability unknown never probed

    Free time slots for a call with Jan Linketscher. meeting_type: "kennenlernen" (Kennenlernen, 30 min), "sparring" (Sparring, 60 min). Optional date range (YYYY-MM-DD, default: the next 14 days, at most 90 days ahead). Times are ISO 8601 with offset; the text answer lists them in Europe/Berlin.

    mcp-tool

    {
      "type": "object",
      "required": [
        "meeting_type"
      ],
      "properties": {
        "to": {
          "type": "string",
          "format": "date",
          "description": "Last day (YYYY-MM-DD), inclusive. Default: from + 13 days."
        },
        "from": {
          "type": "string",
          "format": "date",
          "description": "First day (YYYY-MM-DD). Default: today."
        },
        "meeting_type": {
          "enum": [
            "kennenlernen",
            "sparring"
          ],
          "type": "string",
          "description": "Kind of call."
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • book_meeting unknown never probed

    Book a call with Jan Linketscher on behalf of your user. The start must be a slot returned by get_availability. If your client supports elicitation (form mode, MCP 2026-07-28), the server itself asks the user to confirm time, name and email – name and email are then prefilled from your arguments and can be corrected by the user. Otherwise: show the user meeting type, date and time (with time zone), name and email, get their explicit approval, then pass name, email and confirmed: true. Use the user's real name and email; never invent them. Cal.com sends the confirmation with a calendar invite and links to reschedule or cancel to that email address.

    mcp-tool

    {
      "type": "object",
      "required": [
        "meeting_type",
        "start"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 100,
          "minLength": 2,
          "description": "Full name of the person attending."
        },
        "email": {
          "type": "string",
          "format": "email",
          "description": "Email of the person attending; the confirmation goes there."
        },
        "notes": {
          "type": "string",
          "maxLength": 1000,
          "description": "Optional: what the call is about, in one or two sentences."
        },
        "start": {
          "type": "string",
          "format": "date-time",
          "description": "Slot start from get_availability (ISO 8601)."
        },
        "confirmed": {
          "type": "boolean",
          "description": "Only for clients without elicitation: true = the user has explicitly approved this booking."
        },
        "time_zone": {
          "type": "string",
          "description": "IANA time zone of the attendee, e.g. \"Europe/Berlin\" (default Europe/Berlin)."
        },
        "meeting_type": {
          "enum": [
            "kennenlernen",
            "sparring"
          ],
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 46 lines
  • get_essay unknown never probed

    Full text of one essay as Markdown (with front matter). Use the slug from list_essays or search.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Essay slug, e.g. \"mein-essay\" (the last part of /essays/<slug>)."
        }
      },
      "additionalProperties": false
    }
    arguments 13 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 3cacdbe70068db89.

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