Silvanexum
PYPI · SILVANEXUM-MCP · 2 COMPONENTS
Spend control for AI agents - cost attribution, budget caps, and signed runs as MCP tools.
Available components
Last scanned (13 hours ago)
Scores higher than 83% of PyPI servers
Category AI and Machine Learning
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
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency71
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to silvanexum/Silvanexum-sdk). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 120 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 571 tokens (~57/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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; "deploy_template" implies "deploy" 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 10 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
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 →
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −20
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.63 functional
- 2 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → 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 5 Nov 2026 · Analysed pypi/silvanexum-mcp@0.2.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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | silvanexum/Silvanexum-sdk |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/silvanexum/Silvanexum-sdk/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 2103392038 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:3036e3d54c2021f77ce65339e8b6f47accf81b834d2566813ac0389e4af7939c |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| 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 →
create_budget ~117
Agent FinOps — create a spend cap over an org/project/agent for a period. With enforcement 'block', a run or mesh hop that would breach it is rejected server-side (HTTP 402). scope_id is required unless scope_type is 'org'. Requires a key with write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| alertThresholdPct | – | – | – |
| enforcement | – | – | – |
| limitCredits | number | yes | – |
| name | string | yes | – |
| periodType | string | yes | – |
| scopeId | – | – | – |
| scopeType | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
deploy_template ~56
Deploy a 1-click vertical agent template into a ready, signed agent (M11). Note: template endpoints may be 'planned' / not yet live on a deployment.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | – | – |
| templateId | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_agent ~27
Fetch an agent's configuration and earned reputation by id.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_reputation ~41
Get an agent's earned reputation — volume-aware trust score, success rate, and confidence, derived from signed runs.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_run ~38
Fetch a run's full signed trace (the step-by-step model/tool/agent timeline) by id.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_spending ~97
Agent FinOps — cost attribution. Spend rolled up by a dimension (agent|project|model|provider) over a window, from real run telemetry + the mesh ledger. Read-only — answers 'which agent/model burned the budget?'. `since` accepts relative ('-7d', '-24h') or ISO; default last 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| groupBy | – | – | – |
| since | – | – | – |
| to | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_budgets ~53
Agent FinOps — list spend caps (budgets), each with its live computed spend, remaining, and state (ok|warn|exceeded) for the current period.
| Name | Type | Req | Description |
|---|---|---|---|
| scopeType | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
run_agent ~67
Run an agent on a prompt. The run is captured, secret-scrubbed, and cryptographically signed. Returns the answer plus a replayable, signed trace URL. Requires the `run` scope.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| prompt | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_agents ~60
Search the marketplace for agents, ranked by PROVEN OUTCOMES (real run corpus + reputation), not stars. `sort` is one of proof|recent|price.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| q | – | – | – |
| sort | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
wallet_balance ~15
Get the org's credit balance.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Silvanexum MCP server?
Silvanexum runs locally as a PyPI package, launched with uvx silvanexum-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · silvanexum-mcp
claude mcp add silvanexum-silvanexum -- uvx silvanexum-mcp
What is the Silvanexum MCP server?
Silvanexum is an MCP server listed in the public MCP registry as io.github.silvanexum/silvanexum. Spend control for AI agents - cost attribution, budget caps, and signed runs as MCP tools. This page covers its PyPI package (silvanexum-mcp).
Is the Silvanexum MCP server safe to use?
Silvanexum scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 Silvanexum MCP server expose?
Silvanexum exposes 10 tools: search_agents, get_agent, get_reputation, run_agent, get_run, and 5 more. Their descriptions and schemas cost roughly 571 tokens of context every time the server is loaded.
Is the Silvanexum MCP server still maintained?
Silvanexum 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 Silvanexum MCP server under?
Silvanexum 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.
What did VerifyMCP test on the Silvanexum MCP server?
VerifyMCP ran 15 checks on Silvanexum, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Silvanexum: Security disclosure. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.