Gunspec
Actively maintained
≈ 538visits/mo
Emerging · estimate, read Oct 15, 2026
- For
- developers and analysts building reports, games, analytics apps or AI agents that need firearm specifications
- Activity
- Actively maintainedrelease 6 days ago · site updated 2 days ago
- Used for
- look up sourced firearm specifications through an API
- compare two firearms field by field
- check whether an attachment fits a given firearm
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantsgunspec.io ↗
- Trust centertheir owntrust center ↗
- Security contactsecurity.txt
These are Gunspec's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
- MCP serverio.gunspec/mcpverified in the MCP registry
- Stateanswers, requires sign-inchecked 2026-10-26
- Address to connectmcp.gunspec.io
- MCP docsdocs.gunspec.io/en/mcp/installthe vendor's page ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use Gunspec for?
Sign in to leave a noteWhat is Gunspec?
Serves firearm specifications, calibers, ballistics and manufacturers as JSON through an API and an MCP server.
Who is Gunspec for?
developers and analysts building reports, games, analytics apps or AI agents that need firearm specifications
Do people use Gunspec?
Emerging: ≈ 538 visits/mo · estimate, 2026-10 · 44 installs/mo (npm).
Is Gunspec still maintained?
Actively maintained: release 6 days ago · site updated 2 days ago.
Is Gunspec safe?
We do not audit vendors. What Gunspec publishes, read 2026-10-26: a trust center.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.