Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Claspine

REMOTE · API.CLASPINE.COM · 2 COMPONENTS

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

+3 this week 85 Trust /100

Last scanned (22 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 3230 tokens (~46/item across 70 items; 12 tools + 58 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

  • 8 Nov 26 +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.

  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.claspine.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.claspine.com CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US 25 Oct 2026 25 Apr 2027 RSA 2048 SHA256-RSA 47749683046201c92f733d36cdf82d1
SANs: api.claspine.com
CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 2 Nov 2017 2 Nov 2027 RSA 2048 SHA256-RSA d07782a133fc6f9a57296e131ffd179

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.claspine.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
claspine.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.claspine.com/mcp Verified 200
http (plaintext) http://api.claspine.com/mcp HTTPS enforced 301 https://api.claspine.com/mcp
MCP tools · 12 exposed · ~1,262 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
api_reference ~87

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.

NameTypeReqDescription
methodstring–HTTP method (default: the path's first).
pathstring–For example /payments/orders/{orderId}/refund.

No output schema declared.

No examples provided.

check_code ~125

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.

NameTypeReqDescription
diffstring–A unified diff (only added lines are checked).
filesarray–Files to check (path decides browser vs server code).

No output schema declared.

No examples provided.

check_config ~88

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.

NameTypeReqDescription
contentstringyesThe settings file's content.
formatstring–yaml, properties or env (default: guessed).

No output schema declared.

No examples provided.

check_upgrade ~97

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.

NameTypeReqDescription
currentstring–Current version, if known.
filesarray–Project files to read the current version from (path and content).
targetstring–Target version (default: the latest release).

No output schema declared.

No examples provided.

explain_error ~68

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.

NameTypeReqDescription
codestringyesThe error's code, for example HOST_NOT_AVAILABLE.

No output schema declared.

No examples provided.

get_guide ~53

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

NameTypeReqDescription
slugstringyesThe guide's slug, for example "sign-in-engine" (see search_docs).

No output schema declared.

No examples provided.

get_recipe ~117

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.

NameTypeReqDescription
formstring–Where Claspine runs (default: the first the recipe supports).
languagestring–Code language (default curl; "all" for every language).
taskstring–Recipe slug or words, for example "file-upload" or "refund".

No output schema declared.

No examples provided.

java_api ~85

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.

NameTypeReqDescription
capabilitystring–For example payments, files, llm, notifications, authorization, foundation.
typestring–A type name, for example Payments or RefundPaymentCommand.

No output schema declared.

No examples provided.

plan_integration ~270

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.

NameTypeReqDescription
current_versionstring–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.
databasestring–Self-hosted: where Claspine keeps its own tables (default postgres).
featuresarrayyesWhat to add first.
formstringyesWhere Claspine runs: the person's choice.
loginstring–Self-hosted: keep the app's own login, or move sign-in to Claspine (default: claspine when sign-in is a feature).
projectstringyesnew: little or no code yet; existing: an app that already runs.
stackstringyesThe backend.
uses_spring_securityboolean–Spring Boot: the project already uses Spring Security.

No output schema declared.

No examples provided.

search_docs ~93

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.

NameTypeReqDescription
limitinteger–Maximum results, 1 to 10 (default 5).
querystringyesA question or keywords, for example "add sign-in and email to my existing Spring Boot app".

No output schema declared.

No examples provided.

upgrade_notes ~89

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.

NameTypeReqDescription
fromstringyesThe version the application uses now, for example 0.26.0.
tostring–The target version (default: the latest release).

No output schema declared.

No examples provided.

what_runs_where ~90

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

NameTypeReqDescription
capabilitystring–Optional words to filter by, for example "sign-in" or "payments".

No output schema declared.

No examples provided.

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.

remote · api.claspine.com

# add to Claude Code
claude mcp add --transport http com-claspine-claspine 'https://api.claspine.com/mcp'
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.