Skip to main content
Glama

Syracuse Company News

Server Details

Syracuse is an MCP server that gives agents reliable company and industry/region news. Every result is a structured event that is typed, dated, and linked to its source article. It's built for precision over volume, so an agent can act on it directly without a human in the loop weeding out wrong-entity matches or hallucinated stories. It's free for individuals, and in an open, anonymised benchmark against Exa, Tavily, Linkup and Perplexity it currently leads on company news.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

B3/5.0

Scored across 4 tools

Disambiguation4/5

The four tools cover clearly separable concerns: location hierarchy lookup, account/key creation, industry+location story search, and organization story search. The two story endpoints share most parameters and near-identical descriptions, so an agent must notice that one requires `org_name` and the other is industry/location-driven to pick correctly. That overlap is the only real confusion point.

Naming Consistency3/5

Names follow a loose `<resource>_list` / `<resource>_create` shape, but the prefix orderings are inconsistent (location_groups_list vs stories_industry_location_list vs register_and_get_key_create) and the registration tool uses a long chained verb phrase unlike anything else. Readable, but no single predictable pattern.

Tool Count3/5

Four tools is thin for a news/company-intelligence API; the two story endpoints are the bulk of the value and everything else is support scaffolding. Not egregious, but the surface feels under-built rather than well-scoped.

Completeness3/5

Read paths for stories and a registration path exist, but there is no story-detail lookup, no keyword/date search, and no industry-clusters tool even though descriptions instruct agents to pull `industry_id` from that endpoint. Agents can fall back to industry names, so it is a workaround-able gap rather than a hard dead end.

Available Tools

4 tools
location_groups_listCInspect

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.

Inputs: page, page_size.

register_and_get_key_createAInspect

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)

Inputs: email (required).

stories_industry_location_listBInspect

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

-- IndustryEventActivity: Conferences, trade shows, award ceremonies and similar events an organization hosts or takes part in

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 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 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 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.

Inputs: page, output, industry, location, +7 more.

stories_organization_listAInspect

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

-- IndustryEventActivity: Conferences, trade shows, award ceremonies and similar events an organization hosts or takes part in

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 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 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 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.

Inputs: org_name (required), page, output, industry, +9 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.
      16
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Browse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources