# Claspine (remote · api.claspine.com)

Claspine docs, API reference and code checks for AI agents: guides, recipes, errors, upgrades.

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.claspine.com`: 85/100 (this document), [markdown](https://verifymcp.io/servers/com-claspine-claspine/api.md), [page](https://verifymcp.io/servers/com-claspine-claspine/api)
- npm · `@grahmur-org/claspine-cli`: 34/100, [markdown](https://verifymcp.io/servers/com-claspine-claspine/grahmur-org-claspine-cli.md), [page](https://verifymcp.io/servers/com-claspine-claspine/grahmur-org-claspine-cli)

## Channel facts

- Endpoint: `https://api.claspine.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.31.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 3230 tokens (~46/item across 70 items; 12 tools + 58 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Claspine MCP server?

Claspine is a hosted endpoint at https://api.claspine.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-claspine-claspine 'https://api.claspine.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-claspine-claspine": {
      "url": "https://api.claspine.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-claspine-claspine": {
      "type": "http",
      "url": "https://api.claspine.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-claspine-claspine]
url = "https://api.claspine.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-claspine-claspine": {
      "type": "remote",
      "url": "https://api.claspine.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-claspine-claspine --url 'https://api.claspine.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-claspine-claspine:
    url: "https://api.claspine.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-claspine-claspine": {
      "Transport": "http",
      "Url": "https://api.claspine.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-claspine-claspine -t streamable-http -u 'https://api.claspine.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-claspine-claspine": {
      "type": "http",
      "url": "https://api.claspine.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-06 (score 78, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (12)

### `what_runs_where` (~90 tokens)

What runs where

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

Input parameters:

- `capability` (string): Optional words to filter by, for example "sign-in" or "payments".

### `plan_integration` (~270 tokens)

Plan a Claspine integration

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.

Input parameters:

- `current_version` (string): Only if the project already uses Claspine: its version now (grahmur.platform.version or the BOM version), for example 0.12.0. The plan then upgrades first.
- `database` (string): Self-hosted: where Claspine keeps its own tables (default postgres).
- `features` (array, required): What to add first.
- `form` (string, required): Where Claspine runs: the person's choice.
- `login` (string): Self-hosted: keep the app's own login, or move sign-in to Claspine (default: claspine when sign-in is a feature).
- `project` (string, required): new: little or no code yet; existing: an app that already runs.
- `stack` (string, required): The backend.
- `uses_spring_security` (boolean): Spring Boot: the project already uses Spring Security.

### `search_docs` (~93 tokens)

Search the Claspine docs

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.

Input parameters:

- `limit` (integer): Maximum results, 1 to 10 (default 5).
- `query` (string, required): A question or keywords, for example "add sign-in and email to my existing Spring Boot app".

### `get_guide` (~53 tokens)

Read a Claspine guide

The full text of one Claspine guide: steps, code, settings, safety notes and troubleshooting.

Input parameters:

- `slug` (string, required): The guide's slug, for example "sign-in-engine" (see search_docs).

### `get_recipe` (~117 tokens)

Get the exact calls for a task

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.

Input parameters:

- `form` (string): Where Claspine runs (default: the first the recipe supports).
- `language` (string): Code language (default curl; "all" for every language).
- `task` (string): Recipe slug or words, for example "file-upload" or "refund".

### `upgrade_notes` (~89 tokens)

Upgrade notes between two versions

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.

Input parameters:

- `from` (string, required): The version the application uses now, for example 0.26.0.
- `to` (string): The target version (default: the latest release).

### `check_upgrade` (~97 tokens)

What an upgrade needs

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.

Input parameters:

- `current` (string): Current version, if known.
- `files` (array): Project files to read the current version from (path and content).
- `target` (string): Target version (default: the latest release).

### `api_reference` (~87 tokens)

Claspine HTTP API reference

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.

Input parameters:

- `method` (string): HTTP method (default: the path's first).
- `path` (string): For example /payments/orders/{orderId}/refund.

### `java_api` (~85 tokens)

Claspine Java API (self-hosted Spring Boot)

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.

Input parameters:

- `capability` (string): For example payments, files, llm, notifications, authorization, foundation.
- `type` (string): A type name, for example Payments or RefundPaymentCommand.

### `explain_error` (~68 tokens)

Explain a Claspine error code

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.

Input parameters:

- `code` (string, required): The error's code, for example HOST_NOT_AVAILABLE.

### `check_code` (~125 tokens)

Check code against Claspine's guardrails

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.

Input parameters:

- `diff` (string): A unified diff (only added lines are checked).
- `files` (array): Files to check (path decides browser vs server code).

### `check_config` (~88 tokens)

Check Claspine settings

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.

Input parameters:

- `content` (string, required): The settings file's content.
- `format` (string): yaml, properties or env (default: guessed).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-claspine-claspine/api#diagnostics

## Score history

- 2026-11-21: 85
- 2026-11-20: 84
- 2026-11-19: 84
- 2026-11-18: 84
- 2026-11-17: 83
- 2026-11-16: 83
- 2026-11-15: 82
- 2026-11-14: 82
- 2026-11-13: 81
- 2026-11-12: 81
- 2026-11-11: 80
- 2026-11-10: 80
- 2026-11-09: 79
- 2026-11-08: 79
- 2026-11-07: 78
- 2026-11-06: 78
- 2026-11-05: 77
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 76
- 2026-11-01: 76
- 2026-10-31: 75
- 2026-10-30: 75
- 2026-10-29: 74
- 2026-10-28: 74
- 2026-10-27: 73
- 2026-10-26: 73

## Common questions

### What is the Claspine MCP server?

Claspine is an MCP server listed in the public MCP registry as com.claspine/claspine. Claspine docs, API reference and code checks for AI agents: guides, recipes, errors, upgrades. This page covers its hosted endpoint (https://api.claspine.com/mcp).

### Is the Claspine MCP server safe to use?

Claspine scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Claspine MCP server expose?

Claspine exposes 12 tools: what_runs_where, plan_integration, search_docs, get_guide, get_recipe, and 7 more. Their descriptions and schemas cost roughly 1,262 tokens of context every time the server is loaded.

### Does the Claspine MCP server require authentication?

No. We connected to Claspine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Claspine MCP server still maintained?

Claspine is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Claspine MCP server?

VerifyMCP ran 13 checks on Claspine, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.claspine.com/mcp
- Website: https://claspine.com/docs/ai-agents/
- Changelog RSS feed: https://verifymcp.io/servers/com-claspine-claspine/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-claspine-claspine/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-claspine-claspine/api.json
- HTML version of this page: https://verifymcp.io/servers/com-claspine-claspine/api
