← Back to Check

medterms-mcp

https://medterms.mcpize.run

Scanned May 8, 2026

F30/100
Clarity
0
Protocol
33
Auth
0
Reliability
38
Trust
51
Safety
87
Market
30

Upgrade available

Your server uses protocol 2025-06-18. The latest version is 2025-11-25 with session management, origin validation, and notification support.

Strengths & Weaknesses

Clarity (0)Protocol (33)Auth (0)Reliability (38)Trust (51)Safety (87)Market (30)

Top Issues

16 found
CRITICAL

Cannot enumerate tools — tools/list request failed

Server does not reject invalid MCP-Protocol-Version header.

Server does not reject malformed JSON-RPC requests.

Server crashed on DELETE request (returned 500).

HIGH

Could not measure latency — ping requests failed.

Server does not return valid JSON-RPC response to POST requests.

HIGH

Server cannot handle concurrent requests.

HIGH

Could not verify session persistence — request failed.

Server does not validate Origin header — potential CSRF risk.

Server does not return 202 for JSON-RPC notifications.

Server does not return proper JSON-RPC error format.

MEDIUM

Response time: Latency measurement failed: MCP request timed out after 15000ms

MEDIUM

Custom domain: Default hosting subdomain

MEDIUM

Error quality: Error format check failed: MCP request timed out after 15000ms

MEDIUM

No authentication required — server is open to anonymous access, which may be intentional for public tools

MEDIUM

Multiple similar MCP servers exist. Consider differentiating with unique features.

Protocol & Capabilities

Transport:Streamable HTTP
Protocol:2025-06-18
SSE Support:No
Session ID:Yes
Protocol Checks
Ping

Server responded to ping

Session ID

Valid Mcp-Session-Id assigned (36 chars)

Version Header Validation

Server returned 200 for invalid protocol version (expected 400)

JSON-RPC Validation

Error testing JSON-RPC validation: Signal timed out.

Origin Header

Error testing origin validation: Signal timed out.

Session Termination (DELETE)

Error testing DELETE: Signal timed out.

Notification Handling (202)

Error testing notification: Signal timed out.

!
Server Info

Server info: name, version

Server Capabilities
Tools
Resources
Prompts
Completions
Tasks
Logging

Auth

No OAuth? That's OK

OAuth is optional, but consider it for production deployments to protect your server from unauthorized access.

Trust

Latency: 15000ms
HTTPS
Default hosting subdomain
Name: medterms-mcp, Version: 1.0.0
Structured errors

Market

UniquenessCan it be done with an LLM alone?
5/10

No tools to assess

OriginalityHow many similar servers exist?
1/10

5+ similar servers — crowded space

DemandHow broad is the audience?
5/10

Moderate audience size estimated

Competitors found

6 Model Context Protocol alternatives to consider in 2026 - Merge

LangChain and LangGraph are development frameworks that can integrate with MCP servers through adapters, treating them as tools in their ecosystem. This creates ...

a safer, more scalable tool-calling alternative to MCP - Reddit

I'm building UTCP (Universal Tool Calling Protocol), an open standard for AI agents to call tools directly. The core idea is to eliminate the wrapper tax and ...

Context7 MCP Alternatives - Gopher Security

Explore secure alternatives to Context7 MCP for AI coding assistants. Discover options like Bright Data, Chrome DevTools, and Sequential ...

5 Essential MCP Servers Every Developer Should Know - Medium

5 Essential MCP Servers Every Developer Should Know · 1. Artiforge.ai · 2. Filesystem · 3. GitHub · 4. Sequential Thinking · 5. Fetch.

Top 10 MCP Alternatives: Connect Everything in 2025 - O-mega.ai

Discover 10 powerful MCP alternatives for connecting AI to everything - from ChatGPT plugins to autonomous agents and unified APIs in 2025.

Publish on MCPize

Get OAuth, billing, and discovery for free. Your server scored F — developers are looking for this.

Get Started →