{"id":"dpolishuk-spring-boot-ai-mcp-server","name":"spring-boot-ai-mcp-server","homepage":null,"repo_url":"https://github.com/dpolishuk/spring-boot-ai-mcp-server","category":"ai-ml","subcategories":[],"tags":["mcp","spring-boot","json-rpc","sse","agent-tools","crypto-news","sqlite","caffeine"],"what_it_does":"Provides a Spring Boot implementation of an MCP (Model Context Protocol) server exposing crypto/news-related tools (search/get latest news, token tracking, sentiment analysis) over HTTP (JSON-RPC) and SSE transports, with SQLite persistence and Caffeine caching.","use_cases":["Enable AI assistants to query crypto news and token sentiment via MCP tools","Provide lightweight local MCP endpoint for development/testing of agent tool use","Persist and retrieve tracked crypto tokens/news data"],"not_for":["Production-grade multi-tenant deployments requiring strong auth, audit controls, and strict rate limiting","Use as a general-purpose data platform outside crypto/news/token sentiment tooling","Publicly exposed endpoints without network-level protections"],"best_when":"You want a local or controlled environment MCP server for crypto news tool calling with simple HTTP/SSE integration.","avoid_when":"You need robust security controls (auth, scoped permissions) and well-specified operational guarantees (SLA, rate limit policy, error codes) for internet-facing use.","alternatives":["Use a hosted MCP server (if available) with proper production security and rate limiting","Build an MCP server in a framework with OpenAPI + formal auth (e.g., API gateway + OAuth2) and well-defined error contracts","Expose a REST API directly for tool use if MCP is not strictly required"],"af_score":52.8,"security_score":21.0,"reliability_score":22.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:59:38.024102+00:00","interface":{"has_rest_api":true,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":"http://localhost:8080/mcp/messages (HTTP JSON-RPC) and http://localhost:8080/mcp/v1/sse (SSE)","has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"README does not mention any authentication/authorization mechanism for MCP endpoints or any REST APIs."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided (appears to be a self-hosted open-source style project)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":52.8,"security_score":21.0,"reliability_score":22.5,"mcp_server_quality":70.0,"documentation_accuracy":55.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":100.0,"rate_limit_clarity":5.0,"tls_enforcement":20.0,"auth_strength":5.0,"scope_granularity":0.0,"dependency_hygiene":45.0,"secret_handling":45.0,"security_notes":"No authentication/authorization described for MCP endpoints; running over plain HTTP URLs in README (localhost examples) suggests TLS/auth are not addressed. SQLite local storage and logging are mentioned but no details on access controls, data protection, or secret handling. Dependency/security hygiene and CVE status cannot be confirmed from the provided content.","uptime_documented":10.0,"version_stability":30.0,"breaking_changes_history":30.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":"No explicit idempotency guidance for tools/calls in README; likely non-idempotent where tracking/persistence occurs (e.g., track_token).","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["SSE endpoint requires correct URL (/mcp/v1/sse) and session handling; README does not document session lifecycle/expiration behavior","If tools appear unavailable, README suggests initialization must be called first (agents should send initialize before tools/call)","No rate-limit or backoff behavior documented, so agents may need conservative retry strategies"]}}