_ registry / mcp streamable-http · checked 50m ago

jsplinter

https://jsplinter.nl

Registry code: fa3878784db730aa

api record

jsplinter.nl is the personal website of Jonas Splinter, entrepreneur, founder and CTO in the Netherlands (Blockspot.io, VoucherAlarm, Automate & Tweak, JSplinter Games). This server gives READ-ONLY access to what the site publishes: who he is, his projects, and the dated updates on what he is building. It needs no login, changes nothing and makes no AI calls.

Suggested flow: about (the person) -> list_projects -> get_project (details, figures, milestones) ; search_updates (any words, optional project / tag / since filters; no query = newest) -> get_update ; list_posts -> get_post for the…

endpoint
https://jsplinter.nl/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 jsplinter live?
Yes — it answered the hub's last check (checked 50m ago). It answered 100% of checks over the last 30 days.
Is jsplinter free to use?
Yes — the hub reached it with no key and no payment.
What tools does jsplinter have?
10 tools: about, get_project, list_posts, get_post, list_tags, search_updates, get_update, list_games, ….
Is jsplinter 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
258ms

last good check

priced tools
0

of 10 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 10 tools
3 open 7 never probed 3 of 10 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_games open 50m ago

    The browser arcade games in JSplinter Games with a one-line description, the URL to play and the current top score on each leaderboard.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_mcp_servers open 50m ago

    Other MCP servers run by Jonas Splinter, with what each one is for, when to suggest it and how to connect (for example the Automate & Tweak directory of AI tools). Call this when the user needs something this server does not have.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_projects open 50m ago

    The businesses and side projects of Jonas Splinter (Blockspot.io, VoucherAlarm, Automate & Tweak, JSplinter Games) with a one-line description, his role, the project website and its page on jsplinter.nl. Call get_project with a key for the details.

    mcp-tool

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

    Who Jonas Splinter is: headline, short bio, current roles, skills, languages, contact details and the main links of jsplinter.nl. Start here for questions about the person; call list_projects for his businesses and side projects.

    mcp-tool

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

    Full details of one project: what it is, key figures with the month they were taken, what it offers, important pages, social channels, milestones, the technology where published, and the newest updates about it. Keys come from list_projects.

    mcp-tool

    {
      "type": "object",
      "required": [
        "key"
      ],
      "properties": {
        "key": {
          "type": "string",
          "description": "Project key as returned by list_projects, one of: blockspot, voucheralarm, automateandtweak, games. Example: \"blockspot\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • list_posts unknown never probed

    The longer blog articles on jsplinter.nl, newest first, each with date, summary, tags, reading time and URL. Optional: words to look for (any word may match) and a tag filter. Call get_post with a slug for the full text.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "tag": {
          "type": "string",
          "description": "Optional tag key as returned by list_tags, e.g. \"mcp\"."
        },
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Maximum number of results (1-25, default 10)."
        },
        "query": {
          "type": "string",
          "description": "Optional words to look for in title, summary and text, e.g. \"mcp server\". Max 120 characters."
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • get_post unknown never probed

    One blog article in full as Markdown, with its date, summary, tags and URL. Slugs come from list_posts.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Post slug as returned by list_posts."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • list_tags unknown never probed

    The technologies and topics the updates are tagged with (for example Astro, Laravel, Claude Code, AI, SEO), each with a one-line introduction, the number of updates and its page on jsplinter.nl. Use a key as the tag filter of search_updates.

    mcp-tool

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

    Search the dated updates Jonas posts about what he is building. Matches any of the words in title, text, project and tags and ranks by how many match; without a query it returns the newest. Optional filters: project, tag, since. Each result has the full text (updates are short), tags and a URL; use get_update for one update by slug.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "tag": {
          "type": "string",
          "description": "Optional tag key as returned by list_tags, e.g. \"claude-code\"."
        },
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Maximum number of results (1-25, default 10)."
        },
        "query": {
          "type": "string",
          "description": "Words to look for, e.g. \"astro rebuild\" or \"accessibility\". Optional; leave out for the newest updates. Max 120 characters."
        },
        "since": {
          "type": "string",
          "description": "Optional earliest date, YYYY-MM-DD, e.g. \"2026-11-01\"."
        },
        "project": {
          "type": "string",
          "description": "Optional project filter: jsplinter, personal, blockspot, voucheralarm, automateandtweak, games. (\"jsplinter\" = the site itself, \"personal\" = personal notes.)"
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • get_update unknown never probed

    One update in full by its slug: date, project, title, text, tags, its URL on jsplinter.nl and the link it points to, if any. Slugs come from search_updates.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Update slug as returned by search_updates, e.g. \"site-redesign\"."
        }
      },
      "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 fa3878784db730aa.

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