
Silvanexum
io.github.silvanexumPublished by GitHub account silvanexumv0.4.0Updated Oct 27, 2026
Spend control for AI agents - cost attribution, budget caps, and signed runs as MCP tools.
Overview
Silvanexum is a local MCP server that gives an AI assistant spend-control tools for agents: cost attribution, budget caps and signed runs.
- What you can do
- The manifest lists no individual tools, so capabilities come from the description only.
- It exposes spend control for AI agents as MCP tools.
- It covers cost attribution, so assistant activity can be tied to costs.
- It offers budget caps and signed runs.
- It runs locally over stdio and talks to the Silvanexum API.
- When to use it
- Worth considering when you run AI agents and want their spending tracked, attributed and capped, or want runs recorded with signatures, and you are comfortable routing that through the Silvanexum service.
- Requirements
- Runs as a local process on the user's machine (desktop only) via npx from the npm package or uvx from the PyPI package, so Node.js or Python tooling is needed. Requires a scoped Silvanexum API key in SILVANEXUM_API_KEY (read+run recommended). SILVANEXUM_BASE_URL optionally overrides the default API base URL. Network access to the Silvanexum API.
Installation
In SourceWeft
- Open Silvanexum in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.4.0LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.