io.github.1145-am/syracuse-mcp-server

Official4 tools

by 1145-am · Python

Syracuse Company News

Structured company & industry news for AI agents: typed, dated, source-linked events.

Retrieve structured company and industry news with timestamps and sources.

Captured live from the server via tools/list.

location_groups_list

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.

Parameters (2)

pageinteger
A page number within the paginated result set.
page_sizeinteger
Number of results to return per page.

register_and_get_key_create

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)

Parameters (1)

emailstringrequired
User email address

stories_industry_location_list

Stories by Industry/Location Simplified endpoint that runs the same logic as the main stories endpoint, with a restricted parameter set (only industry and 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: - 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 (e.g. "Packaging" when searching for "Rigid Metal"). Applied to every value of `industry` in the same request. - location: Location group name or id (e.g. "texas", "india", "MidWest", "FR", "us-ca"). Not case sensitive. Accepts multiple values. They must each match an id or name from the [location groups](#/location-groups/location-groups_list) endpoint. - 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.

Parameters (7)

include_provenanceboolean
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.
industryarray
Industry name to filter by. Accepts multiple values.
industry_contextarray
Optional context aspects to anchor the industry search in. Pass each aspect as a separate value (e.g. "Packaging" when searching for "Rigid Metal"). Applied to every value of `industry` in the same request.
locationarray
Location group name or id (e.g. "texas", "india", "MidWest", "FR", "us-ca"). Not case sensitive. Accepts multiple values. They must each match an id or name from the [location groups](#/location-groups/location-groups_list) endpoint.
outputstring
Output format. Defaults to "simple" (SimpleStory schema). Use "full" for the detailed response.
pageinteger
A page number within the paginated result set.
page_sizeinteger
Number of results to return per page.

stories_organization_list

Stories by Organization Simplified endpoint that runs the same logic as the main stories endpoint, with a restricted parameter set (only org_name). 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: - 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.

Parameters (4)

org_namestringrequired
Filter by organization name (partial match).
outputstring
Output format. Defaults to "simple" (SimpleStory schema). Use "full" for the detailed response.
pageinteger
A page number within the paginated result set.
page_sizeinteger
Number of results to return per page.

README.md3 KBView on GitHub

Syracuse Company New MCP Server

Installation notes

API Key

Get a free API key from syracuse.1145.am - all you need to provide is your email address. Here is a curl command to do so:

code

curl -X POST "https://syracuse.1145.am/api/v1/register-and-get-key/" \
  -H "Content-Type: application/json" \
  -d "{\"email\":\"your_email@example.com\"}"

You'll get a low usage level until you confirm the key, so make sure to use an email address that you have access to.

Using the MCP Server

There are 3 options:

Run as a Local MCP Server (e.g. to connect with Claude Desktop)
Connect via the Syracuse MCP server
Run your own Remote MCP Server locally

To run as Local MCP Server

Pre-req: Install uv

Clone this repo
Copy .env.sample to .env and configure your MCP_SERVER_API_TOKEN with the API key you got above
Example claude_desktop_config.json

code

{
  "mcpServers": {
    "Syracuse Company News API": {
      "command": "/path/to/uv",
      "args": [
        "--directory",
        "/path/to/repo/syracuse-mcp-server",
        "run",
        "stdio_mcp_server.py"
      ]
    }
  }
}

To connect via Syracuse's MCP Server

There are no special pre-requisites

Connect to https://syracuse.1145.am/mcp and provide your key as part of the authorization

MCP doc is at https://syracuse.1145.am/.well-known/mcp.json

Running your own Remote MCP Server

If, for some reason, you want to run your own local MCP server then that is also possible. Again, it expects uv.

You don't need to update your key in the .env file, but you do need to:

Clone this repo
Copy .env.sample to .env - though any further configuration is not needed
Run it with uv run stateless_streaming_http_mcp_server.py

Connection info for MCP Inspector:

Transport Type: Streamable HTTP
URL: host:port/mcp, e.g. http://127.0.0.1:9000/mcp
Anyone making calls that require authorization will need to add their API key in the Authentication section

The Stateless Streaming MCP Server also serves an mcp.json at .well-known/mcp.json (in this example it would be http://127.0.0.1/.well-known/mcp.json )

Allowed tools

By default the ALLOWED_TOOLS restricts the MCP server to the minimum needed to register accounts and get stories:

register_and_get_key
location_groups_list
stories_industry_location_list
stories_organization_list

There's no problem to allow all tools - if you'd like to experiment simply remove ALLOWED_TOOLS from .env

Distinguishing tools that need auth

Each tool is tagged with whether it requires authentication, derived from the OpenAPI security rules (an operation's security overrides the spec-level security, and an explicit empty security: [] means no auth). This is exposed two ways:

In tools/list, each tool carries _meta: { "requiresAuth": true | false }.
In .well-known/mcp.json, the same _meta flag is present, and the security block is only attached to tools that actually require auth.

Clients can use this to call public endpoints without prompting the user for a token, and only request credentials for tools that need them.

Install

claude_desktop_config.json

{
  "mcpServers": {
    "syracuse-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://syracuse.1145.am/mcp/"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.