Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Hex.pm MCP

REMOTE · HEXPM-MCP.FLY.DEV

MCP server for hex.pm and hexdocs.pm: search, inspect, compare, and audit Elixir packages

0 this week 79 Trust /100

Last scanned (12 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability80
  • 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
  • Tool/resource definitions use about 1150 tokens (~46/item across 25 items; 24 tools + 1 resources), lean.Pass
  • 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 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 24 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 1 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 37 → 46 ▼ functional
    • Server version: 0.3.8 → 0.3.10 functional
  • 28 Sept 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
  • 25 Sept 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
Diagnostics

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 21 Nov 2026 · Probed https://hexpm-mcp.fly.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.fly.dev CN=YE1,O=Let's Encrypt,C=US 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA384 5e6e25e6df778e81cd07b85fc9f12d4df7d
SANs: *.fly.dev
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 hexpm-mcp.fly.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
fly.dev. No DS 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://hexpm-mcp.fly.dev/mcp Verified 200
http (plaintext) http://hexpm-mcp.fly.dev/mcp HTTPS enforced 301 https://hexpm-mcp.fly.dev/mcp
MCP tools · 24 exposed · ~931 tokens

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 →

Tool Tokens
alternatives ~23

Find alternative packages

NameTypeReqDescription
namestringyesPackage name on hex.pm

No output schema declared.

No examples provided.

audit ~38

Audit package dependencies for risks

NameTypeReqDescription
namestringyesPackage name on hex.pm
versionstring–Release version (defaults to latest)

No output schema declared.

No examples provided.

audit_mix_deps ~56

Audit mix.exs dependencies for risks

NameTypeReqDescription
depsstringyesMix.exs deps list as text, e.g. {:phoenix, "~> 1.7"}, {:ecto, "~> 3.10"}

No output schema declared.

No examples provided.

compare ~36

Compare 2-5 packages side by side

NameTypeReqDescription
packagesstringyesComma-separated list of package names (2-5 packages)

No output schema declared.

No examples provided.

dep_tree ~59

Build a package dependency tree

NameTypeReqDescription
max_depthinteger–Maximum depth to traverse (default 5, max 5)
namestringyesPackage name on hex.pm
versionstring–Release version (defaults to latest)

No output schema declared.

No examples provided.

dependencies ~39

Get dependencies for a package version

NameTypeReqDescription
namestringyesPackage name on hex.pm
versionstring–Release version (defaults to latest)

No output schema declared.

No examples provided.

doc_item ~57

Get documentation for a module or function

NameTypeReqDescription
modulestringyesModule name (e.g. "Plug.Conn")
namestringyesPackage name on hex.pm
versionstring–Package version (defaults to latest)

No output schema declared.

No examples provided.

docs ~39

Browse a package documentation module listing

NameTypeReqDescription
namestringyesPackage name on hex.pm
versionstring–Package version (defaults to latest)

No output schema declared.

No examples provided.

downloads ~24

Get package download statistics

NameTypeReqDescription
namestringyesPackage name on hex.pm

No output schema declared.

No examples provided.

features ~40

Get optional features for a package release

NameTypeReqDescription
namestringyesPackage name on hex.pm
versionstring–Release version (defaults to latest)

No output schema declared.

No examples provided.

health ~26

Run a comprehensive package health check

NameTypeReqDescription
namestringyesPackage name on hex.pm

No output schema declared.

No examples provided.

info ~24

Get detailed package information

NameTypeReqDescription
namestringyesPackage name on hex.pm

No output schema declared.

No examples provided.

owners ~26

Get package owners and maintainers

NameTypeReqDescription
namestringyesPackage name on hex.pm

No output schema declared.

No examples provided.

readme ~38

Get package README content

NameTypeReqDescription
namestringyesPackage name on hex.pm
versionstring–Package version (defaults to latest)

No output schema declared.

No examples provided.

release ~44

Get detailed package release information

NameTypeReqDescription
namestringyesPackage name on hex.pm
versionstringyesRelease version (e.g. "1.8.5")

No output schema declared.

No examples provided.

search ~60

Search hex.pm packages

NameTypeReqDescription
pageinteger–Page number (default 1)
querystringyesSearch query string
sortstring–Sort by: name, recent_downloads, total_downloads, inserted_at, updated_at

No output schema declared.

No examples provided.

search_docs ~47

Search within package documentation

NameTypeReqDescription
namestringyesPackage name on hex.pm
querystringyesSearch query
versionstring–Package version (defaults to latest)

No output schema declared.

No examples provided.

toolbox_category ~76

List projects in a Toolbox category

NameTypeReqDescription
categorystringyesCategory slug within the group (e.g. "frameworks")
groupstringyesGroup slug (e.g. "web", "ai")
sortstring–Ordering: "name" (alphabetical) or "downloads"; defaults to popularity order

No output schema declared.

No examples provided.

toolbox_group ~33

List categories in a Toolbox group

NameTypeReqDescription
groupstringyesGroup slug (e.g. "web", "ai")

No output schema declared.

No examples provided.

toolbox_groups ~15

Browse the Elixir Toolbox taxonomy

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

toolbox_search ~25

Search packages through Elixir Toolbox

NameTypeReqDescription
querystringyesSearch query string

No output schema declared.

No examples provided.

toolbox_trending ~28

List trending Elixir packages

NameTypeReqDescription
limitinteger–Maximum number of projects to return

No output schema declared.

No examples provided.

upgrade_check ~54

Check mix.exs dependencies for upgrades

NameTypeReqDescription
depsstringyesMix.exs deps list as text, e.g. {:phoenix, "~> 1.7"}, {:ecto, "~> 3.10"}

No output schema declared.

No examples provided.

versions ~24

List all package versions

NameTypeReqDescription
namestringyesPackage name on hex.pm

No output schema declared.

No examples provided.

Install

How do I install the Hex.pm MCP server?

Hex.pm MCP is a hosted endpoint at https://hexpm-mcp.fly.dev/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 · hexpm-mcp.fly.dev

# add to Claude Code
claude mcp add --transport http joshrotenberg-hexpm-mcp 'https://hexpm-mcp.fly.dev/mcp'
Common questions

What is the Hex.pm MCP server?

Hex.pm MCP is listed in the public MCP registry as io.github.joshrotenberg/hexpm-mcp. MCP server for hex.pm and hexdocs.pm: search, inspect, compare, and audit Elixir packages. This page covers its hosted endpoint (https://hexpm-mcp.fly.dev/mcp).

Is the Hex.pm MCP server safe to use?

Hex.pm MCP scores 79 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 Hex.pm MCP server expose?

Hex.pm MCP exposes 24 tools: alternatives, audit, audit_mix_deps, compare, dep_tree, and 19 more. Their descriptions and schemas cost roughly 931 tokens of context every time the server is loaded.

Does the Hex.pm MCP server require authentication?

No. We connected to Hex.pm MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Hex.pm MCP server still maintained?

Hex.pm MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Hex.pm MCP server?

VerifyMCP ran 12 checks on Hex.pm MCP, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Hex.pm MCP: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.