mcp-go-server-ak

An MCP-compatible (per description) Go server that exposes vector search functionality backed by Pinecone for storage/indexing and OpenAI for embeddings/processing. It also includes a health endpoint, search/index endpoints, and authentication endpoints under /auth/* (with optional GitHub OAuth for development and an MCP secret token).

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ Ai Ml mcp vector-search pinecone openai go api-server
⚙ Agent Friendliness
32
/ 100
Can an agent use this?
🔒 Security
38
/ 100
Is it safe for agents?
⚡ Reliability
20
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
35
Documentation
45
Error Messages
0
Auth Simplicity
50
Rate Limits
0

🔒 Security

TLS Enforcement
20
Auth Strength
45
Scope Granularity
20
Dep. Hygiene
30
Secret Handling
70

README recommends using environment variables for API keys and notes .env is gitignored, which helps secret handling. However, TLS enforcement, transport security requirements, authorization model details (scopes/roles), and error/response handling guidance are not documented. JWT and an optional MCP secret token are mentioned, but strength and configuration requirements are unclear.

⚡ Reliability

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

Use Cases

  • Agent/MCP integration for querying a Pinecone-backed vector index
  • Indexing/updating vector documents (POST /index)
  • Semantic search over embedded content (POST /search)
  • Providing a local or internal service that wraps Pinecone + OpenAI behind an HTTP interface for agents

Not For

  • Production deployments without verifying authentication, TLS, and operational hardening
  • Use as a general-purpose API without clear request/response schemas (not provided in README)
  • Environments that cannot send data/queries to OpenAI and Pinecone

Interface

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

Authentication

Methods: JWT-based auth (JWT_SECRET env var) MCP secret token (MCP_SECRET_TOKEN env var, optional) Optional GitHub OAuth for development (/auth/*, GitHub_* env vars)
OAuth: Yes Scopes: No

README indicates JWT_SECRET and optional GitHub OAuth settings for development. It does not document token formats, validation rules, authorization granularity, or how /auth/* endpoints are secured.

Pricing

Free tier: No
Requires CC: No

No pricing information for the server itself is provided; costs would be driven by Pinecone and OpenAI usage.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • MCP/tool contract details (tool names, input/output schemas, auth method for MCP) are not included in the provided README, so agent integration may require source inspection.
  • API request/response formats for /search and /index are not documented here, making it harder for an agent to construct correct payloads.
  • Rate limiting behavior is not documented.
  • The service depends on external APIs (Pinecone/OpenAI); failures may require agent retry/backoff, but retry guidance and error codes are not described.

Alternatives

Full Evaluation Report

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

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