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 分