io.github.1145-amPublished by GitHub account 1145-amv1.2.0Updated Oct 24, 2026
Structured company & industry news for AI agents: typed, dated, source-linked events.
Remote MCP server giving assistants structured, dated, source-linked company and industry news, plus location groups and free API key registration.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.1145-am%2Fsyracuse-mcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"syracuse-company-news": {
"type": "http",
"url": "https://syracuse.1145.am/mcp/"
}
}
}Installation notes
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:
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.
There are 3 options:
Pre-req: Install uv
.env.sample to .env and configure your MCP_SERVER_API_TOKEN with the API key you got aboveThere 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
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:
.env.sample to .env - though any further configuration is not neededuv run stateless_streaming_http_mcp_server.pyConnection info for MCP Inspector:
http://127.0.0.1:9000/mcpThe 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 )
By default the ALLOWED_TOOLS restricts the MCP server to the minimum needed to register accounts and get stories:
There's no problem to allow all tools - if you'd like to experiment simply remove ALLOWED_TOOLS from .env
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:
tools/list, each tool carries _meta: { "requiresAuth": true | false }..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.
Source: README.md at commit 7137bc2
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.
pagepage_sizeCreates 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)
emailrequiredStories 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
pageoutputindustrylocationpage_sizeindustry_idlocation_idindustry_contextactivity_locationinclude_provenanceactivity_location_idStories 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 multip
pageoutputindustrylocationorg_namerequiredpage_sizeindustry_idlocation_idorg_locationorg_location_idindustry_contextactivity_location+1 more100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
curl -X POST "https://syracuse.1145.am/api/v1/register-and-get-key/" \ -H "Content-Type: application/json" \ -d "{\"email\":\"[email protected]\"}"{ "mcpServers": { "Syracuse Company News API": { "command": "/path/to/uv", "args": [ "--directory", "/path/to/repo/syracuse-mcp-server", "run", "stdio_mcp_server.py" ] } }}