# FIRMSapi (remote · api.firmsapi.com)

Look up, search and validate U.S. CBP FIRMS facility codes for piers, CFS, warehouses and FTZs.

- Trust score: 73/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.firmsapi.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-firmsapi-mcp/api.md), [page](https://verifymcp.io/servers/com-firmsapi-mcp/api)

## Channel facts

- Endpoint: `https://api.firmsapi.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1616 tokens (~269/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the FIRMSapi MCP server?

FIRMSapi is a hosted endpoint at https://api.firmsapi.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-firmsapi-mcp 'https://api.firmsapi.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-firmsapi-mcp": {
      "url": "https://api.firmsapi.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-firmsapi-mcp": {
      "type": "http",
      "url": "https://api.firmsapi.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-firmsapi-mcp]
url = "https://api.firmsapi.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-firmsapi-mcp": {
      "type": "remote",
      "url": "https://api.firmsapi.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-firmsapi-mcp --url 'https://api.firmsapi.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-firmsapi-mcp:
    url: "https://api.firmsapi.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-firmsapi-mcp": {
      "Transport": "http",
      "Url": "https://api.firmsapi.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-firmsapi-mcp -t streamable-http -u 'https://api.firmsapi.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-firmsapi-mcp": {
      "type": "http",
      "url": "https://api.firmsapi.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 70, +1)

- [functional improvement] Tool coverage: 74% → 100%
- [functional] Schema quality: good → excellent
- [cosmetic] “find_nearby_firms_facilities” reworded the description of “lat”
- [cosmetic] “find_nearby_firms_facilities” reworded the description of “limit”
- [cosmetic] “find_nearby_firms_facilities” reworded the description of “lon”
- [cosmetic] “find_nearby_firms_facilities” reworded the description of “radius_km”
- [cosmetic] “get_cbp_port” reworded the description of “cursor”
- [cosmetic] “get_cbp_port” reworded the description of “limit”
- [cosmetic] “search_firms_facilities” reworded the description of “limit”

### 2026-10-29 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 68)

First indexed and scored.

## MCP tools (6)

### `lookup_firms_code` (~150 tokens)

Look up a FIRMS code

Get the CBP FIRMS record for one code: facility name, status (active or deleted), facility type, address, CBP port, location, and the other codes registered at the same address. Deleted codes and "DO NOT USE" placeholders (junk: true) are returned with warnings. A code that is not on the list returns a not_found error, which still counts as a call. Wraps GET /v1/firms/{code}. Live keys (fapi_live_...): one counted call. Test keys (fapi_test_...): fixture sample data, not counted.

Input parameters:

- `code` (string, required): 4-character FIRMS code, e.g. E430.

### `search_firms_facilities` (~279 tokens)

Search facilities by name or address

Find FIRMS codes from a facility name and/or street address, e.g. 'maher terminal elizabeth' or '231 tyler st newark'. Typo-tolerant; returns ranked matches with a 0-100 score. Active codes only unless include_deleted is true. One call per search, however many results. Wraps GET /v1/search. Live keys (fapi_live_...): one counted call. Test keys (fapi_test_...): fixture sample data, not counted.

Input parameters:

- `include_deleted` (boolean): Include deleted codes (ranked after active ones).
- `limit` (integer): Most matches to return.
- `port` (string): 4-digit CBP port code, e.g. 4601.
- `query` (string, required): Name and/or address.
- `state` (string): 2-letter state, e.g. NJ.
- `types` (array): Only these facility types: 01 Container freight station (CFS), 02 Foreign trade zone (FTZ), 03 Pier or terminal, 04 Bonded warehouse, 05 Inspection facility, 06 Importer premises, 07 DP site, 08 CBP…

### `find_nearby_firms_facilities` (~357 tokens)

Find facilities near a point, code or address

List FIRMS facilities within radius_km, nearest first. Pass exactly one origin: lat and lon; code (another FIRMS facility, left out of the results); or address (a US street address, geocoded unless it is a FIRMS facility's own address). meta.origin says which point was used. Facilities whose address could not be geocoded are not included. Test keys use approximate coordinates. Wraps GET /v1/nearby. Live keys (fapi_live_...): one counted call. Test keys (fapi_test_...): fixture sample data, not counted.

Input parameters:

- `address` (string): Search around this US street address, e.g. 231 Tyler St, Newark, NJ 07114.
- `code` (string): Search around this FIRMS code.
- `include_deleted` (boolean): Include deleted codes (ranked after active ones).
- `lat` (number): Origin latitude in decimal degrees, e.g. 40.68. Pass with lon.
- `limit` (integer): Most facilities to return.
- `lon` (number): Origin longitude in decimal degrees, e.g. -74.15. Pass with lat.
- `radius_km` (number): Search radius in km around the origin.
- `types` (array): Only these facility types: 01 Container freight station (CFS), 02 Foreign trade zone (FTZ), 03 Pier or terminal, 04 Bonded warehouse, 05 Inspection facility, 06 Importer premises, 07 DP site, 08 CBP…

### `validate_firms_code` (~279 tokens)

Check a FIRMS code before filing

Pre-filing checks of a FIRMS code against the published CBP list, in order: format, exists (catches ACE reject 158), active (159), in the stated port (164), facility type fits the use (warehouse_entry: bonded warehouse 04; ftz_admission: FTZ 02; exam_site: CES 09; location_of_goods: not 07 or 08), not a placeholder. Returns valid, checks_passed, checks_failed, checks_skipped, checks_not_possible (bond status, FTZ zone ID, direct delivery, port clusters: not in the FIRMS list) and a note. valid: true is not ACE acceptance: FIRMSapi has no ACE connection, so confirm in ACE before filing. A failing code is a normal result (valid: false) and counts as a call. Wraps POST /v1/validate. Live keys (fapi_live_...): one counted call. Test keys (fapi_test_...): fixture sample data, not counted.

Input parameters:

- `code` (string, required): The code as it appears in your system. A malformed code is a failed check.
- `port` (string): 4-digit CBP port of entry of the filing.
- `use` (string): How the code will be used; enables the facility type check.

### `list_cbp_ports` (~75 tokens)

List CBP ports

Every CBP port that has FIRMS codes, with name, state, region, facility_count and active_count, in one call. Wraps GET /v1/ports. Live keys (fapi_live_...): one counted call. Test keys (fapi_test_...): fixture sample data, not counted.

### `get_cbp_port` (~255 tokens)

Get a CBP port and its facilities

One CBP port with a page of its FIRMS facilities, ordered by code. Placeholders are left out; active codes only unless include_deleted is true. For the next page pass cursor = meta.next_cursor (null on the last page); each page is one call. Wraps GET /v1/ports/{port}. Live keys (fapi_live_...): one counted call. Test keys (fapi_test_...): fixture sample data, not counted.

Input parameters:

- `cursor` (string): meta.next_cursor from the previous page.
- `include_deleted` (boolean): Include deleted codes (ranked after active ones).
- `limit` (integer): Facilities per page.
- `port` (string, required): 4-digit CBP port code, e.g. 4601.
- `types` (array): Only these facility types: 01 Container freight station (CFS), 02 Foreign trade zone (FTZ), 03 Pier or terminal, 04 Bonded warehouse, 05 Inspection facility, 06 Importer premises, 07 DP site, 08 CBP…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-firmsapi-mcp/api#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 68
- 2026-10-27: 68
- 2026-10-26: 68

## Common questions

### What is the FIRMSapi MCP server?

FIRMSapi is an MCP server listed in the public MCP registry as com.firmsapi/mcp. Look up, search and validate U.S. CBP FIRMS facility codes for piers, CFS, warehouses and FTZs. This page covers its hosted endpoint (https://api.firmsapi.com/mcp).

### Is the FIRMSapi MCP server safe to use?

FIRMSapi scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the FIRMSapi MCP server expose?

FIRMSapi exposes 6 tools: lookup_firms_code, search_firms_facilities, find_nearby_firms_facilities, validate_firms_code, list_cbp_ports, get_cbp_port. Their descriptions and schemas cost roughly 1,395 tokens of context every time the server is loaded.

### Does the FIRMSapi MCP server require authentication?

No. We connected to FIRMSapi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the FIRMSapi MCP server still maintained?

FIRMSapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.firmsapi.com/mcp
- Authorisation metadata: https://api.firmsapi.com/.well-known/oauth-protected-resource/mcp
- Website: https://docs.firmsapi.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-firmsapi-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-firmsapi-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/com-firmsapi-mcp/api