Enterprise DNA
M MCP Servers Developer low

vessel-api/vesselapi-mcp

by Various

Model Context Protocol server providing tools to access VesselAPI endpoints

V

MCP

vessel-api/vesselapi-mcp

Added 1 June 2026

Overview

An MCP server that exposes VesselAPI endpoints as tools for AI agents. It implements the Model Context Protocol so agents can invoke web data extraction, browsing, and other VesselAPI actions through a standardized interface.

Best for

Best for
Developers building MCP‑based AI agents that need programmatic access to web data or browser automation via VesselAPI

Use cases

  • Enable an AI agent to scrape or extract structured data from web pages via VesselAPI
  • Give agents the ability to fill forms or interact with web applications through browser automation endpoints
  • Integrate VesselAPI's data enrichment capabilities into a Claude or other MCP‑compatible agent workflow

Notes

An MCP server that exposes VesselAPI endpoints as tools for AI agents. It implements the Model Context Protocol so agents can invoke web data extraction, browsing, and other VesselAPI actions through a standardized interface.

0 stars on GitHub. Last updated 2026-05-23. Licensed MIT.

Use cases

  • Enable an AI agent to scrape or extract structured data from web pages via VesselAPI
  • Give agents the ability to fill forms or interact with web applications through browser automation endpoints
  • Integrate VesselAPI’s data enrichment capabilities into a Claude or other MCP‑compatible agent workflow

Pros

  • Simple drop‑in integration for any MCP‑compatible AI agent or host
  • Eliminates the need to write custom API wrappers for VesselAPI
  • Leverages a well‑defined protocol for tool discovery and invocation

Cons

  • Tied to VesselAPI’s availability, pricing, and endpoint coverage
  • Latency and reliability depend on the external VesselAPI service
  • Limited to actions that VesselAPI exposes; not a general‑purpose browsing tool

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Simple drop‑in integration for any MCP‑compatible AI agent or host
  • Eliminates the need to write custom API wrappers for VesselAPI
  • Leverages a well‑defined protocol for tool discovery and invocation

Cons

  • Tied to VesselAPI's availability, pricing, and endpoint coverage
  • Latency and reliability depend on the external VesselAPI service
  • Limited to actions that VesselAPI exposes; not a general‑purpose browsing tool