Tollary Agent Transaction Guard
NPM · TOLLARY
Local fit-check and safe integration guidance for non-custodial Base USDC agent transactions.
Available components
Last scanned (11 hours ago)
Scores higher than 98% of npm servers
Category Crypto and Web3
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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to hyKwon13/tollary). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 64 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 224 tokens (~56/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 3 Nov 26 −1
- Stability: 0.97 → pass security
- Security disclosure: pass → unverified ▼ functional
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 15 Oct 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.
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 npm/tollary@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 | hyKwon13/tollary |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/hyKwon13/tollary/.github/workflows/bootstrap-tollary-npm.yml@refs/heads/main |
| Rekor log index | 2651086147 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f61fc701dca7622a8b49b25169f159270b6c1e36446f0135c25f39069a2f5583ae127ad558e55f4e3ad1d2ff6af389c674cd13cca0026c3787139b78b |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
tollary_fit_check ~60
Read-only local project fit check. It skips secrets and makes no network, wallet, or payment call.
| Name | Type | Req | Description |
|---|---|---|---|
| origin | string | – | Tollary HTTPS origin. |
| project | string | – | Local project directory. Defaults to the MCP process working directory. |
No output schema declared.
No examples provided.
tollary_free_lint ~65
Submit exactly {transaction, mandate} to the free structural lint. It makes no RPC, wallet, or payment call.
| Name | Type | Req | Description |
|---|---|---|---|
| origin | string | – | Tollary HTTPS origin. |
| request | object | yes | Public unsigned transaction and owner-signed mandate. Never include secrets. |
No output schema declared.
No examples provided.
tollary_get_integration_plan ~39
Return the non-custodial integration sequence and prohibited secret-handling paths.
| Name | Type | Req | Description |
|---|---|---|---|
| origin | string | – | Tollary HTTPS origin. |
No output schema declared.
No examples provided.
tollary_inspect_offer ~38
Fetch public product, readiness, and legal metadata without paying or connecting a wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| origin | string | – | Tollary HTTPS origin. |
No output schema declared.
No examples provided.
How do I install the Tollary Agent Transaction Guard MCP server?
Tollary Agent Transaction Guard runs locally as an npm package, launched with npx -y tollary. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tollary
claude mcp add kr-p-e-tollary-agent-transaction-guard -- npx -y tollary
What is the Tollary Agent Transaction Guard MCP server?
Tollary Agent Transaction Guard is an MCP server listed in the public MCP registry as kr.p-e.tollary/agent-transaction-guard. Local fit-check and safe integration guidance for non-custodial Base USDC agent transactions. This page covers its npm package (tollary).
Is the Tollary Agent Transaction Guard MCP server safe to use?
Tollary Agent Transaction Guard scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 Tollary Agent Transaction Guard MCP server expose?
Tollary Agent Transaction Guard exposes 4 tools: tollary_free_lint, tollary_fit_check, tollary_inspect_offer, tollary_get_integration_plan. Their descriptions and schemas cost roughly 202 tokens of context every time the server is loaded.
Is the Tollary Agent Transaction Guard MCP server still maintained?
Tollary Agent Transaction Guard 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 Tollary Agent Transaction Guard MCP server under?
Tollary Agent Transaction Guard 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 Tollary Agent Transaction Guard MCP server?
VerifyMCP ran 15 checks on Tollary Agent Transaction Guard, 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 Tollary Agent Transaction Guard: Security disclosure. 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.