Claspine MCP server
com.claspine/claspineclaspine.comstreamable-httpv0.31.0Scanned
Claspine docs, API reference and code checks for AI agents: guides, recipes, errors, upgrades.
12 tools: 1 do something that can't be undone, 8 change things and 3 only read.
- Reads private data · 3
- Reads text others write · 1
- Can send data out · 1
- 5 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Claspine MCP server can do
The Claspine MCP server is published by claspine.com, a domain the MCP Registry verified. It has 12 tools. It can do things that cannot be undone, such as sending, paying or publishing (upgrade_notes) and create or change data (8 tools: what_runs_where, plan_integration, get_recipe, api_reference and 4 more), but cannot delete data. 3 tools only read.
3 tools read private data (search_docs, get_guide and check_upgrade); 1 tool brings in text other people can write (get_recipe); 1 tool can send data out of your system (upgrade_notes). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 5 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 0.31.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.
12 tools
Can't be undone 1Claude Code: ask
upgrade_notesEvery Claspine upgrade note after one version up to another, oldest first, with what changed, the checklist for product code and what to do before deploying.Can send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "upgrade_notes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it Every Claspine upgrade note after one version up to another, oldest first, with what changed, the checklist for product code and what to do before deploying. Read them all before changing the Claspine version.
Annotations the server declares
- title: Upgrade notes between two versions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Changes things 8Claude Code: ask
api_referenceThe published HTTP contract shared by Claspine Atlas and the self-hosted engine (paths under /api/v1).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 The published HTTP contract shared by Claspine Atlas and the self-hosted engine (paths under /api/v1). Without path: every operation. With path (and method): parameters, request body and responses with schemas resolved.
Annotations the server declares
- title: Claspine HTTP API reference
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_codeRuns Claspine's Agent Shield rules on files or a unified diff: hardcoded or client-exposed secrets, SQL built from strings, unscoped tenant queries, secrets in logs, buffered uploa…1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "check_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.
Description, as the server wrote it Runs Claspine's Agent Shield rules on files or a unified diff: hardcoded or client-exposed secrets, SQL built from strings, unscoped tenant queries, secrets in logs, buffered uploads, imports of platform internals. Returns file, line, rule and the fix. Code is analysed in memory and not stored. A clean result is not proof of safety; Spring Boot builds also run ProductBoundaryTest.
Annotations the server declares
- title: Check code against Claspine's guardrails
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_configChecks application.yml / application.properties or the engine's environment variables: empty values that switch providers on, sandbox sign-in in STAGING/PRODUCTION, IP addresses as…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 Checks application.yml / application.properties or the engine's environment variables: empty values that switch providers on, sandbox sign-in in STAGING/PRODUCTION, IP addresses as hosts, secrets written into settings, and misspelled setting names. Content is not stored.
Annotations the server declares
- title: Check Claspine settings
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
explain_errorWhat a Claspine error code means and how to fix it: HTTP status, the messages it is raised with, where, and the fix for common ones.1 finding
Why it is in this group
- The name "explain_error" says "explain": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "explain_error" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explain_error" says "explain": a word for reading.
Description, as the server wrote it What a Claspine error code means and how to fix it: HTTP status, the messages it is raised with, where, and the fix for common ones. Every Claspine error response carries its code.
Annotations the server declares
- title: Explain a Claspine error code
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_recipeCopy-ready HTTP calls for a common task on Claspine Atlas or the self-hosted engine, in curl, Node.js, Python, Go or Java, checked against Claspine's API on every build.Reads text others write1 finding
Why it is in this group
- The name "get_recipe" says "get": a word for reading.
- The description's first verb is "copy": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe description's first sentence says "copy" and "http": it reads web pages, which anyone can write.
Findings
- Warn
The server marks "get_recipe" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_recipe" says "get": a word for reading.
Description, as the server wrote it Copy-ready HTTP calls for a common task on Claspine Atlas or the self-hosted engine, in curl, Node.js, Python, Go or Java, checked against Claspine's API on every build. Without task: the list.
Annotations the server declares
- title: Get the exact calls for a task
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
java_apiThe public Java types of a Claspine capability (its api package) and of the foundation, with methods and record fields, from the current platform build.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 The public Java types of a Claspine capability (its api package) and of the foundation, with methods and record fields, from the current platform build. Without arguments: the capabilities.
Annotations the server declares
- title: Claspine Java API (self-hosted Spring Boot)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
plan_integrationAn exact, ordered plan for adding Claspine to this project: what the person must do first, then each step with the files and settings to change (current release pinned) and how to …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 An exact, ordered plan for adding Claspine to this project: what the person must do first, then each step with the files and settings to change (current release pinned) and how to prove it worked. Call it after you know the stack, new or existing, and the person's decisions (Atlas or self-hosted, whose login, which features), and follow it step by step.
Annotations the server declares
- title: Plan a Claspine integration
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
what_runs_whereWhich Claspine capabilities exist on Claspine Atlas, the self-hosted engine (any language over HTTP) and self-hosted Spring Boot.1 finding
Why it is in this group
- The name "what_runs_where" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "what_runs_where" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "what_runs_where" says "run": a word for a change.
Description, as the server wrote it Which Claspine capabilities exist on Claspine Atlas, the self-hosted engine (any language over HTTP) and self-hosted Spring Boot. Check this before planning any Claspine integration: they differ (for example, Claspine Atlas has no sign-in, permissions or push).
Annotations the server declares
- title: What runs where
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
check_upgradeFinds the Claspine version in project files (pom.xml, build.gradle, package.json, docker-compose.yml) or takes it as given, and lists the checklist items of every upgrade note up t…Reads private dataNo findings
Why it is in this group
- The description's first verb is "find": a word for reading.
What it can reach
- private-dataThe description's first sentence says "find" and "file": it reads files.
- private-dataThe input names a file (input.files), and the tool reads: it reads files.
Description, as the server wrote it Finds the Claspine version in project files (pom.xml, build.gradle, package.json, docker-compose.yml) or takes it as given, and lists the checklist items of every upgrade note up to the target.
Annotations the server declares
- title: What an upgrade needs
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_guideThe full text of one Claspine guide: steps, code, settings, safety notes and troubleshooting.Reads private dataNo findings
Why it is in this group
- The name "get_guide" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "note": it reads notes.
Description, as the server wrote it The full text of one Claspine guide: steps, code, settings, safety notes and troubleshooting.
Annotations the server declares
- title: Read a Claspine guide
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_docsSearch Claspine's guides, recipes, capability table and error fixes with a plain question or keywords.Reads private dataNo findings
Why it is in this group
- The name "search_docs" says "search": a word for reading.
What it can reach
- private-dataThe name "search_docs" says "search" and "doc": it reads documents.
- private-dataThe description's first sentence says "search" and "table": it reads databases.
Description, as the server wrote it Search Claspine's guides, recipes, capability table and error fixes with a plain question or keywords. Returns the best matches first, with links; follow up with get_guide or get_recipe.
Annotations the server declares
- title: Search the Claspine docs
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- 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.
3 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__claspine__upgrade_notes"
]
}
}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 18, 2026, 16:23 UTC, unchanged since Oct 27, 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
- 9
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.claspine.com/.well-known/oauth-protected-resource
- Authorization servers
- https://api.claspine.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 9 tools that change things (1 irreversible, 8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.claspine.com/mcp: tools/list returned 12 tools to an anonymous client, including upgrade_notes (irreversible), what_runs_where (write), plan_integration (write), get_recipe (write), api_reference (write) and 4 more
Findings
Matches of fixed checks, with the text they matched.
- Warnwhat_runs_where
The server marks "what_runs_where" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "what_runs_where" says "run": a word for a change.
- Warnget_recipe
The server marks "get_recipe" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_recipe" says "get": a word for reading.
- Warnupgrade_notes
The server marks "upgrade_notes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
- Warnexplain_error
The server marks "explain_error" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explain_error" says "explain": a word for reading.
- Warncheck_code
The server marks "check_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added.+1 addedView diff
- Added:plan_integrationChanges things
Install
Pinned to version 0.31.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http claspine https://api.claspine.com/mcpclaude mcp add --transport http claspine https://api.claspine.com/mcpRun 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__claspine__search_docs",
"mcp__claspine__get_guide",
"mcp__claspine__check_upgrade"
],
"ask": [
"mcp__claspine__what_runs_where",
"mcp__claspine__plan_integration",
"mcp__claspine__get_recipe",
"mcp__claspine__upgrade_notes",
"mcp__claspine__api_reference",
"mcp__claspine__java_api",
"mcp__claspine__explain_error",
"mcp__claspine__check_code",
"mcp__claspine__check_config"
],
"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 claspine. Review it before you use it.
Capability tags behind 5 rules
- mcp__claspine__search_docs private-data
- mcp__claspine__get_guide private-data
- mcp__claspine__get_recipe untrusted-input
- mcp__claspine__upgrade_notes outbound
- mcp__claspine__check_upgrade private-data
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/com.claspine/claspine/verify?hash=a237ec7fa32cd85286f80538cdfbec4a708de7ea320faf7c459b506b1f55edfc" | jq -e '.changed == false'Pinned hash a237ec7fa32c, from Nov 9, 2026, 11:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.claspine/claspine/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.claspine/claspine)Source: MCP Registry. Synced Oct 26, 2026, 19:19 UTC.
Claspine MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Claspine MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 9 of which can change, send or delete something, and 5 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 Claspine MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Claspine MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: upgrade_notes.
What tools does the Claspine MCP server have?
- 12 tools: 1 irreversible, 8 write, 3 read. upgrade_notes, what_runs_where, plan_integration, get_recipe, api_reference, java_api, explain_error, check_code and 4 more.
Does the Claspine MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Claspine MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): upgrade_notes.
Has the Claspine MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.