Syracuse Company News
io.github.1145-am/syracuse-mcp-serverVersion 1.2.0Structured company & industry news for AI agents: typed, dated, source-linked events.
Status
Responds119 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:34 UTC
- Latency
- 119 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- EU hosting detected (detected, not a legal statement)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://syracuse.1145.am/mcp/Responds119 msNo sign-in
Claude Code
claude mcp add --transport http syracuse-mcp-server https://syracuse.1145.am/mcp/Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: syracuse-mcp-server
Remote MCP server URL: https://syracuse.1145.am/mcp/Cursor
{
"mcpServers": {
"syracuse-mcp-server": {
"url": "https://syracuse.1145.am/mcp/"
}
}
}VS Code
code --add-mcp '{"name":"syracuse-mcp-server","type":"http","url":"https://syracuse.1145.am/mcp/"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
4 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
location_groups_listLocation 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. | Not declared | Not declared | Not declared | Not declared |
register_and_get_key_createCreates 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) | Not declared | Not declared | Not declared | Not declared |
stories_industry_location_listStories 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 | Not declared | Not declared | Not declared | Not declared |
stories_organization_listStories 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 | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- Website
- Not given
- Categories (suggested)
- Search and webSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared