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.

Spring Boot Runtime Diagnostics

PYPI · SPRING-RUNTIME-MCP

Read-only Spring Boot runtime evidence for agents: beans, routes, health, startup.

Available components

62 Trust /100

Last scanned (14 hours ago)

Scores higher than 58% of PyPI servers

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to neilmorse/spring-runtime-mcp). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability49
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 1237 tokens (~154/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 12% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.8 → 0.2.12 functional
    • Package version: 0.2.8 → 0.2.11 functional
    • Package version: 0.2.8 → 0.2.10 functional
    • Package version: 0.2.8 → 0.2.9 functional
  • 1 Nov 26 +15
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.2 → 0.2.8 functional
    • Package version: 0.2.2 → 0.2.7 functional
    • Package version: 0.2.2 → 0.2.6 functional
    • Package version: 0.2.2 → 0.2.5 functional
    • Package version: 0.2.2 → 0.2.4 functional
  • 31 Oct 26 60

    First indexed and scored.

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 4 Nov 2026 · Analysed pypi/spring-runtime-mcp@0.2.12

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo neilmorse/spring-runtime-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/neilmorse/spring-runtime-mcp/.github/workflows/release.yml@refs/tags/v0.2.12
Rekor log index 3642517170
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:9816ef18671d1ae5550c4fee2c52f9ed85674071702a7d0b9c56edcf404067c4

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,237 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
springboot_analyze_startup ~162

返回非破坏性启动快照中的版本、时间线跨度、最慢步骤及父子链;排查慢启动时调用,不用于当前请求延迟,也不执行排空缓冲区的 POST。

NameTypeReqDescription
beanNamePatternstring–Bounded case-sensitive glob: only * and ? are wildcards; all other allowed characters are literal. No regex.
cursorstring––
maxDepthinteger––
maxResultsinteger––
minDurationMsnumber––
stepNamePatternstring–Bounded case-sensitive glob: only * and ? are wildcards; all other allowed characters are literal. No regex.
targetIdstring––
NameTypeReqDescription
coverageobjectyes–
data–yes–
errorsarrayyes–
nextActionobjectyes–
nextCursor–yes–
redactionsarrayyes–
schemaVersion–yes–
sourceobjectyes–
status–yes–
totalMatched–yes–
truncatedbooleanyes–
truncationReasonsarrayyes–
warningsarrayyes–

No examples provided.

springboot_check_migrations ~142

返回所有容器和迁移 Bean 的已报告迁移、校验和、顺序及异常状态;排查迁移失败或版本差异时调用,未报告的待执行状态需要可信预期,且不会执行 SQL 或迁移。

NameTypeReqDescription
contextIdstring––
cursorstring––
engine–––
expectedMigrationsarray––
expectedSetCompleteboolean––
maxResultsinteger––
migrationBeanstring––
statearray––
targetIdstring––
versionstring––
NameTypeReqDescription
coverageobjectyes–
data–yes–
errorsarrayyes–
nextActionobjectyes–
nextCursor–yes–
redactionsarrayyes–
schemaVersion–yes–
sourceobjectyes–
status–yes–
totalMatched–yes–
truncatedbooleanyes–
truncationReasonsarrayyes–
warningsarrayyes–

No examples provided.

springboot_detect_drift ~165

比较调用者从获权工作区提取的 Bean、路由、迁移版本和 Profile 预期,返回差异及分级根因候选;源码与运行行为不一致时调用,省略维度不参与比较,文件时间本身不能证明未重启。

NameTypeReqDescription
cursorstring––
expectedBeansarray––
expectedMigrationVersionobject––
expectedProfilesarray––
expectedRoutesarray––
expectedScopeCompleteboolean––
maxDepthinteger––
maxResultsinteger––
sourceModifiedAtstring––
sourceRevisionstring––
targetIdstring––
NameTypeReqDescription
coverageobjectyes–
data–yes–
errorsarrayyes–
nextActionobjectyes–
nextCursor–yes–
redactionsarrayyes–
schemaVersion–yes–
sourceobjectyes–
status–yes–
totalMatched–yes–
truncatedbooleanyes–
truncationReasonsarrayyes–
warningsarrayyes–

No examples provided.

springboot_diagnose_health ~126

返回整体健康状态、异常组件树及已脱敏的结构化错误和修复代码;依赖故障或探针异常时调用,组件下钻在本地完成,不获取日志、堆转储或原始异常栈。

NameTypeReqDescription
componentPatharray––
cursorstring––
group–––
includeDetailsboolean––
includeHealthyboolean––
maxDepthinteger––
maxResultsinteger––
targetIdstring––
NameTypeReqDescription
coverageobjectyes–
data–yes–
errorsarrayyes–
nextActionobjectyes–
nextCursor–yes–
redactionsarrayyes–
schemaVersion–yes–
sourceobjectyes–
status–yes–
totalMatched–yes–
truncatedbooleanyes–
truncationReasonsarrayyes–
warningsarrayyes–

No examples provided.

springboot_inspect_beans ~198

返回匹配 Bean、别名及双向依赖图,并在 Bean 缺失时自动读取已授权条件报告、展开嵌套与传递阻塞链;排查注入或条件装配时调用,证据不足时返回 unknown,不猜测确切原因。

NameTypeReqDescription
beanNamePatternstring–Bounded case-sensitive glob: only * and ? are wildcards; all other allowed characters are literal. No regex.
conditionDepthinteger––
contextIdstring––
cursorstring––
direction–––
maxDepthinteger––
maxResultsinteger––
packagePrefixstring––
targetIdstring––
typePatternstring–Bounded case-sensitive glob: only * and ? are wildcards; all other allowed characters are literal. No regex.
NameTypeReqDescription
coverageobjectyes–
data–yes–
errorsarrayyes–
nextActionobjectyes–
nextCursor–yes–
redactionsarrayyes–
schemaVersion–yes–
sourceobjectyes–
status–yes–
totalMatched–yes–
truncatedbooleanyes–
truncationReasonsarrayyes–
warningsarrayyes–

No examples provided.

springboot_inspect_config ~142

返回双层强制脱敏后的生效属性、绑定 Bean、来源位置及 Active Profiles;排查属性绑定或配置覆盖时按前缀或键模式调用,能力默认关闭且不能用于获取秘密或导出全量配置。

NameTypeReqDescription
contextIdstring––
cursorstring––
includeValuesboolean––
maxResultsinteger––
prefixstring––
propertyKeyPatternstring–Bounded case-sensitive glob: only * and ? are wildcards; all other allowed characters are literal. No regex.
targetIdstring––
NameTypeReqDescription
coverageobjectyes–
data–yes–
errorsarrayyes–
nextActionobjectyes–
nextCursor–yes–
redactionsarrayyes–
schemaVersion–yes–
sourceobjectyes–
status–yes–
totalMatched–yes–
truncatedbooleanyes–
truncationReasonsarrayyes–
warningsarrayyes–

No examples provided.

springboot_search_openapi ~144

返回匹配操作或 Schema,并默认内联直接与二阶同文档引用;确认接口契约时使用精确选择器调用,不执行业务接口、不返回全量文档,也不解析远程引用。

NameTypeReqDescription
cursorstring––
httpMethod–––
maxRefDepthinteger––
maxResultsinteger––
operationIdstring––
pathPatternstring–Bounded case-sensitive glob: only * and ? are wildcards; all other allowed characters are literal. No regex.
schemaNamestring––
targetIdstring––
NameTypeReqDescription
coverageobjectyes–
data–yes–
errorsarrayyes–
nextActionobjectyes–
nextCursor–yes–
redactionsarrayyes–
schemaVersion–yes–
sourceobjectyes–
status–yes–
totalMatched–yes–
truncatedbooleanyes–
truncationReasonsarrayyes–
warningsarrayyes–

No examples provided.

springboot_verify_mappings ~158

返回统一的 MVC/WebFlux 路由、处理器和方法描述符;排查路径、方法或 Controller 未注册时调用,不向业务 URL 发请求,也不把注册匹配等同于请求一定成功。

NameTypeReqDescription
contextIdstring––
controllerClassPatternstring–Bounded case-sensitive glob: only * and ? are wildcards; all other allowed characters are literal. No regex.
cursorstring––
httpMethod–––
maxResultsinteger––
pathPatternstring–Bounded case-sensitive glob: only * and ? are wildcards; all other allowed characters are literal. No regex.
targetIdstring––
NameTypeReqDescription
coverageobjectyes–
data–yes–
errorsarrayyes–
nextActionobjectyes–
nextCursor–yes–
redactionsarrayyes–
schemaVersion–yes–
sourceobjectyes–
status–yes–
totalMatched–yes–
truncatedbooleanyes–
truncationReasonsarrayyes–
warningsarrayyes–

No examples provided.

Install

How do I install the Spring Boot Runtime Diagnostics MCP server?

Spring Boot Runtime Diagnostics runs locally as a PyPI package, launched with uvx spring-runtime-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · spring-runtime-mcp

# add to Claude Code
claude mcp add neilmorse-spring-runtime-mcp -- uvx spring-runtime-mcp
Common questions

What is the Spring Boot Runtime Diagnostics MCP server?

Spring Boot Runtime Diagnostics is an MCP server listed in the public MCP registry as io.github.neilmorse/spring-runtime-mcp. Read-only Spring Boot runtime evidence for agents: beans, routes, health, startup. This page covers its PyPI package (spring-runtime-mcp).

Is the Spring Boot Runtime Diagnostics MCP server safe to use?

Spring Boot Runtime Diagnostics scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 Spring Boot Runtime Diagnostics MCP server expose?

Spring Boot Runtime Diagnostics exposes 8 tools: springboot_analyze_startup, springboot_check_migrations, springboot_detect_drift, springboot_diagnose_health, springboot_inspect_beans, and 3 more. Their descriptions and schemas cost roughly 1,237 tokens of context every time the server is loaded.

Is the Spring Boot Runtime Diagnostics MCP server still maintained?

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

What licence is the Spring Boot Runtime Diagnostics MCP server under?

Spring Boot Runtime Diagnostics declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.