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.

io.github.imharikumaran/altimateguide

NPM · ALTIMATEGUIDE-AGENT-MCP

Submit a tool to the Altimateguide directory for editorial review.

+7 this week 66 Trust /100

Last scanned (6 hours ago)

Scores higher than 38% of npm servers

Category Search and Retrieval

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 Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.5.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 7 of 14 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 239 tokens (~239/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 Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +6
    • Stability: unverified → 0.37 ▲ functional
  • 13 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 11 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 4 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Oct 26 44

    First indexed and scored.

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 18 Oct 2026 · Analysed npm/altimateguide-agent-mcp@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-w48q-cv73-mx4w CVE-2025-66414 high yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 14 packages
Packages resolved 14
Stale 7
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~239 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
submit_tool ~239

Submit a tool to the Altimateguide directory for editorial review (POST /api/agent/submit). The listing is queued as pending and is never published automatically — an editor reviews it. Requires ALTIMATEGUIDE_AGENT_TOKEN, a per-account API token created at https://altimateguide.com/account (Agent & API access).

NameTypeReqDescription
categoriesarrayyesOne or more category slugs
descriptionstring–Neutral listing copy (min 20 chars; promotional/ranking language is rejected)
externalIdstring–Your own id for idempotent replays
featuresarray–Structured feature list (label + optional detail)
namestringyesTool name
paymentRefstring–Required for paid proof
proofstring–Inclusion path (default none). sayabout/badge need verificationUrl; paid needs paymentRef.
sourcestring–Origin id, e.g. agent:mcp
urlstringyesCanonical http(s) URL of the tool
verificationUrlstring–Required for sayabout/badge proof

No output schema declared.

No examples provided.

Install

How do I install the io.github.imharikumaran/altimateguide MCP server?

io.github.imharikumaran/altimateguide runs locally as an npm package, launched with npx -y altimateguide-agent-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 · altimateguide-agent-mcp

# add to Claude Code
claude mcp add imharikumaran-altimateguide -- npx -y altimateguide-agent-mcp
Common questions

What is the io.github.imharikumaran/altimateguide MCP server?

io.github.imharikumaran/altimateguide is an MCP server listed in the public MCP registry as io.github.imharikumaran/altimateguide. Submit a tool to the Altimateguide directory for editorial review. This page covers its npm package (altimateguide-agent-mcp).

Is the io.github.imharikumaran/altimateguide MCP server safe to use?

io.github.imharikumaran/altimateguide scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 18 October 2026. It declares no install or post-install scripts. 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 io.github.imharikumaran/altimateguide MCP server expose?

io.github.imharikumaran/altimateguide exposes 1 tool: submit_tool. Their descriptions and schemas cost roughly 239 tokens of context every time the server is loaded.

Is the io.github.imharikumaran/altimateguide MCP server still maintained?

io.github.imharikumaran/altimateguide is still listed as active in the MCP registry. We last reached this channel on 18 October 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 io.github.imharikumaran/altimateguide MCP server under?

io.github.imharikumaran/altimateguide declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.