Syracuse Company News
REMOTE · SYRACUSE.1145.AM · SCANNED SEP 20
Structured company & industry news for AI agents: typed, dated, source-linked events.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2885 tokens (~577/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Syracuse Company News MCP server?
Syracuse Company News is a hosted endpoint at https://syracuse.1145.am/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · syracuse.1145.am
claude mcp add --transport http 1145-am-syracuse-mcp-server 'https://syracuse.1145.am/mcp/'
{
"mcpServers": {
"1145-am-syracuse-mcp-server": {
"url": "https://syracuse.1145.am/mcp/"
}
}
} {
"servers": {
"1145-am-syracuse-mcp-server": {
"type": "http",
"url": "https://syracuse.1145.am/mcp/"
}
}
} [mcp_servers.1145-am-syracuse-mcp-server] url = "https://syracuse.1145.am/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"1145-am-syracuse-mcp-server": {
"type": "remote",
"url": "https://syracuse.1145.am/mcp/",
"enabled": true
}
}
} openclaw mcp add 1145-am-syracuse-mcp-server --url 'https://syracuse.1145.am/mcp/' --transport streamable-http
mcp_servers:
1145-am-syracuse-mcp-server:
url: "https://syracuse.1145.am/mcp/" {
"McpServers": {
"1145-am-syracuse-mcp-server": {
"Transport": "http",
"Url": "https://syracuse.1145.am/mcp/"
}
}
} assistant mcp add 1145-am-syracuse-mcp-server -t streamable-http -u 'https://syracuse.1145.am/mcp/'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Aug 26 0
- Tool “stories_industry_location_list” rewrote its description, which is the text the model reads security
- Tool “stories_organization_list” rewrote its description, which is the text the model reads security
- Schema quality: 299 → 577 ▼ functional
- Server version: 1.2.0 → 1.3.0 functional
- “stories_industry_location_list” added an optional parameter “activity_location” cosmetic
- “stories_industry_location_list” added an optional parameter “activity_location_id” cosmetic
- “stories_industry_location_list” added an optional parameter “industry_id” cosmetic
- “stories_industry_location_list” added an optional parameter “location_id” cosmetic
- “stories_organization_list” added an optional parameter “activity_location” cosmetic
- “stories_organization_list” added an optional parameter “activity_location_id” cosmetic
- “stories_organization_list” added an optional parameter “industry” cosmetic
- “stories_organization_list” added an optional parameter “industry_context” cosmetic
- “stories_organization_list” added an optional parameter “industry_id” cosmetic
- “stories_organization_list” added an optional parameter “location” cosmetic
- “stories_organization_list” added an optional parameter “location_id” cosmetic
- “stories_organization_list” added an optional parameter “org_location” cosmetic
- “stories_organization_list” added an optional parameter “org_location_id” cosmetic
- “stories_industry_location_list” reworded the description of “industry_context” cosmetic
- “stories_industry_location_list” reworded the description of “location” cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://syracuse.1145.am/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=1145.am | CN=YE1,O=Let's Encrypt,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 657d3559cada5941ce5ae1d95a9a07e6eb0 |
| SANs: 1145.am, syracuse.1145.am | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of syracuse.1145.am. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| am. | present | 39902 | 13 | Verified |
| 1145.am. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://syracuse.1145.am/mcp/ | Verified | 200 | |
| http (plaintext) | http://syracuse.1145.am/mcp/ | HTTPS enforced | 301 | https://syracuse.1145.am/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
location_groups_list ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | A page number within the paginated result set. |
| page_size | integer | – | Number of results to return per page. |
No output schema declared.
No examples provided.
register_and_get_key_create ~85
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)
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | User email address |
No output schema declared.
No examples provided.
stories_industry_location_list ~1,225
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-group…
| Name | Type | Req | Description |
|---|---|---|---|
| activity_location | array | – | 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 [locatio… |
| activity_location_id | array | – | 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-g… |
| 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. Can be a broader category name or detailed examples (e.g. "Movie Industry" when searching for "Distrib… |
| industry_id | array | – | 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 | array | – | 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 | array | – | 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 | 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. |
No output schema declared.
No examples provided.
stories_organization_list ~1,437
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 multi…
| Name | Type | Req | Description |
|---|---|---|---|
| activity_location | array | – | 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 [locatio… |
| activity_location_id | array | – | 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-g… |
| industry | array | – | Industry name the company must work in. Narrows which companies match `org_name`. Accepts multiple values. |
| industry_context | array | – | 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 "Distrib… |
| industry_id | array | – | 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) e… |
| location | array | – | 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 | array | – | 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 | array | – | 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 sto… |
| org_location_id | array | – | 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 | string | yes | 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. |
No output schema declared.
No examples provided.
What is the Syracuse Company News MCP server?
Syracuse Company News is an MCP server listed in the public MCP registry as io.github.1145-am/syracuse-mcp-server. Structured company & industry news for AI agents: typed, dated, source-linked events. This page covers its hosted endpoint (https://syracuse.1145.am/mcp/).
Is the Syracuse Company News MCP server safe to use?
Syracuse Company News scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Syracuse Company News MCP server expose?
Syracuse Company News exposes 4 tools: location_groups_list, register_and_get_key_create, stories_industry_location_list, stories_organization_list. Their descriptions and schemas cost roughly 2,873 tokens of context every time the server is loaded.
Does the Syracuse Company News MCP server require authentication?
No. We connected to Syracuse Company News without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Syracuse Company News MCP server still maintained?
Syracuse Company News is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.