Other · Remote MCP server
Vepathos
Import orders, manage your fleet, and generate optimized last-mile delivery routes at scale.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.vepathos/vepathos- Version
- 0.11.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-24
- Updated
- 2026-09-24
- Publisher
- com.vepathos
- Namespace
- Namespace verified by the MCP Registry via the domain vepathos.com · how
- Website
- vepathos.com
- Repository
- github.com/vizzito/vepathos-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.vepathos.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Vepathos
Vepathos is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.vepathos.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, vepathos.com, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More other servers
| Server | Runs |
|---|---|
| Vendor Clearance AuditFree to compete: testnet faucet funds everything. Audit supplier rollout readiness. | Remote · HTTPLive check: ✓ handshake |
| Vendor SignalsVendor documentation and changelog change-tracking as ACCOUNT SIGNALS. | Remote · HTTPLive check: ✓ handshake |
| VenmoMCP server for Venmo - check balance, send/request money, view history. | Local · stdio |
| Venues AbroadWedding venues and planners in Portugal: capacity, rooms, catering, each fact with its source. | Remote · HTTPLive check: ✓ handshake |
| VeraciumProvenance-aware memory for AI agents: quarantine, abstention gate, supersession-with-history. | Local · stdio |
| Veracrypt MCPMCP server to mount and unmount VeraCrypt containers with secure stdin password handling. | Local · stdio |
| VERAXThe body an agent asks before it acts: decide, approve, and keep a signed record on your machine. | Local · HTTP |
| Verdict QARead-only MCP server over Verdict QA state: verdicts, findings, flaky quarantine, history. | Local · stdio |