Syracuse Company News
Structured company & industry news for AI agents: typed, dated, source-linked events.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"syracuse-mcp-server": {
"url": "https://syracuse.1145.am/mcp/"
}
}
}Remote endpoints
https://syracuse.1145.am/mcp/streamable-httpWhat it can do
Tool inventory
Tools (4)
🟢location_groups_list(page, page_size)
Location Groups are a way of grouping GeoNamesLocation entities into a simplified hierarchy. They start from top-level regions using the United Nations M49 standard (Region/Sub-Region/Intermediate Region). The US is further broken down United States Census Bureau regions (e.g. East/West etc) and then into individual states. Certain other countries are also broken down into their states/provinces: AE, CA, CN, IN.
Input Schema
{
"type": "object",
"properties": {
"page": {
"type": "integer",
"in": "query",
"description": "A page number within the paginated result set."
},
"page_size": {
"type": "integer",
"in": "query",
"description": "Number of results to return per page."
}
},
"required": []
}🔴register_and_get_key_create(email)
Creates a user account with the given email, sends a verification email, and returns an API token. Unverified users are limited to 30 queries/month; verified users can make 300/month for free. Drop us an email to tell us how you found the service and if you want more queries (see website footer)
Input Schema
{
"type": "object",
"properties": {
"email": {
"type": "string",
"description": "User email address",
"format": "email"
}
},
"required": [
"email"
]
}🟡stories_industry_location_list(activity_location, activity_location_id, include_provenance, industry, industry_context, ...)
Stories by Industry/Location Simplified endpoint that runs the same logic as the main stories endpoint, with a restricted parameter set (industry and the location the story happened in). Stories can either be -- IndustrySectorUpdate or activities in an organization's lifecycle. We track the following activities: -- CorporateFinanceActivity: M&A, investments, stock purchases -- PartnershipActivity: Partnership between 2 or more organizations. Often, companies describe their customers as their partners. This type of activity covers both genuine partnerships and customer/supplier relationships -- RoleActivity: Key change in senior personnel, e.g. replacing CEO -- LocationActivity: Opening or closing a new location (e.g. setting up in EMEA or shutting down a factory in a particular town) -- ProductActivity: New product launches -- AnalystRatingActivity: Updates from industry analysts -- EquityActionsActivity: Stock repurchases, dividends etc -- FinancialReportingActivity: Notice that an organization is going to announce its financials -- FinancialsActivity: Information about company financials, e.g. revenue or EBITDA -- IncidentActivity: Adverse incidents e.g. safety -- LegalActivity: Lawsuits or activities that could lead to lawsuits, e.g. SEC investigations -- MarketingActivity: e.g. launching a new advertising campaign -- OperationsActivity: Company operations news, e.g. we are investing in a new product, or we have just completed an security audit -- RecognitionActivity: e.g. we are delighted to announce that we won Agency of the Year -- RegulatoryActivity: Legal or regulatory activity affecting this organizationg e.g. permit for drilling, or regulatory filing Parameters: - activity_location: Location group name or id (e.g. "texas", "india", "MidWest", "FR", "us-ca") where the story happened. Not case sensitive. Accepts multiple values. They must each match an id or name from the [location groups](#/location-groups/location-groups_list) endpoint. - activity_location_id: Location group identifiers (e.g., "Southern Asia", "BT", "US-CA") where the story happened. Case-sensitive. Accepts multiple values. They must each match an id from the [location groups](#/location-groups/location-groups_list) endpoint. - include_provenance: Add a `source_audit` field to each story explaining how it was surfaced (source path, Typesense match score, and the entity that carried it). Defaults to false. - industry: Industry name to filter by. Accepts multiple values. - industry_context: Optional context aspects to anchor the industry search in. Pass each aspect as a separate value. Can be a broader category name or detailed examples (e.g. "Movie Industry" when searching for "Distribution", or "BOPP Film" and "BOPET Film" when searching for "Film"). Applied to every value of `industry` in the same request. - industry_id: Industry ID (topic ID) to filter by. Accepts multiple values. They must each match a topic_id from the [industry-clusters](#/industry-clusters/industry-clusters_list) endpoint. - location: Deprecated alias of `activity_location`, kept for backwards compatibility. It means the location the story happened in, not where the company is based. - location_id: Deprecated alias of `activity_location_id`, kept for backwards compatibility. It means the location the story happened in, not where the company is based. - output: Output format. Defaults to "simple" (SimpleStory schema). Use "full" for the detailed response. - page: A page number within the paginated result set. - page_size: Number of results to return per page.
Input Schema
{
"type": "object",
"properties": {
"activity_location": {
"type": "array",
"items": {
"type": "string"
},
"in": "query",
"description": "Location group name or id (e.g. \"texas\", \"india\", \"MidWest\", \"FR\", \"us-ca\") where the story happened. Not case sensitive. Accepts multiple values. They must each match an id or name from the [location groups](#/location-groups/location-groups_list) endpoint."
},
"activity_location_id": {
"type": "array",
"items": {
"type": "string"
},
"in": "query",
"description": "Location group identifiers (e.g., \"Southern Asia\", \"BT\", \"US-CA\") where the story happened. Case-sensitive. Accepts multiple values. They must each match an id from the [location groups](#/location-groups/location-groups_list) endpoint."
},
"include_provenance": {
"type": "boolean",
"in": "query",
"description": "Add a `source_audit` field to each story explaining how it was surfaced (source path, Typesense match score, and the entity that carried it). Defaults to false."
},
"industry": {
"type": "array",
"items": {
"type": "string"
},
"in": "query",
"description": "Industry name to filter by. Accepts multiple values."
},
"industry_context": {
"type": "array",
"items": {
"type": "string"
},
"in": "query",
"description": "Optional context aspects to anchor the industry search in. Pass each aspect as a separate value. Can be a broader category name or detailed examples (e.g. \"Movie Industry\" when searching for \"Distribution\", or \"BOPP Film\" and \"BOPET Film\" when searching for \"Film\"). Applied to every value of `industry` in the same request."
},
"industry_id": {
"type": "array",
"items": {
"type": "integer"
},
"in": "query",
"description": "Industry ID (topic ID) to filter by. Accepts multiple values. They must each match a topic_id from the [industry-clusters](#/industry-clusters/industry-clusters_list) endpoint."
},
"location": {
"type": "array",
"items": {
"type": "string"
},
"in": "query",
"description": "Deprecated alias of `activity_location`, kept for backwards compatibility. It means the location the story happened in, not where the company is based."
},
"location_id": {
"type": "array",
"items": {
"type": "string"
},
"in": "query",
"description": "Deprecated alias of `activity_location_id`, kept for backwards compatibility. It means the location the story happened in, not where the company is based."
},
"output": {
"type": "string",
"enum": [
"full",
"simple"
],
"in": "query",
"description": "Output format. Defaults to \"simple\" (SimpleStory schema). Use \"full\" for the detailed response."
},
"page": {
"type": "integer",
"in": "query",
"description": "A page number within the paginated result set."
},
"page_size": {
"type": "integer",
"in": "query",
"description": "Number of results to return per page."
}
},
"required": []
}🟡stories_organization_list(activity_location, activity_location_id, industry, industry_context, industry_id, ...)
Stories by Organization Simplified endpoint that runs the same logic as the main stories endpoint, with a restricted parameter set: `org_name`, optionally narrowed by where the company is based (`org_location`), what it does (`industry`), and where its stories happened (`activity_location`). Stories can either be -- IndustrySectorUpdate or activities in an organization's lifecycle. We track the following activities: -- CorporateFinanceActivity: M&A, investments, stock purchases -- PartnershipActivity: Partnership between 2 or more organizations. Often, companies describe their customers as their partners. This type of activity covers both genuine partnerships and customer/supplier relationships -- RoleActivity: Key change in senior personnel, e.g. replacing CEO -- LocationActivity: Opening or closing a new location (e.g. setting up in EMEA or shutting down a factory in a particular town) -- ProductActivity: New product launches -- AnalystRatingActivity: Updates from industry analysts -- EquityActionsActivity: Stock repurchases, dividends etc -- FinancialReportingActivity: Notice that an organization is going to announce its financials -- FinancialsActivity: Information about company financials, e.g. revenue or EBITDA -- IncidentActivity: Adverse incidents e.g. safety -- LegalActivity: Lawsuits or activities that could lead to lawsuits, e.g. SEC investigations -- MarketingActivity: e.g. launching a new advertising campaign -- OperationsActivity: Company operations news, e.g. we are investing in a new product, or we have just completed an security audit -- RecognitionActivity: e.g. we are delighted to announce that we won Agency of the Year -- RegulatoryActivity: Legal or regulatory activity affecting this organizationg e.g. permit for drilling, or regulatory filing Parameters: - activity_location: Location group name or id (e.g. "texas", "india", "MidWest", "FR", "us-ca") where the story happened. Not case sensitive. Accepts multiple values. They must each match an id or name from the [location groups](#/location-groups/location-groups_list) endpoint. - activity_location_id: Location group identifiers (e.g., "Southern Asia", "BT", "US-CA") where the story happened. Case-sensitive. Accepts multiple values. They must each match an id from the [location groups](#/location-groups/location-groups_list) endpoint. - industry: Industry name the company must work in. Narrows which companies match `org_name`. Accepts multiple values. - industry_context: Optional context aspects to anchor the industry search in. Pass each aspect as a separate value. Can be a broader category name or detailed examples (e.g. "Movie Industry" when searching for "Distribution", or "BOPP Film" and "BOPET Film" when searching for "Film"). Applied to every value of `industry` in the same request. - industry_id: Industry ID (topic ID) the company must belong to. Narrows which companies match `org_name`. They must each match a topic_id from the [industry-clusters](#/industry-clusters/industry-clusters_list) endpoint. - location: Deprecated alias of `activity_location`, kept for backwards compatibility. It means the location the story happened in, not where the company is based. - location_id: Deprecated alias of `activity_location_id`, kept for backwards compatibility. It means the location the story happened in, not where the company is based. - org_location: Location group name or id where the company is *based*. Narrows which companies match `org_name`, so it may only be used together with `org_name`. Not case sensitive. Accepts multiple values. For stories that happened in a place use `activity_location` instead. - org_location_id: Location group identifiers (e.g., "Southern Asia", "BT", "US-CA") where the company is *based*. Case-sensitive. May only be used together with `org_name`. - org_name: Filter by organization name (partial match). (required) - output: Output format. Defaults to "simple" (SimpleStory schema). Use "full" for the detailed response. - page: A page number within the paginated result set. - page_size: Number of results to return per page.
Input Schema
{
"type": "object",
"properties": {
"activity_location": {
"type": "array",
"items": {
"type": "string"
},
"in": "query",
"description": "Location group name or id (e.g. \"texas\", \"india\", \"MidWest\", \"FR\", \"us-ca\") where the story happened. Not case sensitive. Accepts multiple values. They must each match an id or name from the [location groups](#/location-groups/location-groups_list) endpoint."
},
"activity_location_id": {
"type": "array",
"items": {
"type": "string"
},
"in": "query",
"description": "Location group identifiers (e.g., \"Southern Asia\", \"BT\", \"US-CA\") where the story happened. Case-sensitive. Accepts multiple values. They must each match an id from the [location groups](#/location-groups/location-groups_list) endpoint."
},
"industry": {
"type": "array",
"items": {
"type": "string"
},
"in": "query",
"description": "Industry name the company must work in. Narrows which companies match `org_name`. Accepts multiple values."
},
"industry_context": {
"type": "array",
"items": {
"type": "string"
},
"in": "query",
"description": "Optional context aspects to anchor the industry search in. Pass each aspect as a separate value. Can be a broader category name or detailed examples (e.g. \"Movie Industry\" when searching for \"Distribution\", or \"BOPP Film\" and \"BOPET Film\" when searching for \"Film\"). Applied to every value of `industry` in the same request."
},
"industry_id": {
"type": "array",
"items": {
"type": "integer"
},
"in": "query",
"description": "Industry ID (topic ID) the company must belong to. Narrows which companies match `org_name`. They must each match a topic_id from the [industry-clusters](#/industry-clusters/industry-clusters_list) endpoint."
},
"location": {
"type": "array",
"items": {
"type": "string"
},
"in": "query",
"description": "Deprecated alias of `activity_location`, kept for backwards compatibility. It means the location the story happened in, not where the company is based."
},
"location_id": {
"type": "array",
"items": {
"type": "string"
},
"in": "query",
"description": "Deprecated alias of `activity_location_id`, kept for backwards compatibility. It means the location the story happened in, not where the company is based."
},
"org_location": {
"type": "array",
"items": {
"type": "string"
},
"in": "query",
"description": "Location group name or id where the company is *based*. Narrows which companies match `org_name`, so it may only be used together with `org_name`. Not case sensitive. Accepts multiple values. For stories that happened in a place use `activity_location` instead."
},
"org_location_id": {
"type": "array",
"items": {
"type": "string"
},
"in": "query",
"description": "Location group identifiers (e.g., \"Southern Asia\", \"BT\", \"US-CA\") where the company is *based*. Case-sensitive. May only be used together with `org_name`."
},
"org_name": {
"type": "string",
"minLength": 1,
"in": "query",
"description": "Filter by organization name (partial match)."
},
"output": {
"type": "string",
"enum": [
"full",
"simple"
],
"in": "query",
"description": "Output format. Defaults to \"simple\" (SimpleStory schema). Use \"full\" for the detailed response."
},
"page": {
"type": "integer",
"in": "query",
"description": "A page number within the paginated result set."
},
"page_size": {
"type": "integer",
"in": "query",
"description": "Number of results to return per page."
}
},
"required": [
"org_name"
]
}Community
Evidence