mcp server
com.stackscan/mcp-server
Look up the technology stack behind any domain, and the company running it.
Description as published by the maintainer. Source
- version 0.2.1
- active
active — Most recent push to the repository was 2026-08-04.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 1 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-04 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Package downloads | 538 downloads | Package downloads from the npm registry in this window. Includes continuous integration runs, mirrors and automated installs, so it overstates the number of human users. | 2026-07-30 to 2026-08-05 | npm | |
| Latest published version | 0.2.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-04 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-08-04 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
Generate Tech Stack
— last commit 2026-07-27, shares tech-stack
Visual tech-stack inventory of any codebase: languages, frameworks, databases, AI SDKs, infra.
-
io.ausdata/ausdata-mcp
— last commit 2026-05-20, shares api-client
28 tools over 9 AU gov data sources (ABS, RBA, ATO, APRA, AIHW, ASIC, AEMO, BOM, WGEA) via one key.
-
io.github.aborruso/ckan-mcp-server
— last commit 2026-08-06, shares api-client
MCP server for interacting with CKAN open data portals
-
Nummeropslag
— last commit 2026-08-04, shares api-client
Privacy-first Danish caller ID, CVR company lookup, operator data, and community spam signals.
-
Bargo Congress Trades
— last commit 2026-08-02, shares api-client
Query normalized U.S. Congress STOCK Act trades with member, ticker, and performance data.
-
Podcast Index MCP Server
— last commit 2026-08-03, shares api-client
Search the Podcast Index: podcasts, episodes, person appearances, trending, feed health.
-
Transistor MCP Server
— last commit 2026-08-02, shares api-client
Manage Transistor.fm podcasts: episodes, analytics, transcripts, and webhooks.
These share tags the maintainers applied themselves, such as tech-stack, api-client. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: ai-agents, api-client, builtwith, claude, cursor, firmographics, mcp, model-context-protocol, tech-stack, technographics, typescript.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab