saagarpatel.dev Portfolio
NPM · SAAGAR-PORTFOLIO-MCP · 2 COMPONENTS · SCANNED SEP 20
Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless.
Available components
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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 84 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1907 tokens (~44/item across 43 items; 6 tools + 37 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the saagarpatel.dev Portfolio MCP server?
saagarpatel.dev Portfolio runs locally as an npm package, launched with npx -y saagar-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 · saagar-portfolio-mcp
claude mcp add saagpatel-portfolio-mcp -- npx -y saagar-portfolio-mcp
{
"mcpServers": {
"saagpatel-portfolio-mcp": {
"command": "npx",
"args": [
"-y",
"saagar-portfolio-mcp"
]
}
}
} {
"servers": {
"saagpatel-portfolio-mcp": {
"command": "npx",
"args": [
"-y",
"saagar-portfolio-mcp"
]
}
}
} codex mcp add saagpatel-portfolio-mcp -- npx -y saagar-portfolio-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"saagpatel-portfolio-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"saagar-portfolio-mcp"
],
"enabled": true
}
}
} openclaw mcp add saagpatel-portfolio-mcp --command npx --arg -y --arg saagar-portfolio-mcp
mcp_servers:
saagpatel-portfolio-mcp:
command: "npx"
args: ["-y", "saagar-portfolio-mcp"] {
"McpServers": {
"saagpatel-portfolio-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"saagar-portfolio-mcp"
]
}
}
} assistant mcp add saagpatel-portfolio-mcp -t stdio -c npx -a -y saagar-portfolio-mcp
{
"mcpServers": {
"saagpatel-portfolio-mcp": {
"command": "npx",
"args": [
"-y",
"saagar-portfolio-mcp"
]
}
}
} 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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 14 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/saagar-portfolio-mcp@0.1.0
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 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_document Get a document ~61
Return the full Markdown of one document by id, e.g. "writing/the-handoff" or "book/preface". Get ids from search or list_corpus.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Document id, e.g. "book/preface" |
No output schema declared.
No examples provided.
get_operant_results Get OPERANT benchmark results ~66
Return the public, sanitized OPERANT results: per-model operator-calibration-score (OCS) profiles, the headline figures, and the calibration-profiles (not a flat leaderboard) framing. Sourced from the published OPERANT mirror. Returns availability=false if no dataset was baked.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_profile Get profile ~45
Return Saagar Patel's profile: name, one-line summary, site, and the about / now / uses pages. Start here to understand who this is and what they work on.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_corpus List the corpus ~57
List every document with its id, title, type, date, and word count, plus per-type counts. The table of contents for the whole site. Optionally filter by type.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | – | Filter by content type |
No output schema declared.
No examples provided.
list_projects List projects ~72
List the curated, public projects with stack, status, last-active date, and test/CI signals, plus anonymized portfolio-wide aggregates. Optionally filter by status.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max projects |
| status | string | – | Filter by status, e.g. "active" or "archived" |
No output schema declared.
No examples provided.
search Search the writing corpus ~85
Full-text (BM25) search across all essays, book chapters, and field notes. Returns ranked matches with a snippet, id, and canonical URL. Pass an id to get_document to read the full text.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 10) |
| query | string | yes | Search terms |
| section | string | – | Restrict to one content type |
No output schema declared.
No examples provided.
What is the saagarpatel.dev Portfolio MCP server?
saagarpatel.dev Portfolio is an MCP server listed in the public MCP registry as io.github.saagpatel/portfolio-mcp. Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless. This page covers its npm package (saagar-portfolio-mcp).
Is the saagarpatel.dev Portfolio MCP server safe to use?
saagarpatel.dev Portfolio scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 saagarpatel.dev Portfolio MCP server expose?
saagarpatel.dev Portfolio exposes 6 tools: search, get_document, list_corpus, get_profile, list_projects, get_operant_results. Their descriptions and schemas cost roughly 386 tokens of context every time the server is loaded.
Is the saagarpatel.dev Portfolio MCP server still maintained?
saagarpatel.dev Portfolio is still listed as active in the MCP registry. We last reached this channel on 20 September 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 saagarpatel.dev Portfolio MCP server under?
saagarpatel.dev 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.