# Syracuse Company News (remote · syracuse.1145.am)

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

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `syracuse.1145.am`: 65/100 (this document), [markdown](https://verifymcp.io/servers/1145-am-syracuse-mcp-server/syracuse.md), [page](https://verifymcp.io/servers/1145-am-syracuse-mcp-server/syracuse)

## Channel facts

- Endpoint: `https://syracuse.1145.am/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1499 tokens (~299/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http 1145-am-syracuse-mcp-server https://syracuse.1145.am/mcp/
```

### Codex

```toml
[mcp_servers.1145-am-syracuse-mcp-server]
url = "https://syracuse.1145.am/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "1145-am-syracuse-mcp-server": {
      "type": "remote",
      "url": "https://syracuse.1145.am/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 1145-am-syracuse-mcp-server --url https://syracuse.1145.am/mcp/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  1145-am-syracuse-mcp-server:
    url: "https://syracuse.1145.am/mcp/"
```

### Other

```json
{
  "mcpServers": {
    "1145-am-syracuse-mcp-server": {
      "type": "http",
      "url": "https://syracuse.1145.am/mcp/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (4)

### `location_groups_list` (~126 tokens)

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.

Input parameters:

- `page` (integer): A page number within the paginated result set.
- `page_size` (integer): Number of results to return per page.

### `register_and_get_key_create` (~85 tokens)

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)

Input parameters:

- `email` (string, required): User email address

### `stories_industry_location_list` (~799 tokens)

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 contex…

Input parameters:

- `include_provenance` (boolean): 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` (array): Industry name to filter by. Accepts multiple values.
- `industry_context` (array): 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 r…
- `location` (array): 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-grou…
- `output` (string): Output format. Defaults to "simple" (SimpleStory schema). Use "full" for the detailed response.
- `page` (integer): A page number within the paginated result set.
- `page_size` (integer): Number of results to return per page.

### `stories_organization_list` (~477 tokens)

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.

Input parameters:

- `org_name` (string, required): Filter by organization name (partial match).
- `output` (string): Output format. Defaults to "simple" (SimpleStory schema). Use "full" for the detailed response.
- `page` (integer): A page number within the paginated result set.
- `page_size` (integer): Number of results to return per page.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/1145-am-syracuse-mcp-server/syracuse#diagnostics

## Score history

- 2026-08-03: 65
- 2026-08-02: 65
- 2026-08-01: 64
- 2026-07-31: 64
- 2026-07-30: 64
- 2026-07-29: 63
- 2026-07-28: 62
- 2026-07-27: 62
- 2026-07-26: 61

## Links

- Remote endpoint: https://syracuse.1145.am/mcp/
- Repository: https://github.com/1145-am/syracuse-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/1145-am-syracuse-mcp-server/syracuse/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/1145-am-syracuse-mcp-server/syracuse/changelog.json
- HTML version of this page: https://verifymcp.io/servers/1145-am-syracuse-mcp-server/syracuse