HARBOR Port

com.harborgovconPublished by harborgovcon.comOfficial publisherv0.29.0Updated Oct 24, 2026

Hosted MCP servers for US federal data: 19 servers, 147 tools, one endpoint.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Hosted MCP endpoint that gives an assistant access to US federal data through 19 servers and 147 tools over one connection.

What you can do
  • Access US federal data through a single hosted endpoint.
  • Work across 19 bundled servers exposing 147 tools, grouped by agency or dataset.
  • Query public government datasets without installing anything locally.
When to use it
Useful when an assistant needs to look up or work with US federal government data and you want one hosted connection instead of several separate servers.
Requirements
A remote streamable HTTP endpoint; no local package or runtime. OAuth 2.1 authentication is required, passed as an Authorization header; a static bearer API key is accepted for scripts and CI. Connectors discover the authorization server from the 401 WWW-Authenticate header.
Before you install
The connection requires an OAuth access token or bearer API key in the Authorization header, so treat that credential as a secret. The manifest lists no tools, so review what the 19 bundled servers actually expose before relying on them. Requests go to a third-party hosted service.

Installation

In SourceWeft

  1. Open HARBOR Port in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.harborgovcon%2Fport/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "harbor-port": {
      "type": "http",
      "url": "https://port.harborgovcon.com/plugin/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.29.0LatestOct 11, 2026
  2. v0.4.0Sep 27, 2026

Score

60% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.