freshfilings-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRESHFILINGS_API_KEY | Yes | Your FreshFilings API key | |
| FRESHFILINGS_BASE_URL | No | Override API base URL | https://freshfilings.dev/api/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_businessesC | Search for businesses by name across NY, FL, and CO state filings. |
| get_business_detailB | Get full details for a business including officers, addresses, and registered agent. |
| get_new_formationsB | Get businesses formed since a given date (YYYY-MM-DD). Useful for sales prospecting. |
| check_usageA | Check your FreshFilings API key usage and remaining calls this month. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: check_usage for API limits, get_business_detail for full business info, get_new_formations for date-based listings, search_businesses for name search. No overlap or ambiguity.
All tools use consistent snake_case verb_noun pattern (check_usage, get_business_detail, get_new_formations, search_businesses). The naming is predictable and clear.
4 tools are well-scoped for a business filings API covering search, detail retrieval, date-based listing, and usage monitoring. It's neither too few nor too many.
The domain of business filings is adequately covered for read operations. Missing advanced filtering (e.g., by state or entity type) but core prospecting workflows are supported.