Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Nothing to run from here
Syracuse Company News is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
4
tools declared
remote
at its publisher
—
calls last 7d
What it does
Structured company & industry news for AI agents: typed, dated, source-linked events.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http syracuse-company-news-mcp https://syracuse.1145.am/mcp/ --header 'X-API-Key: ${X_API_KEY}'
# 2 — ask your agent for something these tools do
# location_groups_list, register_and_get_key_create, stories_industry_location_list and 1 more
It needs X_API_KEY (Your Syracuse API key (the raw key, no prefix). Free at syracuse.1145.am; not needed to connect or register): this sends it in the X-API-Key header from your environment, so export it first — its endpoint answers 401 without it.
Syracuse Company News costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
1AAll 1 server
1145-am1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads X_API_KEY (Your Syracuse API key (the raw key, no prefix). Free at syracuse.1145.am; not needed to connect or register) from your environment each time it connects and sends it in the X-API-Key header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx X_API_KEY … and open a new terminal (Windows).
claude mcp add --scope user --transport http syracuse-company-news-mcp https://syracuse.1145.am/mcp/ --header 'X-API-Key: ${X_API_KEY}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.
What it asks of you
Nothing is required, but it can take X-API-Key header (Your Syracuse API key (the raw key, no prefix). Free at syracuse.1145.am; not needed to connect or register.) if you want to set it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | A page number within the paginated result set. |
| page_size | integer | no | Number of results to return per page. |
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)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | User email address |
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 -- PartnershipA
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity_location | array | no | 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 |
| activity_location_id | array | no | 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-gr |
| include_provenance | boolean | no | 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 | no | Industry name to filter by. Accepts multiple values. |
| industry_context | array | no | 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 "Distribu |
| industry_id | array | no | 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 | no | 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 | no | 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 | no | Output format. Defaults to "simple" (SimpleStory schema). Use "full" for the detailed response. |
| page | integer | no | A page number within the paginated result set. |
| page_size | integer | no | Number of results to return per page. |
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 th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity_location | array | no | 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 |
| activity_location_id | array | no | 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-gr |
| industry | array | no | Industry name the company must work in. Narrows which companies match org_name. Accepts multiple values. |
| industry_context | array | no | 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 "Distribu |
| industry_id | array | no | 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) en |
| location | array | no | 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 | no | 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 | no | 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 stor |
| org_location_id | array | no | 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 | no | Output format. Defaults to "simple" (SimpleStory schema). Use "full" for the detailed response. |
| page | integer | no | A page number within the paginated result set. |
| page_size | integer | no | Number of results to return per page. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Syracuse Company News or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.2.0 · scanned 23 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest5e315440ec5c940303ef6dd5b6b3ef63e29331fec367e0edc2e1c60619ec1e28
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| location_groups_list | no tags | |
| register_and_get_key_create | no tags | |
| stories_industry_location_list | no tags | |
| stories_organization_list | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest5e315440ec5c9403
Scanned2026-10-23
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2.0.
1.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Syracuse Company News can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.