mcp-go-sse-server

Implements an MCP server that communicates over Server-Sent Events (SSE). Provides example tools/resources/prompts, with a sample workflow based on an existing MCP Go example; optionally can run with different base URLs/transport options.

Evaluated Apr 04, 2026 (17d ago)
Repo ↗ DevTools mcp sse go ai-agents tooling streaming
⚙ Agent Friendliness
27
/ 100
Can an agent use this?
🔒 Security
37
/ 100
Is it safe for agents?
⚡ Reliability
24
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
35
Error Messages
0
Auth Simplicity
20
Rate Limits
0

🔒 Security

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

Based on available README content, authentication/authorization and rate limiting are not described. TLS usage depends on how the server is deployed (README examples include https baseurl). Additional review of the codebase is required for TLS enforcement, secret management, logging, and dependency vulnerabilities.

⚡ Reliability

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

Best When

You want a lightweight, Go-based MCP server reachable over HTTP(S) SSE for prototyping or internal tooling.

Avoid When

You cannot validate security controls (auth/rate limiting) or you require mature production operational guarantees from the package alone.

Use Cases

  • Expose MCP tools to an AI client over SSE transport
  • Prototype MCP toolsets (tools/resources/prompts) in Go
  • Use SSE-based connectivity for agent tool invocation from environments that work well with HTTP streaming

Not For

  • Production deployments requiring robust documented authentication/authorization
  • Use cases needing a published OpenAPI/SDK surface (this appears to be MCP-first, not REST-first)
  • Organizations needing strict reliability/SLA guarantees without additional operational validation

Interface

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

Authentication

Methods: none mentioned
OAuth: No Scopes: No

README provided does not describe any authentication mechanism for the SSE MCP server (based on available content).

Pricing

Free tier: No
Requires CC: No

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • SSE transport can be sensitive to proxy/load-balancer buffering and connection timeouts; agents may see disconnect/reconnect behavior if infrastructure is not configured for streaming.
  • No documented auth/rate limiting in the provided README content—agent deployments may require additional hardening not covered here.
  • Examples mention PostgreSQL/NATS on a branch, but available content does not describe operational behaviors (timeouts, retries, backpressure) for real integrations.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-go-sse-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