Syracuse Company News MCP server
io.github.1145-am/syracuse-mcp-server1145-amstreamable-httpv1.3.0Scanned
Structured company & industry news for AI agents: typed, dated, source-linked events.
4 tools: 1 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Syracuse Company News MCP server can do
The Syracuse Company News MCP server is published by the GitHub account 1145-am. It has 4 tools. It can create or change data (1 tool: register_and_get_key_create), but cannot delete data. 3 tools only read.
1 tool reads private data (register_and_get_key_create); 1 tool brings in text other people can write (register_and_get_key_create).
The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 1.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 1Claude Code: ask
register_and_get_key_createCreates a user account with the given email, sends a verification email, and returns an API token.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "register_and_get_key_create" says "get": a word for reading.
- The description's first verb is "create": a word for a change.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "create" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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)
Only reads 3Show 3 read-only tools
location_groups_listLocation Groups are a way of grouping GeoNamesLocation entities into a simplified hierarchy.No findings
Why it is in this group
- The name "location_groups_list" says "list": a word for reading.
Description, as the server wrote it 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.
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 happene…1 finding
Why it is in this group
- The name "stories_industry_location_list" says "list": a word for reading.
Findings
- Info
The description is 3,737 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...thin the paginated result set. - page_size: Number of results to return per page."
Description, as the server wrote it 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](#/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_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 com…1 finding
Why it is in this group
- The name "stories_organization_list" says "list": a word for reading.
Findings
- Info
The description is 4,265 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...thin the paginated result set. - page_size: Number of results to return per page."
Description, as the server wrote it 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](#/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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:56 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://syracuse.1145.am/mcp/: tools/list returned 4 tools to an anonymous client, including register_and_get_key_create (write)
Findings
Matches of fixed checks, with the text they matched.
The description is 3,737 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...thin the paginated result set. - page_size: Number of results to return per page."
The description is 4,265 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...thin the paginated result set. - page_size: Number of results to return per page."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:stories_industry_location_listOnly readsdescription
- Changed:stories_organization_listOnly readsdescription
Install
Pinned to version 1.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http syracuse https://syracuse.1145.am/mcp/claude mcp add --transport http syracuse https://syracuse.1145.am/mcp/Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__syracuse__location_groups_list",
"mcp__syracuse__stories_industry_location_list",
"mcp__syracuse__stories_organization_list"
],
"ask": [
"mcp__syracuse__register_and_get_key_create"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as syracuse. Review it before you use it.
Capability tags behind 1 rule
- mcp__syracuse__register_and_get_key_create private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.1145-am/syracuse-mcp-server/verify?hash=b5ea73f79bf9ea37b4ec84ca5b3c3b677e4bfd31076eb98d543386bcaf565cd4" | jq -e '.changed == false'Pinned hash b5ea73f79bf9, from Nov 21, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.1145-am/syracuse-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.1145-am/syracuse-mcp-server)Source: MCP Registry · repository. Synced Nov 21, 2026, 20:17 UTC.
Syracuse Company News MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Syracuse Company News MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Syracuse Company News MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Syracuse Company News MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Syracuse Company News MCP server have?
- 4 tools: 1 write, 3 read. register_and_get_key_create, location_groups_list, stories_industry_location_list and stories_organization_list.
Does the Syracuse Company News MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Syracuse Company News MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Syracuse Company News MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.