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.

Anshul Panigrahi Portfolio

NPM · ANSHUL-PORTFOLIO-MCP

Anshul Panigrahi's portfolio as MCP tools: profile, projects, patents and contact.

+18 this week 75 Trust /100

Last scanned (19 hours ago)

Scores higher than 51% of npm servers

Category Developer Tools

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability81
  • 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 398 tokens (~49/item across 8 items; 6 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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 (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 16 Nov 26 +1
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Stability: unverified → 0.07 ▲ functional
    • Package version: 1.0.1 → 1.0.3 functional
  • 15 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 14 Nov 26 57

    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 21 Nov 2026 · Analysed npm/anshul-portfolio-mcp@1.0.3

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 →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~309 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
get_contact ~29

How to reach Anshul and where to find his resume, portfolio, GitHub and LinkedIn.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_profile ~38

Who Anshul Panigrahi is: headline, summary, what he is looking for, education, experience, achievements, certifications and links.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_project ~65

Full detail on one project: what it does, why it matters, stack and links. Pass the project name (partial names work, e.g. 'Eve', 'Stella', 'Veri-Dose').

NameTypeReqDescription
namestringyesProject name or part of it

No output schema declared.

No examples provided.

list_patents ~43

Anshul's published Indian patent applications (co-inventor): number, title, publication date, a plain-language summary and a link to the full official PDF.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_projects ~66

Anshul's projects with a one-line description, tech stack and link. Optionally filter by a keyword such as 'agents', 'LangGraph', 'computer vision' or 'CUDA'.

NameTypeReqDescription
querystring–Optional keyword to filter by (matches name, description and stack)

No output schema declared.

No examples provided.

search_profile ~68

Search everything in Anshul's profile (projects, patents, experience, skills, education) for a word or phrase and return the matching sections.

NameTypeReqDescription
querystringyesWord or phrase, e.g. 'RAG', 'YOLO', 'Raspberry Pi', 'hackathon'

No output schema declared.

No examples provided.

Install

How do I install the Anshul Panigrahi Portfolio MCP server?

Anshul Panigrahi Portfolio runs locally as an npm package, launched with npx -y anshul-portfolio-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 · anshul-portfolio-mcp

# add to Claude Code
claude mcp add burntcookiedough-anshul-portfolio-mcp -- npx -y anshul-portfolio-mcp
Common questions

What is the Anshul Panigrahi Portfolio MCP server?

Anshul Panigrahi Portfolio is an MCP server listed in the public MCP registry as io.github.burntcookiedough/anshul-portfolio-mcp. Anshul Panigrahi's portfolio as MCP tools: profile, projects, patents and contact. This page covers its npm package (anshul-portfolio-mcp).

Is the Anshul Panigrahi Portfolio MCP server safe to use?

Anshul Panigrahi Portfolio scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 Anshul Panigrahi Portfolio MCP server expose?

Anshul Panigrahi Portfolio exposes 6 tools: get_profile, list_projects, get_project, list_patents, get_contact, search_profile. Their descriptions and schemas cost roughly 309 tokens of context every time the server is loaded.

Is the Anshul Panigrahi Portfolio MCP server still maintained?

Anshul Panigrahi Portfolio 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 licence is the Anshul Panigrahi Portfolio MCP server under?

Anshul Panigrahi Portfolio declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Anshul Panigrahi Portfolio MCP server?

VerifyMCP ran 16 checks on Anshul Panigrahi Portfolio, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.