Robskan MCP server
nl.robskan/siterobskan.nlstreamable-httpv1.0.0Scanned
Read-only product MCP for robskan.nl — public profile and Spotify listening APIs.
5 tools: 3 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.
What the Robskan MCP server can do
The Robskan MCP server is published by robskan.nl, a domain the MCP Registry verified. It has 5 tools. It can create or change data (3 tools: compute_year_progress, create_listening_summary and verify_http_route), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 3Claude Code: ask
compute_year_progressCompute calendar year progress for a timezone (live product metric).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Compute calendar year progress for a timezone (live product metric).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
create_listening_summaryCreate a listening summary rollup for day or week from recent plays.No findings
Why it is in this group
- The name "create_listening_summary" says "create": a word for a change.
Description, as the server wrote it Create a listening summary rollup for day or week from recent plays.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
verify_http_routeVerify an HTTP method and path against the Robskan product API allowlist.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Verify an HTTP method and path against the Robskan product API allowlist.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 2Show 2 read-only tools
lookup_project_statusLook up Meridian or Dock product availability and links.No findings
Why it is in this group
- The name "lookup_project_status" says "lookup": a word for reading.
Description, as the server wrote it Look up Meridian or Dock product availability and links.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
pull_now_playing_snapshotLoad the live Spotify now-playing snapshot from the music product API.No findings
Why it is in this group
- The name "pull_now_playing_snapshot" says "snapshot": a word for reading.
Description, as the server wrote it Load the live Spotify now-playing snapshot from the music product API.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:22 UTC, unchanged since Nov 2, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://robskan.nl/.well-known/oauth-protected-resource
- Authorization servers
- https://robskan.nl
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- no
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://robskan.nl/mcp/product: tools/list returned 5 tools to an anonymous client, including compute_year_progress (write), create_listening_summary (write), verify_http_route (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools5 added, 3 removed.+5 added−3 removedView diff
- Added:compute_year_progressChanges things
- Added:create_listening_summaryChanges things
- Added:lookup_project_statusOnly reads
- Added:pull_now_playing_snapshotOnly reads
- Added:verify_http_routeChanges things
- Removed:get_listening_history_summary
- Removed:get_now_playing
- Removed:get_profile
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http site https://robskan.nl/mcp/productclaude mcp add --transport http site https://robskan.nl/mcp/productRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__site__lookup_project_status",
"mcp__site__pull_now_playing_snapshot"
],
"ask": [
"mcp__site__compute_year_progress",
"mcp__site__create_listening_summary",
"mcp__site__verify_http_route"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as site. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/nl.robskan/site/verify?hash=99ef1f63622e294d98d9b2750c70b00d18ba59e6b332e69b2d902e12dff1121b" | jq -e '.changed == false'Pinned hash 99ef1f63622e, from Nov 13, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/nl.robskan/site/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/nl.robskan/site)Source: MCP Registry. Synced Nov 1, 2026, 01:17 UTC.
Robskan MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Robskan MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Robskan MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Robskan MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Robskan MCP server have?
- 5 tools: 3 write, 2 read. compute_year_progress, create_listening_summary, verify_http_route, lookup_project_status and pull_now_playing_snapshot.
Does the Robskan MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Robskan MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Robskan MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.