rest-mcp-server

A Java/Spring Boot integration that auto-exposes Spring REST controller endpoints as Model Context Protocol (MCP) tools, mounted into the app (SSE endpoint at /sse).

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ Ai Ml mcp spring-boot sse java ai-tools rest-api autodiscovery
⚙ Agent Friendliness
34
/ 100
Can an agent use this?
🔒 Security
27
/ 100
Is it safe for agents?
⚡ Reliability
24
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
60
Error Messages
0
Auth Simplicity
30
Rate Limits
0

🔒 Security

TLS Enforcement
20
Auth Strength
20
Scope Granularity
10
Dep. Hygiene
40
Secret Handling
50

README does not describe authentication/authorization, rate limiting, or TLS requirements for the /sse endpoint. Because it auto-exposes REST endpoints as agent tools, the primary risk is unintended exposure of sensitive endpoints; access should be restricted at the Spring layer (not covered here).

⚡ Reliability

Uptime/SLA
0
Version Stability
45
Breaking Changes
30
Error Recovery
20
AF Security Reliability

Best When

You already have a Spring Boot app with REST controllers and you want rapid MCP tool access for development or internal tooling.

Avoid When

You cannot control or audit which REST endpoints get exposed as agent tools, or you require strict security-by-default and detailed operational controls.

Use Cases

  • Expose existing Spring REST APIs to MCP-capable AI clients without manually writing MCP tools
  • Create quick internal tool surfaces for agent workflows based on controller method signatures
  • Prototype agent-API integrations using request/response model schemas

Not For

  • Production deployments requiring strong authentication/authorization defaults
  • Environments needing explicit, curated tool selection (it appears to auto-discover all REST endpoints)
  • Teams requiring published SLAs, detailed operational guidance, or formal stability guarantees

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication/authorization mechanism is described in the provided README. Security controls, if any, are delegated to the underlying Spring/MCP configuration referenced in the Spring AI docs link.

Pricing

Free tier: No
Requires CC: No

Open-source (MIT license claimed). No pricing information provided.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Auto-discovery may expose more tools/endpoints than intended unless you restrict controller exposure.
  • Tool names map to REST controller method names, which may not be agent-friendly or may collide across controllers.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for rest-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered