Inventory

com.oceanbuildersPublished by oceanbuilders.comOfficial publisherv1.0.0Updated Oct 24, 2026

Search Ocean Builders' floating-home inventory, get unit specs and pricing, register buyer interest.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Lets an assistant search Ocean Builders' floating-home inventory, retrieve unit specs and pricing, and register a prospective buyer's interest with the sales团队.

What you can do
The server exposes Ocean Builders' floating-home inventory to an assistant, so it can look up available units along with their specifications and pricing. Its documented tool, submit_inquiry, registers a prospective buyer's interest with the Ocean Builders sales team, requiring the buyer's real name and email and their consent to be contacted. The team then follows up by email, and the tool returns a neutral acknowledgment.
When to use it
Useful when someone is exploring Ocean Builders floating homes and wants an assistant to check units, specs and pricing, or to pass their contact details to the sales team for a follow-up.
Requirements
A remote endpoint at app.oceanbuilders.com over streamable HTTP; no packages, environment variables or headers are declared. No authentication is declared.
Before you install
submit_inquiry sends the buyer's real name and email to Ocean Builders and asks for consent to be contacted, so personal data leaves the conversation and the sales team may email the buyer. Confirm consent before submitting.

Installation

In SourceWeft

  1. Open Inventory in the dashboard and add it to a workspace.
  2. 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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.oceanbuilders%2Finventory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "inventory": {
      "type": "http",
      "url": "https://app.oceanbuilders.com/mcp"
    }
  }
}

Tools

1

submit_inquiry

Register a buyer inquiry with the sales team

Registers a prospective buyer's interest with the Ocean Builders sales team. Requires the buyer's real name and email (with their consent to be contacted); the team follows up by email. Returns a neutral acknowledgment.

Parametersnamerequiredemailrequiredphonemessagewebsiteelapsed_ms

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.