# Syracuse Company News

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

- name: io.github.1145-am/syracuse-mcp-server
- version: 1.2.0
- connection class: R0 (autonomous)
- trust: 87/100
- quality: 76/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.1145-am%2Fsyracuse-mcp-server
- tools: https://api.protogrid.dev/v1/servers/io.github.1145-am%2Fsyracuse-mcp-server/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "syracuse-mcp-server": {
      "type": "http",
      "url": "https://syracuse.1145.am/mcp/",
      "headers": {
        "X-API-Key": "${X_API_KEY}"
      }
    }
  }
}
```

Placeholders to fill: `${X_API_KEY}`.

## Trust

- hygiene: 100
- liveness: 100
- freshness: 65
- provenance: 80
- drivers: +repository +namespace-matches-repo +reachable +uptime-100% ~updated-138d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 76/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 64 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 2 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: stories_organization_list (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); stories_industry_location_list (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); location_groups_list (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 3,713 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 4, about 3,713 tokens to load them all
- tool set hash: 572737ba13669a93415b961a6ec114d0
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.1145-am/syracuse-mcp-server.svg)](https://protogrid.dev/servers/io.github.1145-am/syracuse-mcp-server)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://syracuse.1145.am/mcp/ (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (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.
- `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)
- `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_list) endpoint.
- activity_location_id: Location group identifiers (e.g., "Southern Asia", "BT", "US-CA") where the story happened. Case-sensitive. Accepts multiple values. They must each match an id from the [location groups](#/location-groups/location-groups_list) endpoint.
- 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 context aspects to anchor the industry search in. Pass each aspect as a separate value. Can be a broader category name or detailed examples (e.g. "Movie Industry" when searching for "Distribution", or "BOPP Film" and "BOPET Film" when searching for "Film"). Applied to every value of `industry` in the same request.
- industry_id: Industry ID (topic ID) to filter by. Accepts multiple values. They must each match a topic_id from the [industry-clusters](#/industry-clusters/industry-clusters_list) endpoint.
- location: Deprecated alias of `activity_location`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.
- location_id: Deprecated alias of `activity_location_id`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.
- 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.
- `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 multiple values. They must each match an id or name from the [location groups](#/location-groups/location-groups_list) endpoint.
- activity_location_id: Location group identifiers (e.g., "Southern Asia", "BT", "US-CA") where the story happened. Case-sensitive. Accepts multiple values. They must each match an id from the [location groups](#/location-groups/location-groups_list) endpoint.
- industry: Industry name the company must work in. Narrows which companies match `org_name`. Accepts multiple values.
- industry_context: Optional context aspects to anchor the industry search in. Pass each aspect as a separate value. Can be a broader category name or detailed examples (e.g. "Movie Industry" when searching for "Distribution", or "BOPP Film" and "BOPET Film" when searching for "Film"). Applied to every value of `industry` in the same request.
- industry_id: Industry ID (topic ID) the company must belong to. Narrows which companies match `org_name`. They must each match a topic_id from the [industry-clusters](#/industry-clusters/industry-clusters_list) endpoint.
- location: Deprecated alias of `activity_location`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.
- location_id: Deprecated alias of `activity_location_id`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.
- org_location: Location group name or id where the company is *based*. Narrows which companies match `org_name`, so it may only be used together with `org_name`. Not case sensitive. Accepts multiple values. For stories that happened in a place use `activity_location` instead.
- org_location_id: Location group identifiers (e.g., "Southern Asia", "BT", "US-CA") where the company is *based*. Case-sensitive. May only be used together with `org_name`.
- 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.