Loading ToolBench

Reading the current corpus…

langChain-travelAgent MCP server · F · ToolBench

langChain-travelAgent

github.com/wayde1122/langChain-travelAgent

A Next.js-based travel planning agent that uses LangChain, LLMs, and RAG to provide travel recommendations and itinerary planning

2026-07-28+STDIO1 tools

13/100

Definition Quality16

Protocol Readiness5

SupportabilityNot measured-

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · detected: Dynamic Client Registration

Deprecated protocol patterns detected

Summary

This is not an MCP server. The repository is a Next.js travel agent application using LangChain, not an MCP server implementation. The single tool 'currentDateTool' is a LangChain tool, not an MCP tool. No MCP protocol implementation is present. The codebase shows a chat UI (ToolCallSteps.tsx), Supabase integration, and LangChain dependencies (@langchain/mcp-adapters suggests MCP consumption, not serving). No tool schemas, descriptions, or MCP tool registration visible in provided source. The tool file reference (src/lib/langchain/tools/current-date.ts) is not included, so tool definition cannot be verified.

Tools (1)

currentDateToolread only20/100

Tool to get the current date

Issues (5)

CRITICALmcp-server-architecture ↗

Not an MCP server, this is a Next.js LangChain application, not an MCP server implementation

currentDateTool

CRITICALtool-definition ↗

Tool definition source file (src/lib/langchain/tools/current-date.ts) not provided, cannot verify schema, parameters, or descriptions

currentDateTool

CRITICALconstrained-input ↗

No input schema visible for currentDateTool, schema score must be 0

currentDateTool

HIGHtool-description ↗

Tool description provided ('Tool to get the current date') is only 27 characters, below 50-char minimum for LLM clarity

currentDateTool

HIGHmcp-transport ↗

No MCP protocol transport detected, STDIO-only servers are capped at 50 for protocol readiness

Recommendations

Clarify: is this repository intended to be an MCP server, or a client application that consumes MCP? The GitHub description and package.json suggest a LangChain travel agent UI, not an MCP server.
If converting to MCP server: implement proper MCP protocol with Tool definitions including input schemas (JSON Schema with type, description, properties, required fields) and output schemas.
Expand currentDateTool description from 27 chars to 50-200 chars. Example: 'Returns the current date in ISO 8601 format (YYYY-MM-DD). Use this when the user asks for today's date or when you need the current date for travel planning calculations.'
Add parameter descriptions and type constraints. Even a no-parameter tool should document its output schema (e.g., returns {date: string, timezone: string}).
If this is an MCP server, migrate from STDIO to HTTP+SSE or Streamable HTTP transport for remote accessibility and hosted client compatibility.

Score history

Overall score trend

First recorded score · v2 rubric

13/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	13	2026-07-28+	v2