Syracuse Company News

io.github.1145-am由 GitHub 帳號 1145-am 發布v1.2.0更新於 Oct 24, 2026

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

已驗證Streamable HTTP可網頁執行網頁搜尋與抓取商業與電商

概覽

AI 產生的概覽

遠端 MCP 伺服器,讓助理取得結構化、附日期與來源連結的公司與產業新聞,並提供地區分組與免費 API 金鑰註冊。

可以做什麼
  • 列出地區分組,即依聯合國 M49 標準與美國人口普查區域劃分的簡化層級
  • 依產業與事件發生地點擷取新聞報導
  • 依組織名稱擷取新聞報導,可再依總部所在地、產業或活動地點縮小範圍
  • 以電子郵件註冊帳號並取得 API 權杖
適用情境
適合助理需要調查公司、產業或區域商業動態,並希望取得結構化、附日期與來源連結的新聞事件,而非原始網頁搜尋結果時使用。
執行需求
託管方式使用 syracuse.1145.am 遠端端點,不需本機執行環境。需授權的呼叫須在 X-API-Key 標頭提供 API 金鑰,可透過電子郵件註冊免費取得。自行架設需安裝 uv 並複製程式碼儲存庫。
安裝前請注意
註冊會將電子郵件傳送給服務提供者並建立帳號;未驗證帳號每月僅限 30 次查詢。API 金鑰屬機密,不應寫入共用設定。查詢內容與金鑰都會傳送給第三方服務。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Syracuse Company News,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.1145-am%2Fsyracuse-mcp-server/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "syracuse-company-news": {
      "type": "http",
      "url": "https://syracuse.1145.am/mcp/"
    }
  }
}

README

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:

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

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:

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

To run as Local MCP Server

Pre-req: Install uv

  1. Clone this repo
  2. Copy .env.sample to .env and configure your MCP_SERVER_API_TOKEN with the API key you got above
  3. Example claude_desktop_config.json
{  "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:

  1. Clone this repo
  2. Copy .env.sample to .env - though any further configuration is not needed
  3. 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.

來源:README.md,提交 7137bc2

工具

4

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.

輸入參數pagepage_size

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)

輸入參數email必填

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 (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_id

stories_organization_list

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 multip

輸入參數pageoutputindustrylocationorg_name必填page_sizeindustry_idlocation_idorg_locationorg_location_idindustry_contextactivity_location另有 1 個

版本歷史

1
  1. v1.2.0最新Sep 16, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分