FIRMSapi
REMOTE · API.FIRMSAPI.COM
Look up, search and validate U.S. CBP FIRMS facility codes for piers, CFS, warehouses and FTZs.
Available components
Last scanned (4 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 30 Oct 26 +1
- Tool coverage: 74% → 100% ▲ functional
- Schema quality: good → excellent functional
- “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” cosmetic
- 29 Oct 26 +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.
- 27 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.firmsapi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.firmsapi.com | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 25 Oct 2026 | 10 May 2027 | RSA 2048 | SHA256-RSA | a954007558d1799a2256813fa0a28e1 |
| SANs: api.firmsapi.com | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.firmsapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| firmsapi.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.firmsapi.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.firmsapi.com/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_nearby_firms_facilities Find facilities near a point, code or address ~357
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
No output schema declared.
No examples provided.
get_cbp_port Get a CBP port and its facilities ~255
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
No output schema declared.
No examples provided.
list_cbp_ports List CBP ports ~75
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_firms_code Look up a FIRMS code ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | 4-character FIRMS code, e.g. E430. |
No output schema declared.
No examples provided.
search_firms_facilities Search facilities by name or address ~279
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
No output schema declared.
No examples provided.
validate_firms_code Check a FIRMS code before filing ~279
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · api.firmsapi.com
claude mcp add --transport http com-firmsapi-mcp 'https://api.firmsapi.com/mcp'
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.