io.github.shivam-app-developers/ai-optimizer
NPM · @AI-OPTIMIZER/CORE · SCANNED SEP 20
MCP server that cuts AI coding agent token usage via framework-aware context optimization
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 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to shivam-app-developers/ai-optimizer). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 105 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 954 tokens (~86/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "strip_bash_noise" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 11 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 io.github.shivam-app-developers/ai-optimizer MCP server?
io.github.shivam-app-developers/ai-optimizer runs locally as an npm package, launched with npx -y @ai-optimizer/core. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @ai-optimizer/core
claude mcp add shivam-app-developers-ai-optimizer -- npx -y @ai-optimizer/core
{
"mcpServers": {
"shivam-app-developers-ai-optimizer": {
"command": "npx",
"args": [
"-y",
"@ai-optimizer/core"
]
}
}
} {
"servers": {
"shivam-app-developers-ai-optimizer": {
"command": "npx",
"args": [
"-y",
"@ai-optimizer/core"
]
}
}
} codex mcp add shivam-app-developers-ai-optimizer -- npx -y @ai-optimizer/core
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shivam-app-developers-ai-optimizer": {
"type": "local",
"command": [
"npx",
"-y",
"@ai-optimizer/core"
],
"enabled": true
}
}
} openclaw mcp add shivam-app-developers-ai-optimizer --command npx --arg -y --arg @ai-optimizer/core
mcp_servers:
shivam-app-developers-ai-optimizer:
command: "npx"
args: ["-y", "@ai-optimizer/core"] {
"McpServers": {
"shivam-app-developers-ai-optimizer": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@ai-optimizer/core"
]
}
}
} assistant mcp add shivam-app-developers-ai-optimizer -t stdio -c npx -a -y @ai-optimizer/core
{
"mcpServers": {
"shivam-app-developers-ai-optimizer": {
"command": "npx",
"args": [
"-y",
"@ai-optimizer/core"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 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.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
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/@ai-optimizer/core@0.1.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 | shivam-app-developers/ai-optimizer |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/shivam-app-developers/ai-optimizer/.github/workflows/release.yml@refs/tags/v0.1.0 |
| Rekor log index | 1739580074 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f60b70a03b54ed9661e3b08a41e385361014ef81b2c2d784289de16d96c8c6c49fa77608348f07be6780d418ddceb747fa71219126dca051b23b2ae4e |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| 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 →
budget_reset Reset budget counters ~27
Zeroes the per-session and per-day token counters. Use after intentionally clearing a budget breach.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
budget_status Show conversation/day budget status ~87
Reports the current per-session and per-day token consumption against configured caps. Caps are set via budgetCaps in .optimizerrc.json or AI_OPTIMIZER_BUDGET_PER_SESSION / AI_OPTIMIZER_BUDGET_PER_DAY env vars. When a cap is exceeded, optimized_read_file / list_files / grep / diagnostics refuse new calls until reset or until UTC midnight (day cap).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_optimizer_config Get optimizer config ~53
Returns the merged effective configuration: defaults overridden by user-global config, then project .optimizerrc.json, then env vars. Use to check whether scheduling, work-stealing, telemetry, etc. are currently enabled.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
optimized_diagnostics Get LSP diagnostics for a file (token-optimized) ~103
Returns errors and warnings from the language server for a single file, plus narrow code slices around each diagnostic. Use this BEFORE calling optimized_read_file when the agent is trying to fix an error — it returns ~10 lines of context around each issue instead of the whole file. Detected frameworks: javascript
| Name | Type | Req | Description |
|---|---|---|---|
| contextLines | integer | – | Lines of context around each diagnostic (default 10) |
| path | string | yes | Path to the file, relative to project root |
No output schema declared.
No examples provided.
optimized_grep Grep across files (token-optimized) ~119
Search file contents for a regex, scoped by directory and optional file glob, applying framework-aware ignore filters. Skips files larger than 2MB and caps at 100 matches. Detected frameworks: javascript
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Directory to search, relative to project root |
| filePattern | string | – | Optional glob pattern to filter files, e.g. "**/*.ts" |
| flags | string | – | Regex flags, e.g. "i" for case-insensitive |
| pattern | string | yes | Regex pattern to search for |
No output schema declared.
No examples provided.
optimized_list_files List files (token-optimized) ~89
List files in a directory with framework-aware ignore filtering. Skips node_modules, .venv, build/, dist/, generated files, etc. Optionally pass a glob pattern to narrow results. Detected frameworks: javascript
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Directory to list, relative to project root |
| pattern | string | – | Optional glob pattern to filter results, e.g. "**/*.ts" |
No output schema declared.
No examples provided.
optimized_read_file Read file (token-optimized) ~121
Read a file from the workspace with framework-aware filtering. Skips files matching framework ignore patterns or .gitignore. Use this instead of the built-in Read tool to reduce token usage. Optionally pass startLine/endLine (1-indexed, inclusive) to read only a slice. Detected frameworks: javascript
| Name | Type | Req | Description |
|---|---|---|---|
| endLine | integer | – | 1-indexed end line (inclusive) |
| path | string | yes | Path to the file, relative to the project root |
| startLine | integer | – | 1-indexed start line (inclusive) |
No output schema declared.
No examples provided.
optimizer_status Optimizer status ~29
Returns active framework packs, detected project type, gitignore status, and cumulative token savings for this session.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_symbol Read a symbol body via LSP (no whole-file read) ~166
Resolves a symbol name (e.g. "UserRepository.getUser", "users::repository::get") via the language server's workspace/symbol API and returns just the symbol body. Use this when you need a function or class definition but not the rest of the file. Falls back to no-match when the LSP can't resolve the symbol. Detected frameworks: javascript
| Name | Type | Req | Description |
|---|---|---|---|
| contextLines | integer | – | Lines of context to include before + after each symbol body |
| includeImports | boolean | – | Prepend leading imports / package / use lines from the file |
| maxMatches | integer | – | Cap on number of symbol matches returned (default 5) |
| query | string | yes | Symbol name, optionally container-qualified (Foo.bar / Foo::bar / Foo#bar) |
No output schema declared.
No examples provided.
set_optimizer_config Set optimizer config (writes to project .optimizerrc.json) ~93
Writes a partial config patch to the project-level .optimizerrc.json (merging with whatever is already there). User-global config and env vars are NOT modified — those are managed out-of-band. Behavior-changing flags (scheduling, workStealing, telemetry) require explicit opt-in via this tool — they are off by default.
| Name | Type | Req | Description |
|---|---|---|---|
| patch | object | yes | Partial OptimizerConfig to merge into project config |
No output schema declared.
No examples provided.
strip_bash_noise Strip noise from shell command output (token-optimized) ~67
Removes ANSI color codes, npm/maven/gradle progress lines, JVM reflective-access warnings, and collapses carriage-return progress bars. Pass the raw stdout/stderr from a Bash tool call here BEFORE keeping it in context.
| Name | Type | Req | Description |
|---|---|---|---|
| output | string | yes | Raw shell output to clean |
No output schema declared.
No examples provided.
What is the io.github.shivam-app-developers/ai-optimizer MCP server?
io.github.shivam-app-developers/ai-optimizer is an MCP server listed in the public MCP registry as io.github.shivam-app-developers/ai-optimizer. MCP server that cuts AI coding agent token usage via framework-aware context optimization. This page covers its npm package (@ai-optimizer/core).
Is the io.github.shivam-app-developers/ai-optimizer MCP server safe to use?
io.github.shivam-app-developers/ai-optimizer scores 93 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. 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 io.github.shivam-app-developers/ai-optimizer MCP server expose?
io.github.shivam-app-developers/ai-optimizer exposes 11 tools: optimized_read_file, optimized_list_files, optimized_grep, optimized_diagnostics, read_symbol, and 6 more. Their descriptions and schemas cost roughly 954 tokens of context every time the server is loaded.
Is the io.github.shivam-app-developers/ai-optimizer MCP server still maintained?
io.github.shivam-app-developers/ai-optimizer 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 io.github.shivam-app-developers/ai-optimizer MCP server under?
io.github.shivam-app-developers/ai-optimizer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.