18 federal sources and 147 tools behind one MCP endpoint. HARBOR holds the upstream credentials, absorbs the rate limits and serves what we can from cache, so your agent keeps working when a government API does not.
Prefer to look first? Browse the sources →
Free tier, no card required. Create your key once you confirm your email.
HARBOR Port is Helm’s federal data layer. See the Helm page →
Example response. SAM.gov's daily ceiling is enforced before the call reaches the agency.
Connect to my HARBOR Port MCP server at https://port.harborgovcon.com/plugin/mcp and answer one question with live federal data. Add it as a remote HTTP MCP server and sign in with OAuth: if you can change your own configuration, do that and tell me when the browser opens so I can approve it, and if you cannot, tell me which settings screen to open and what to paste in, then wait for me. If neither works in your host, stop and tell me instead of guessing: there is more than one way in, and https://port.harborgovcon.com/llms.txt has the details. Call harbor_meta_ping and show me the result, which should say pong, then harbor_meta_list_servers and tell me how many sources I can reach. Then answer this from live federal data rather than a web search: in NAICS 541512, who won the most federal contract dollars in fiscal year 2026, is that market concentrated or fragmented, and how big is that federal market next to the industry as a whole? Use the usaspending tools for the federal side and the census tools for the industry. Put it on a single self-contained HTML page, dark and editorial rather than a dashboard.Copy it, paste it into your agent, and let the agent do the work: it adds the server itself, or names the screen you have to open. The browser prompt is the only part you approve by hand.
Different keys, different auth, different pagination, different limits. Wiring them together is a month of work that is not your product.
| Without HARBOR Port | With HARBOR Port |
|---|---|
| A separate key, signup and authentication scheme for every agency | One account and one connection across every federal source |
| Rate limits and 429 responses your agent has to handle itself | A fair share per tenant, with retries handled before the call reaches the agency |
| Raw payloads that consume your context window | Purpose built tools that return what the task actually needs |
| No MCP surface, so you write the glue yourself | Streamable HTTP MCP that works with Claude Code, Cursor and VS Code today |
Upstream government APIs are slow, rate limited and occasionally down. We absorb that so your agent does not have to.
Repeated queries come back from our cache instead of the source. Your agent gets an answer in milliseconds, and popular federal data stays fast for every account.
Per tenant limits and queued retries sit in front of every upstream call. One heavy account cannot starve the rest, and a slow agency does not become your timeout.
A bearer key or an OAuth connector on every endpoint. Issue a key per machine, revoke one without touching the others, and read usage per key from your dashboard.
Procurement, spending, regulatory, economic, energy, climate and health data. Same endpoint, same authentication, same response shape. The full tool list for every source lives in the documentation.
Every agency source proxies a public US government API, with its license terms enforced at the gateway. The catalogue includes HARBOR’s cross-source join layer, and one of the servers is a first-party account endpoint that never touches an upstream API. SAM.gov is premium and rationed, so it is arranged separately rather than bundled into a plan.
The five SAM.gov servers are in the procurement section below. Browse every tool →
Each source also has a focused endpoint at /servers/<slug>/mcp. Same endpoint, fewer tools loaded at once.
Five servers and 30 tools covering the federal procurement lifecycle end to end, from a sources sought notice to the award that closes it, plus the exclusion check that belongs before any teaming decision.
| Server | Tools | Endpoint |
|---|---|---|
| SAM.gov Agency Hierarchy Agency and sub-agency codes, the cross-API join key for every other federal dataset. |
4 | /servers/sam-federal-hierarchy/mcp |
| SAM.gov Contract Awards Contract award data (CDAS), the FPDS replacement. |
6 | /servers/sam-contract-awards/mcp |
| SAM.gov Entity Entity registration dossiers: the vendor side of the market. |
6 | /servers/sam-entity/mcp |
| SAM.gov Exclusions Debarment and exclusion records, a compliance gate before any teaming decision. |
5 | /servers/sam-exclusions/mcp |
| SAM.gov Opportunities The federal procurement firehose: pre-solicitations, solicitations, sources sought, awards. |
9 | /servers/sam-opportunities/mcp |
Helm is HARBOR’s governed AI platform for work that can’t leave. Its jobs run on federal data from Port, through the same endpoint your agent uses.
Helm job
Helm sweeps the day’s new federal notices for the NAICS codes the firm works in, then hands the team the notices worth a look. The sweep is one call against Port’s SAM.gov layer.
Helm job
Before a call, Helm pulls the public entity record into a one-page brief: registration, size, status and the identifiers a team needs. The brief starts with one dossier call.
Example calls. Sample arguments; the records are public.
Those jobs run on 18 federal sources and 147 tools from HARBOR Port, through the same endpoint your agent uses. Talk to the Helm engineer →
Start free. The free tier is the only plan on sale today; the paid plans are not available yet.
SAM.gov carries a strict upstream ceiling and a shared daily budget, so it is not bundled into any self-serve plan. It is arranged with us as an add-on today, and a paid account will be able to use its own SAM.gov key when the paid plans open.
Stated plainly so the wrong accounts disqualify themselves before support has to.
Not sure which workflow fits your question? The eighteen use cases name the inputs each one needs and the limits it carries.
The same path on every source: one handshake, one tool call shape from exploration to production.
Sign up and you are in. No sales call, and nothing to copy by hand if you would rather use a connector.
Add the gateway to your client and approve it once in the browser, or hand the whole job to your agent. The prompt is at the top of this page.
Start at the aggregate endpoint, or aim at a single source when you know the dataset you need.
The same gateway, registered by hand. Take a key from Keys and replace $HARBOR_KEY with it. A test key costs no plan quota while you wire things up.
claude mcp add --transport http harbor-port \
https://port.harborgovcon.com/mcp \
--header "Authorization: Bearer $HARBOR_KEY"{
"mcpServers": {
"harbor-port": {
"url": "https://port.harborgovcon.com/servers/usaspending/mcp",
"headers": { "Authorization": "Bearer \${env:HARBOR_KEY}" }
}
}
}{
"inputs": [{ "type": "promptString", "id": "harbor-key", "description": "HARBOR Port API key", "password": true }],
"servers": {
"harbor-port": {
"type": "http",
"url": "https://port.harborgovcon.com/servers/usaspending/mcp",
"headers": { "Authorization": "Bearer \${input:harbor-key}" }
}
}
}# MCP is session based. Initialize first and keep the session id, or every
# later request is rejected with "Missing session ID".
SID=$(curl -sD - -o /dev/null https://port.harborgovcon.com/servers/usaspending/mcp \
-H "Authorization: Bearer $HARBOR_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}' \
| tr -d '\r' | awk -F': ' 'tolower($1)=="mcp-session-id"{print $2}')
curl -s https://port.harborgovcon.com/servers/usaspending/mcp \
-H "Authorization: Bearer $HARBOR_KEY" \
-H "Mcp-Session-Id: $SID" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","method":"notifications/initialized"}'
curl -s https://port.harborgovcon.com/servers/usaspending/mcp \
-H "Authorization: Bearer $HARBOR_KEY" \
-H "Mcp-Session-Id: $SID" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"resolve_recipient_id","arguments":{"name":"accenture"}}}'/mcp exposes the
full catalogue, which is the fastest way to explore. Once you know which dataset you need, point at that single
source at /servers/<slug>/mcp. A shorter tool list is measurably more reliable for tool
selection and costs less context. Both work with the same bearer key.
Calls beyond your rolling 24 hour limit return a tool error naming the limit, and nothing is charged as overage. The hourly cap exists to stop a runaway loop. The daily cap is the budget you bought.
No. Every source proxies a public US government API. HARBOR Port is not affiliated with, endorsed by or acting for any agency, and attribution notices travel with the data.
It depends on each source license, and the answer is enforced per source rather than applied as one policy. Where terms permit caching we serve from cache. Where they do not, the request passes through live and we retain nothing.
SAM.gov is the deepest procurement dataset we carry, and it caps how much any account may draw each day. We ration it accordingly, and no self-serve plan bundles it. It is arranged with us as an add-on today; a paid account will be able to attach its own SAM.gov API key when the paid plans open. Talk to us and we will size it with you.
Yes, subject to each source terms. The license conditions are enforced at the gateway before data leaves it, per source.
We publish live status rather than a number we have not measured. Support response times will be stated with each paid plan when the paid plans open, and a formal availability commitment comes once there is a measured history behind it.
There is nothing to cancel on the free tier. The paid plans are not available yet; their cancellation terms will be stated before they go on sale, and the free tier stays real access rather than a demo.
Not yet: the paid plans are not on sale. When they open, annual billing and invoicing will be offered on the Team plan and above; ask us then.
Create an account, confirm your email, and your first key is on the dashboard. No card, and the free tier is real access rather than a demo.