Neptivum
com.crowfoundryv1.0.0Updated Oct 8, 2026
Manage sailing logs, trips, boats, sharing, attachments, and account entitlements.
Overview
AI-generated overview
Lets an assistant manage sailing logs, trips, boats, sharing, attachments, and account entitlements through a hosted remote endpoint.
- What it does
- Neptivum is a remote MCP server for sailing-related record keeping. According to its registry description, it covers sailing logs, trips, boats, sharing, attachments, and account entitlements. No individual tools are listed in the manifest, so the exact operations available are not documented here.
- When to use it
- Consider it when an assistant should work with sailing logs and trip records, boat details, shared content, or attachments held in a Neptivum account. It is not useful if you do not use that service.
- Requirements
- A remote streamable HTTP endpoint at api.neptivum.com; nothing is installed locally. Authentication is required: an Authorization header carrying a Bearer OAuth access token or scoped API key, obtained through the product's browser sign-in flow. Network access to the endpoint is needed.
Before you install
The Authorization header is a secret credential; treat the token or API key as sensitive and grant only the scopes needed. The description mentions sharing and attachments, so the server may expose or change data visible to others. No payment or wallet behavior is described.
Installation
In SourceWeft
- Open Neptivum in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"neptivum": {
"type": "http",
"url": "https://api.neptivum.com/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 8, 2026

