mcp-server-java-sse-http-demo

Provides a demo Java MCP (Model Context Protocol) server that exposes tools over an SSE-based HTTP transport (Jetty). The repository also demonstrates a “fast-agent” workflow that can call other MCP servers (e.g., websearch for geocoding) and then call the included weather MCP server to summarize forecasts.

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ DevTools ai-ml mcp-server java jetty sse http-transport agentic-ai demo
⚙ Agent Friendliness
41
/ 100
Can an agent use this?
🔒 Security
19
/ 100
Is it safe for agents?
⚡ Reliability
18
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
50
Error Messages
0
Auth Simplicity
95
Rate Limits
0

🔒 Security

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

Based on README alone, the SSE/POST endpoints appear unauthenticated and are intended for local demonstration. TLS requirements, authn/authz, scope granularity, and rate limiting are not documented. This should be treated as insecure by default for any non-local/untrusted environment.

⚡ Reliability

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

Best When

For local demos, learning, and early prototypes that need an SSE HTTP transport MCP server in Java.

Avoid When

When you need enterprise-grade security controls, strong auth, and clearly specified reliability guarantees (retries/idempotency, error codes, rate limits) out of the box.

Use Cases

  • Demonstrate MCP server integration over HTTP using SSE
  • Build/learn MCP tool implementations in Java
  • Prototype multi-MCP “agent” flows (e.g., geocoding then weather)
  • Local development/testing of SSE MCP message streaming
  • Educational reference for wiring MCP with minimal Spring usage

Not For

  • Production deployments requiring hardened security, rate limiting, and operational safeguards
  • Use as-is for handling untrusted client traffic on the public internet
  • Workloads needing guaranteed uptime/SLA or rigorous error/retry semantics

Interface

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

Authentication

OAuth: No Scopes: No

No authentication mechanism is described for the SSE endpoint or the message POST endpoint. README shows unauthenticated curl commands to /sse and /mcp/message.

Pricing

Free tier: No
Requires CC: No

No pricing information present; appears to be an open-source demo.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Repo explicitly states it is not production grade; expect incomplete operational behaviors (auth, rate limits, robust error/retry semantics).
  • SSE configuration requires sessionId for follow-up message POSTs; agents must propagate/retain that sessionId from the SSE exchange.
  • No auth described; agents interacting from untrusted networks should not do so without adding external protections.

Alternatives

Full Evaluation Report

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

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