GunSpec

io.gunspecPublished by gunspec.ioOfficial publisherv0.6.3Updated Oct 24, 2026

Read-only firearm specifications: calibers, ammunition, manufacturers and attachment fitment.

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

GunSpec gives an assistant read-only access to firearm specifications: calibers, ammunition, manufacturers and attachment fitment.

What you can do
  • Look up firearm specifications such as calibers and ammunition.
  • Check manufacturers and their product data.
  • Verify whether attachments fit a given firearm.
  • All access is read-only, so the assistant can query reference data but not change it.
When to use it
Useful when you need firearm, caliber, ammunition or attachment-compatibility reference data while researching or comparing gear, and want the assistant to answer from a structured catalog instead of general knowledge.
Requirements
A remote MCP endpoint at mcp.gunspec.io over streamable HTTP. Authentication is required: OAuth, plus a GunSpec API key supplied in the X-API-Key header, obtained from the GunSpec account profile. Network access is needed.
Before you install
You must supply a GunSpec API key as the X-API-Key header; treat it as a secret and check how it is stored and transmitted. Queries and lookups are sent to the GunSpec service, a third party. The description indicates read-only access, but confirm this before relying on it.

Installation

In SourceWeft

  1. Open GunSpec in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.gunspec%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "gunspec": {
      "type": "http",
      "url": "https://mcp.gunspec.io/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

6
  1. v0.6.3LatestOct 9, 2026
  2. v0.6.2Oct 4, 2026
  3. v0.5.0Sep 22, 2026
  4. v0.4.2Sep 18, 2026
  5. v0.3.1Sep 17, 2026
  6. v0.2.4Sep 17, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.