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.

APIFreaks MCP

NPM · @APIFREAKS/MCP

APIFreaks MCP: live APIs for agents. Enable modules with ENABLE_MODULES; discover via list_modules.

Available components

npm · @apifreaks/mcp 94
0 this week 94 Trust /100

Last scanned (1 hour ago)

Scores higher than 97% of npm servers

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 33 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to api-freaks/apifreaks-mcp). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 263 tokens (~263/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 1 Nov 26 0
    • Package version: 1.1.2 → 2.6.0 functional
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
    • Package version: 2.5.0 → 2.6.0 functional
    • Package version: 2.4.0 → 2.5.0 functional
  • 29 Oct 26 0
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: pass → 0.97 functional
    • Package version: 2.4.1 → 2.5.0 functional
  • 24 Oct 26 0
    • Package version: 2.4.0 → 2.4.1 functional
  • 22 Oct 26 0
    • Stability: 0.97 → pass security
  • 21 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: pass → 0.97 functional
  • 20 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 2.4.0 → 2.4.1 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 5 Nov 2026 · Analysed npm/@apifreaks/mcp@2.6.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo api-freaks/apifreaks-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/api-freaks/apifreaks-mcp/.github/workflows/publish-npm.yml@refs/tags/v2.6.0
Rekor log index 3595076162
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:0ba251b6262946b044d5ba2eea7b86005b21a85dfb459309665a09e08660b059ca173d33aa1e0c6f834497f685d0d22049b5216d92cdf52a54e7d4daa

Background: How many MCP packages publish verified provenance →

Dependencies 105 packages
Packages resolved 105
Stale 33
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~163 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
list_modules ~163

APIFreaks module catalog (opt-in via ENABLE_MODULES). Call when a needed capability is missing from your tool list, or to check whether APIFreaks covers a topic. Live tools for enabled modules already appear in tools/list; this returns needs_enable[] with paste-ready enable_line values — give the user that ENABLE_MODULES=... line and ask them to restart. Modules: ip-intelligence, geocoding, whois, dns, scraper, email-validation, phone-validation, ssl, domain, screenshot, pdf, currency, commodity, financial, zipcode, weather, geography, timezone, user-agent. ENABLE_MODULES unset — only this tool is registered (example: ENABLE_MODULES=ip-intelligence,whois,dns,domain,weather).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the APIFreaks MCP server?

APIFreaks MCP runs locally as an npm package, launched with npx -y @apifreaks/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @apifreaks/mcp

# add to Claude Code
claude mcp add api-freaks-apifreaks-mcp -- npx -y @apifreaks/mcp
Common questions

What is the APIFreaks MCP server?

APIFreaks MCP is listed in the public MCP registry as io.github.api-freaks/apifreaks-mcp. APIFreaks MCP: live APIs for agents. Enable modules with ENABLE_MODULES; discover via list_modules. This page covers its npm package (@apifreaks/mcp).

Is the APIFreaks MCP server safe to use?

APIFreaks MCP scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 APIFreaks MCP server expose?

APIFreaks MCP exposes 1 tool: list_modules. Their descriptions and schemas cost roughly 163 tokens of context every time the server is loaded.

Is the APIFreaks MCP server still maintained?

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

What licence is the APIFreaks MCP server under?

APIFreaks MCP declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.